Choose your DNS!

[Melbosa]

So out of any of these Public DNS, which would you choose?

Free Public DNS Server

=> Service provider: Google
Google public dns server IP address:

    * 8.8.8.8
    * 8.8.4.4

=> Service provider:Dnsadvantage
Dnsadvantage free dns server list:

    * 156.154.70.1
    * 156.154.71.1

=> Service provider:OpenDNS
OpenDNS free dns server list / IP address:

    * 208.67.222.222
    * 208.67.220.220

=> Service provider:Norton
Norton free dns server list / IP address:

    * 198.153.192.1
    * 198.153.194.1

=> Service provider: GTEI DNS (now Verizon)
Public Name server IP address:

    * 4.2.2.1
    * 4.2.2.2
    * 4.2.2.3
    * 4.2.2.4
    * 4.2.2.5
    * 4.2.2.6

=> Service provider: ScrubIt
Public dns server address:

    * 67.138.54.100
    * 207.225.209.66

[Mr. Analog]

I used to use Google but they get really slow sometimes...

I seem to occasionally have DNS issues through Shaw, I choose to blame Kadafi

[Tom]

I use my own instance of BIND. DNS lookups are free of high jacking, and I can set the caching time to "very short" so I see updates right away. And its very low latency, and very fast. Makes the entire internet feel faster.

[Melbosa]

I have a client whom needs to use DNS for a secondary service, and am looking for an option on best option

[Tom]

I have a client whom needs to use DNS for a secondary service, and am looking for an option on best option

Hmm, if they don't mind domain result hijacking, try OpenDNS. Google is usually pretty stable too. Those are the only ones I remember using for any kind of time. But the latency to either one is about 2x what you get from your ISP even in the best case.

[Mr. Analog]

I will give Google DNS that, they are stable, but sometimes slow...

[Lazybones]

My domain registrar also has dns hosting, keep it simple an together.

Dns hosting is different from lookup provider, go with what is cheap and stable.

[Melbosa]

Not looking for Hosting... looking for Lookup Provider, so Public DNS.  This is for a secondary lookup should the onsite server not find it itself.

[Lazybones]

Do you have a dedicated on side external dns or all in one? If your site dns is hosed your network is hosed.

Dont know your environment but sounds soho, guessing windows?

Set your dc as primary with root lookups, and assuming your router/firewall has dns set it as secondary and have it point at the local ISP dns.

[Lazybones]

FYI you need to use local dns (ISP or your own) or akimi hosted sites route wrong or slow.

Try a tracert to Canada.com after changing your dns provider and doing an ipconfig /flush dns you should get different results from ISP, google and open dns.

If you can't host your self then ISP is next best unless your ISP sucks.

[Melbosa]

Well its a local DC with its own DNS installed.  It is setup for root lookups, but I have also configured it allow forwarding lookups should a root lookup fail.  The ISP is Supernet and they do NOT provide DNS servers.

Not my first rodeo but thanks for the advice.  It had been a while since I had setup this server, so based on your posts I decided to double checked everything else just encase (never know if someone changed something or I missed a step in my earlier years ).  Its all configured fine for local server DNS lookups by local network devices.  Root server lookup first, then forwarding lookups only on failure.

[Lazybones]

Well if it is a case of what dns the DC points to not what the clients point to then having it setup with the latest root server list is about all you should need. If you set a forwarder it will use that before falling back to the root servers..

Note however that DNS in 2008 and 2008 R2 can be flaky at times, there are a few bugs and settings that can be tweaked to avoid them

[Melbosa]

And registry keys can be used to change order of execution,