My ISP, Pipex, seems to be having problems with its DNS servers on a regular basis now, so I have to keep putting in new ones when they do. Most DNS servers provided by ISPs are limited to their own IP ranges now, so they don't work. I used to use Demon's DNS servers for years, but now you can't. So instead I guess IP addresses in the same range as those at my data center and hope they're running unprotected DNS.. luckily, most are.
This isn't a good situation though, but Googling for public DNS servers mostly brings up projects that provide free DNS hosting rather than simple resolution services. Which DNS servers do you recommend? This has also become a problem with FeedDigest, so much so that FeedDigest now runs its own DNS, which isn't ideal, but we don't have much choice due to ISP reliability.
I've been using http://www.dnsmadeeasy.com/ for two and a bit years now ever since I started having DNS problems with a previous hosting provider. Their support has been incredible and uptime is 100%.
Posted by: Jonathan Conway at January 6, 2006 04:42 PMI enjoy using dyndns.com
Posted by: PJ Hyett at January 6, 2006 06:21 PMThe last time I checked, pretty much all of Internap's DNS servers are usable by the public. You could try ns[12].lon.pnap.net
Posted by: Scott Laird at January 6, 2006 11:09 PMIn fact, running your own DNS *is* ideal.
Posted by: iuhihiuh at January 7, 2006 02:52 AMWhy rely on others when you can do it yourself just as well?
Thanks for the suggestions! I'll give these a try.
Posted by: Peter Cooper at January 10, 2006 03:46 PMReturn to the homepage.
Privacy Policy