Question Locked

Why can't my new 2008 server resolve DNS?

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have migrated my domain from a w2003 server to a W2008 server. The old server is no longer serving any roles in the domain. The old server has a different IP address than the new server.
All workstations in the network show the IP of the new server in their DNS settings.

The problem is that if I down the old server or unplug it's network cable DNS stops working. I can still ping yahoo.com from the new server or a PC but I cannot display it's web page. I have looked everywhere in my Sonicwall 2040 Pro which is doing the routing and the new server and cannot find any reference to the old DNS server's IP address.

Where could the ghost of this old server be hiding that I cannot shut it down?

15 replies

by oldbaritone

Did you copy the DHCP tables from the old server to the new? Maybe it's hiding in the DNS entry in DHCP, pushing the old server out as the DNS server for DHCP at the workstations.

Check IPCONFIG /ALL from a workstation and see if it has the new server address. Or if you're using a router for DHCP, make sure that was updated.

Good Luck

by pshiflet-24

You say that with the old server shut down you can ping by FQDN (i.e. ping www.yahoo.com)? If so, try pinging (from a workstation) a site you have never gone to and verify that the address resolves properly. If it does, DNS does not appear to be the issue. Is there any chance that the old server acted as a proxy or was running anything like ISA on it?

by thebluegoose

If you can resolve ip's from a domain name then DNS is working. Try using the nslookup command from the command prompt and see what DNS server it lists. If it matches your new DNS server name/ip address then the problem is most likely not DNS.

You can flush the local DNS cache from the desktops by running ipconfig /flushdns which would remove any old DNS entries as well but I do not think that is an issue.
If you are running a proxy then make sure that it is setup correctly on your server/workstations as well.

by krlseidl

No proxy. DNS server is listed correctly on all workstations.

I know this is a very vexing question. I have had a lot of very good techs look at this and no one can figure it out.

Could it be that when we moved the Active Directory from the old server to the new that something in the database didn't transfer properly?

by thebluegoose

Check your group policies if you have any setup that may be causing you issues. You can run RSOP from the command prompt on the workstations to see what policies are affecting them. But I do not think that AD is your issue.

Have you run TRACERT to a site that is resolving such as yahoo.com to see if you are making it there to begin with? See how far you get and that will tell you if you are actually getting to the outside. Also make sure there are no entries in your firewall ACL(s) that may be referencing the old server, but again this is not likely the issue either.

You can flush the DNS cache on the new server and then try to resolve a name to see if the server is getting outside for DNS requests as well in case the current entry is old but this is a shot in the dark.

by cg it

if local DNS lookups works but unresolved DNS lookups fail, then I'd vote for a forwarders problem.

by krlseidl

The old server is not a even a member of the domain anymore and has no forwarders in it. However, if I stop the DNS service on the old server none of my workstations or my new server can resolve DNS.

by pshiflet-24

Does the new server have any forwarders setup? If not, it will (should) just use the root hints (assuming they are present, no big deal). Is DNS setup to allow zone transfers and is the old server still listed there? From the DNS mmc check each Forward Lookup's SOA, Name Server, and Zone Transfer settings. You should do the same for each Reverse Lookup, too. Lastly, while you are there, check the DNS events from the Event Viewer. That may give some info.

Lastly, if you manually set the DNS settings for a PC to, say, your ISP's DNS servers can you then browse the Internet as normal?

by cg it

If your old server isn't a member of the domain anymore and doesn't have forwarders, then sticking it back on the network isn't going to do anything for DNS lookups.

think of something else...

lets see what you say when I mention the global catalog server, sysvol and netlogon shares????

and oh lets say, FSMO roles??

and oh, how about your ISP DNS servers ? are they listed anywhere?

by seanferd

if the DNS server has even been set up on the new W2k8 server.

Assuming this has anything to do with DNS at all.

by cg it

especially after the "no longer part of the domain" part....

to quote the poster "The old server is not a even a member of the domain anymore and has no forwarders in it. However, if I stop the DNS service on the old server none of my workstations or my new server can resolve DNS."

if you change the domain assocation from a domain to another domain or workgroup, then your effectively demoting the server. DNS service no longer exists for the old domain. The only time changing server domain associations is if created a new domain in DNS, and also keeping the hold domain in DNS which is not changing the server domain assocation.

The post ends up being the 100 questions type of question.

by thebluegoose

I am a little confused as to what you are seeing. You say that DNS is not working but in your initial post you said:

"I can still ping yahoo.com from the new server or a PC but I cannot display it's web page."

DNS resolves names to IP address's. So unless by this statement you are pinging one of yahoo's IP address directly, DNS is resolving the domain name, yahoo.com, to its IP address. Therefore DNS is working. The fact that you cannot get to the website is a different issue, not DNS related.

Please clarify what is happening if I am reading your statements incorrectly.

by krlseidl

Back from a 4 day weekend. Let's start fresh.
On my 2008 server I can ping yahoo.com. However I cannot open the web page www.yahoo.com unless my old 2003 server which is no longer a DC or even part of the domain is running and connected to the network.
I ran DCDIAG on the 2008 server and got the following error.
Directory Server Diagnosis

Performing initial setup:

Trying to find home server...

Home Server = FILE

* Identified AD Forest.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\FILE

Starting test: Connectivity

......................... FILE passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\FILE

Starting test: Advertising

......................... FILE passed test Advertising

Starting test: FrsEvent

......................... FILE passed test FrsEvent

Starting test: DFSREvent

......................... FILE passed test DFSREvent

Starting test: SysVolCheck

......................... FILE passed test SysVolCheck

Starting test: KccEvent

......................... FILE passed test KccEvent

Starting test: KnowsOfRoleHolders

......................... FILE passed test KnowsOfRoleHolders

Starting test: MachineAccount

......................... FILE passed test MachineAccount

Starting test: NCSecDesc

Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have

Replicating Directory Changes In Filtered Set
access rights for the naming context:

DC=ForestDnsZones,DC=agena,DC=local
Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have

Replicating Directory Changes In Filtered Set
access rights for the naming context:

DC=DomainDnsZones,DC=agena,DC=local
......................... FILE failed test NCSecDesc

Starting test: NetLogons

......................... FILE passed test NetLogons

Starting test: ObjectsReplicated

......................... FILE passed test ObjectsReplicated

Starting test: Replications

......................... FILE passed test Replications

Starting test: RidManager

......................... FILE passed test RidManager

Starting test: Services

......................... FILE passed test Services

Starting test: SystemLog

An error event occurred. EventID: 0xC0002719

Time Generated: 07/21/2010 06:26:11

Event String:

DCOM was unable to communicate with the computer 64.65.196.6 using any of the configured protocols.

An error event occurred. EventID: 0xC0002719

Time Generated: 07/21/2010 06:26:32

Event String:

DCOM was unable to communicate with the computer 64.65.208.6 using any of the configured protocols.

An error event occurred. EventID: 0xC0002719

Time Generated: 07/21/2010 06:27:34

Event String:

DCOM was unable to communicate with the computer 64.65.196.6 using any of the configured protocols.

An error event occurred. EventID: 0xC0002719

Time Generated: 07/21/2010 06:27:55

Event String:

DCOM was unable to communicate with the computer 64.65.208.6 using any of the configured protocols.

......................... FILE failed test SystemLog

The IP addresses that are in the errors are the DNS servers of my ISP which are configured in my Sonicwall 2040 Pro.

by krlseidl

I disconnected the old server from the network. Removed the DNS role form the new server. Rebooted the Sonicwall. Rebooted the new server and added the DNS role back and everything started working.

Go figure ?

This discussion is closed to new replies.