adding google dns to dhcp

Technical Information
Technical Information used Ask the Experts™
on
Hi

I'm having a DNS issue. the only way my clients get Internet is if I add Google dns to dhcp dns. can someone advice?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
you can try to put google dns in  your router or firewall and at client end just put gateway's ip in dns field.

Hope problem will be solved
Technical Specialist
Awarded 2017
Distinguished Expert 2018
Commented:
You need to add the Google DNS servers (8.8.8.8 and 8.8.4.4) to your DNS server's forwarding IPs and assign your DNS server's IP via DHCP to your cients
dnsforwarders.jpg
Distinguished Expert 2018

Commented:
You really haven't given us much to go on, or even what your desired setup would be. In a small workgroup? Adding google DNS to clients via DHCP is fine. Is your complaint that you can't use another DNS provider, such as OpenDNS? Or are you using active directory? Which requires clients use an AD DNS server. In which case Shaun *may* be right that forwarders is an option. But some people (me) have a natural distrust of Google, so if you WANT to use root hunts, you should say so... so we know where to focus our advice. In short, you haven't told us enough to reliably help.

Basically you need to tell us what is broken and why you want to change it...
C++ 11 Fundamentals

This course will introduce you to C++ 11 and teach you about syntax fundamentals.

Satish AutiSenior System Administrator
Commented:
Putting google DNS in dhcp dns is not recommended, sometimes you might get AD connectivity issues and then you have to restart the DNS server service.

As shaun said configure it in DNS servers forwarders, it will work no need to put it in root hints.
Satish AutiSenior System Administrator

Commented:
hoping you have AD and DNS servers in place...
Dr. KlahnPrincipal Software Engineer

Commented:
Rather than Google DNS, use OpenDNS instead.  Google DNS does not always return truthful results.  In particular, the Spamhaus blocking list (which is checked via DNS) always indicates "not blocked" when using Google DNS.

Falsus in uno, falsus in omnibus.  If Google DNS returns incorrect data for a site as important as Spamhaus, it is probably doing so for other sites as well.

Demonstration of this problem below, first using OpenDNS, then using Google.  The test FQDN "2.0.0.127.sbl-xbl.spamhaus.org" should always return 127.0.0.2 / 127.0.0.4, blocked.  Google DNS does not.

root@www:# nslookup 2.0.0.127.sbl-xbl.spamhaus.org
Server:         208.67.220.220
Address:        208.67.220.220#53

Non-authoritative answer:
Name:   2.0.0.127.sbl-xbl.spamhaus.org
Address: 127.0.0.2
Name:   2.0.0.127.sbl-xbl.spamhaus.org
Address: 127.0.0.4

root@www:# nslookup 2.0.0.127.sbl-xbl.spamhaus.org 8.8.8.8
Server:         8.8.8.8
Address:        8.8.8.8#53

** server can't find 2.0.0.127.sbl-xbl.spamhaus.org: NXDOMAIN

Open in new window

Shaun VermaakTechnical Specialist
Awarded 2017
Distinguished Expert 2018

Commented:
Out of curiosity, would you want to resolve to a none route-able IP?
Shaun VermaakTechnical Specialist
Awarded 2017
Distinguished Expert 2018

Commented:
Nvm.
I see it is Spamhaus return codes. Only an issue if DNSBL is used.
Spamhaus recommends using your own DNS. I would not go so far as to say Google DNS is not trustworthy only because it does not support DNSBL.
I do however prefer OpenDNS because I can do some content/malicious filter on it
Satish AutiSenior System Administrator

Commented:
Closing Inactive question

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial