AlpsAuto said:
Hello,
We recently renamed our AD domain. All server save one registered to
DNScorrectly. The problem server won't register in the DNS. When I run
ipconfig /registerdns I get -
If it is an ordinary member server that should work,
but it is insufficient for a DC if that is what you mean
by server. (See below*)
Error: the systems connot find the files specified
: Rfreshing DNS names
Where do you see this? You will do better giving the
full and exact text with the context in which you see it.
Most such problems with registration are due to the DNS
client not finding the (correct) DNS server for registration.
DNS Clients must use strictly the internal DNS servers,
and must be able to find -- through those servers -- the
Primary or AD-integrated DNS which is (physically)
dynamic.
More about DNS for AD (follows):
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)
netdiag /fix
....or maybe:
dcdiag /fix
(Win2003 can do this from Support tools):
nltest /dsregdns /server
C-ServerNameGoesHere
http://support.microsoft.com/kb/q260371/
Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.
Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.
Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
