DNS Trouble? What's the cure?

[Guest]

Our network consisted of two Win2k servers, the PDC also runs Exchange. I
bought a new server & need to retire the old one. I installed win2k, added
it to the domain as an additional controller. Installed DNS, A/D & then
Exchange. I moved e-mail, FSMO roles, moved the global catalog, set it as
PDC as per KB 300468, KB 295419 & KB 255690. If the original PDC is shut
down I get DNS errors on the other two servers, all servers & PC's run
extremely slow & it takes 15 minutes to access network files thru explorer.
The original PDC is old & it's got to go. For now I leave it running but
need a solution. All are on SP4. Help!!!

 

[Danny Sanders]

Our network consisted of two Win2k servers, the PDC also runs Exchange. I

bought a new server & need to retire the old one. I installed win2k, added
it to the domain as an additional controller. Installed DNS,

Did you have your DNS zone set to AD integrated? This way your existing DNS
zone gets replicated to the new server.

then

Exchange. I moved e-mail, FSMO roles, moved the global catalog, set it as
PDC as per KB 300468, KB 295419 & KB 255690.

Did you point ALL AD clients to the NEW DNS server via DHCP or manually?

hth
DDS W 2k MVP MCSE

 

[Guest]

Did you have your DNS zone set to AD integrated? This way your existing DNS
zone gets replicated to the new server.

Yes it is AD integrated

then


Did you point ALL AD clients to the NEW DNS server via DHCP or manually?

DHCP is pointed to the two servers I want to remain on my network, new
server listed first. Even my servers bog down when the original PDC is
turned off. Any other ideas?

 

[Danny Sanders]

DHCP is pointed to the two servers I want to remain on my network, new

server listed first. Even my servers bog down when the original PDC is
turned off.

Do you mean your DHCP server is passing out the DNS settings to your clients
and it is giving them both the DNS servers? The new one and the old DNS
server?


Do both servers have the correct DNS information?
See:
How to verify that SRV DNS records have been created for a domain controller

http://support.microsoft.com/default.aspx?scid=kb;en-us;816587



hth

DDS W 2k MVP MCSE

 

[Guest]

The DHCP server is passing out the DNS settings to clients and it is pointing
them both the two DNS servers I intend to keep on the network neither of
which is the original PDC. Should I only point DHCP clients to one DNS
server? Should my servers point only to themselves or should they also point
to each other?

 

[Danny Sanders]

You can have them point to them selves first then to the other as second.

Do both servers have the correct DNS information?
See:
How to verify that SRV DNS records have been created for a domain controller

http://support.microsoft.com/default.aspx?scid=kb;en-us;816587

hth
DDS W 2k MVP MCSE

 

[Enkidu]

Yes it is AD integrated


DHCP is pointed to the two servers I want to remain on my network, new
server listed first. Even my servers bog down when the original PDC is
turned off. Any other ideas?

It definitely sounds like a DNS problem. Check the servers and clients
using ipconfig /all to ensure that the information is getting
propogated around.

Cheers,

Cliff

 

[Guest]

I read kb816587. I have the SRV records for all three of my servers in DNS
Manager as discribed in the article. I tried the nslookup as described in
the article and received the correct information back for all three servers
as described in the article.

What else can I try?

 

[Guest]

Thanks for the tip. When I ran ipconfig on a client I found it had "server1"
& "server2" listed. "server1" is the one I am trying to retire but can't
because of the problems I discribed above. DHCP has "server2" & "server3"
listed. I am going to force clients to obtain new DNS from DHCP. After a
couple of days when I have confirmed with ipconfig that DHCP has updated DNS
I'll try shutting down "server1" & post the results.