Replacing DNS Server with new.

[ekke]

Hi
I have an 2003 dns server running but the computer is old
and is being replaced. i have an new 2003 server running dns and they look exactly the same but when i use the new server i cant surf.

when i set up the new server i created an secondary server instance based on the old one.

Any ideas would be greateful.

//:EkkE

 

[aftertaf]

check your forwarders on the new server -vs- the old one...
you need to forward to your ISP DNS servers

if you do dhcp on your net, update name servers too!

and set it up for dynamic updates too, and make sure (if AD) that you get your domain controllers correctly registered with DNS otherwise you'll not be surfing but you'll have big waves!!


Aftertaf
We shall prevail, and they shall not

 

[ChrisAC]

you need to forward to your ISP DNS servers

Can't Windows DNS servers resolve DNS without using forwarders?

Chris.

**********************
Chris A.C, CCNA, CCSA
**********************

 

[aftertaf]

internal zone data, yes.

rest of world, no
he says he can't surf, hence i jump to the conclusion ...

there is also the root zone to delete..
otherwise they get a god complex


Aftertaf
We shall prevail, and they shall not

 

[ChrisAC]

I've just always wondered why Windows DNS servers can't get by without having forwarders set up. Can't they do thier own resolution without having to send recursive queries to a forwarder?

Chris.

**********************
Chris A.C, CCNA, CCSA
**********************

 

[Serbtastic]

They can resolve external queries by using root hints, they do not need DNS forwarders configured.

 

[BigShyBear]

Yes they can normally. Problems can be caused by the firewall between the network and the internet blocking UDP port 53, by the ISP blocking UDP port 53 to any IP address EXCEPT their DNS servers, and a '.' zone on the Windows DNS server making the DNS server think it is a root server. There are two schools of thought on whether Windows DNS servers ought to be configured with forwarders, personally I only do so if the firewall or the ISP force me to.

Check

http://support.microsoft.com/kb/291382

From the way I was reading this thread, the new server was set up as a secondary to the original server. You want to make the new server a primary or an active directory integrated DNS server. In the DNS service properties there is a tab 'Monitoring' If configured as a primary, just copy over the zone records from the old server. You can check whether the DNS service is resolving correctly. In the network card properties of the new server point DNS back on itself, and change the DNS server in DHCP and in the network card TCP/IP properties of any server with a fixed IP address. At that point I would reboot every computer with a fixed IP address (I am told this is not necessary, but I do it anyway.)