retiring a 2003 AD DNS and replacing with 2008 AD DNS

Hello Experts,

I have a 2003 PDC running DNS for our domain. i've installed a 2008 server, joined it to domain, and added the DNS server role to it. The 2008 DNS has synced the forward lookups, reverse, and custom zone. I went into the 2008 machine and specified in network settings to look to it's own IP address for the DNS server and a public DNS for internet.

I changed my network settings of my client to point to the new 2008 DNS. I logged into AD Domain successfully, got email from the exchange server, etc. but i lost internet. i checked my network settings and i'm still pointing to my gateway/firewall.

the 2008 Server has internet and my f/w rules are setup to allow all outbound. wondering what i'm missing?



The DNS settings for the NIC on the server should only point to another DNS server inside your network and itself, not to any public DNS servers like your ISP's or Google's, etc. Resolving of internet addresses is accomplished through the use of root hints or forwarders configured in the DNS Management console.

With those settings in place, in the DNS Management console, go to the properties of the server and check the Monitoring tab, select both the tests (simple and recursive query), and click Test Now. If both pass you should be good to go as far as the server config is concerned. You could try browsing from the server to be sure.

With your client NIC settings pointing to the new server for DNS, running a command like
nslookup www.google.com
should tell you whether it can resolve names correctly.



The DNS settings for the NIC on the server should only point to another DNS server inside your network and itself, not to any public DNS servers like your ISP's or Google's, etc. Resolving of internet addresses is accomplished through the use of root hints or forwarders configured in the DNS Management console.

With those settings in place, in the DNS Management console, go to the properties of the server and check the Monitoring tab, select both the tests (simple and recursive query), and click Test Now. If both pass you should be good to go as far as the server config is concerned. You could try browsing from the server to be sure.

With your client NIC settings pointing to the new server for DNS, running a command like
nslookup www.google.com
should tell you whether it can resolve names correctly.



thank you for schooling me! within dns mgmt i copied the root hints from my first DNS server and i'm able to resolve those outside addresses. regards peter







Share this

Related Posts

There was an error in this gadget