Best Practices Question

Public nameservers - commonly used

nameserver 4.2.2.1
nameserver 4.2.2.2
nameserver 4.2.2.3
nameserver 4.2.2.4
nameserver 4.2.2.5
nameserver 4.2.2.6


# host 4.2.2.2
2.2.2.4.in-addr.arpa domain name pointer vnsc-bak.sys.gtei.net.
 
Just a quick update:

I sent mail to ICANN.ORG asking the same question I have had posted on this forum. Here is the response I got back from the Manager, Root Zone Services Internet Assigned Numbers Authority via ICANN:

"We don't have a specific reference to a "best practice", but there is no problem for you setting up your own recursive name server rather than using a forwarder. All we recommend is that you take steps to make sure your root hints file is kept up to date — and as long as you use a package like BIND and regularly update it they should automatically provide you with updated hints files. Alternatively, you can download it from http://www.internic.net/zones/named.root"
 
hostpc.com said:
Public nameservers - commonly used

nameserver 4.2.2.1
nameserver 4.2.2.2
nameserver 4.2.2.3
nameserver 4.2.2.4
nameserver 4.2.2.5
nameserver 4.2.2.6
Click to expand...
Not quite. They're actually maintained for several different ISPs/hosting companies; do reverse lookups on all of them.

They usually work. We've seen them occasionally not work.

We now recommend using OpenDNS; however to run it on a server you MUST open an account and disable all their extra services so they won't redirect you to their own advert pages in case of non-existent domains.

Jeff
 
jlasman said:
We now recommend using OpenDNS; however to run it on a server you MUST open an account and disable all their extra services so they won't redirect you to their own advert pages in case of non-existent domains.
Click to expand...


What do I care if the server "sees" an advert page? People don't see the advert page.
 
floyd said:
What do I care if the server "sees" an advert page? People don't see the advert page.
Click to expand...
Well I suspect some scripts might break. Instead of getting an error back explaining the problem to the script, the script will instead get a page from OpenDNS. Scripts will get tricked into thinking that the connection was successful when it really was just redirected to a yahoo search with OpenDNS's logo and ads.
 
Not to mention problems sending emails to nonexistent or problem domains will return errors that are impossible to trace.

Not to mention that if you use ping or traceroute you'll never know the domain isn't reachable.

Jeff
 
Has anybody had any actual problems and not theoretical problems? I have not over the years.
 
I don't know why I lost track of this thread, but I'm back now.

Yes, Floyd, I've had problems. Lots of times. For example, I'd do a DNS query on a domain name to see if it exists, and I get an IP# instead of an NXDOMAIN status.

Same problem with email. Instead of getting back a notice that the domain doesn't exist I get a delivery failure.

So if you really insist on using OpenDNS you should really set up an account and make your settings for your IP#s so it worksas a properly working (non-redirecting) nameserver would.

However there's now another option; Google Public DNS. Google Public DNS doesn't do redirecting.

Jeff
 
Google is now what I use and recommend. Lots of things change in a year.
 
You must log in or register to reply here.
Back
Top