thanks
Regards,
/Jimmy
--
Jimmy Andersson, Q Advice AB
Microsoft MVP - Directory Services
---------- www.qadvice.com ----------
"Roger" <ro...@nospam.com> wrote in message
news:%23NMeq8u...@TK2MSFTNGP10.phx.gbl...
"Jimmy Andersson [MVP]" <jimmy_N...@mvps.org> wrote in message
news:eJZvwAvD...@TK2MSFTNGP09.phx.gbl...
IF they aren't listed on each client the clients can
only try the ONE (or two) which they have as
possible choices.
Remember that DCs are "DNS clients" too.
DNS for AD
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:DC-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: ]
--
Herb Martin
"Roger" <ro...@nospam.com> wrote in message
news:O0AC1Lv...@TK2MSFTNGP14.phx.gbl...