new DC

[bill s via WinServerKB.com]

I swapped a crashed DC with another. This is the sole server on the network.
I first removed all PC's from the domain to a workgroup...then swapped.
However I used a modified domain name and now when I go to join the PC's to
the new domain and server they say they can't find the DC.
Do I need to flush their DNS or something??

Thanks

 

[Richard G. Harper]

Are the clients looking at the "new" DNS server for name resolution?

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[bill s via WinServerKB.com]

Are the clients looking at the "new" DNS server for name resolution?

I swapped a crashed DC with another. This is the sole server on the
network.

[quoted text clipped - 5 lines]

Thanks

Rihard.....Yes....the clients point to the server IP and the server points to
itself. Should I not have an external DNS IP listed in the forwarder?? I did
not do this before and the DC seemed not to be able to resolve MSN.COM.
Really strange because we could find every other site but MSN.

Thanks

 

[Richard G. Harper]

A correctly configured DNS server in AD will use either forwarders or root
hints to resolve all names outside the domain. The domain clients should
have only the AD DNS server configured - no others.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

Are the clients looking at the "new" DNS server for name resolution?

I swapped a crashed DC with another. This is the sole server on the
network.

[quoted text clipped - 5 lines]

Thanks

Rihard.....Yes....the clients point to the server IP and the server points
to
itself. Should I not have an external DNS IP listed in the forwarder?? I
did
not do this before and the DC seemed not to be able to resolve MSN.COM.
Really strange because we could find every other site but MSN.

Thanks

 

[bill s via WinServerKB.com]

A correctly configured DNS server in AD will use either forwarders or root
hints to resolve all names outside the domain. The domain clients should
have only the AD DNS server configured - no others.
[quoted text clipped - 12 lines]

Thanks

I removed an EXPIRED copy of NORTON Internet security that was on the PC and
after, the PC happily joined the domain. UN-friggin'-believable. Thanks to
all who tried to help.

Bill

 

[Richard G. Harper]

I'm glad you finally figured it out.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

A correctly configured DNS server in AD will use either forwarders or root
hints to resolve all names outside the domain. The domain clients should
have only the AD DNS server configured - no others.

Are the clients looking at the "new" DNS server for name resolution?

[quoted text clipped - 12 lines]

Thanks

I removed an EXPIRED copy of NORTON Internet security that was on the PC
and
after, the PC happily joined the domain. UN-friggin'-believable. Thanks to
all who tried to help.

Bill