ok, to make sure my understanding is what you're communicating:
two clients, (one on an NT domain, one on an AD domain called 'grouchy.com') nic has 'Obtain IP address automatically' checked, but if you click on the advanced button, and DNS tab,
x.x.x.48 is listed as the primary server
x.x.x.30 is listed as the secondary server
'Append these DNS suffixes' is also checked and listed is:
frog.com
fish.com
lizard.com
In 'DNS suffix for this connection' frog.com is listed
register this connections address in dns is checked
Use this connections DNS suffix in DNS registration is checked
Then in DHCP, DHCP specifies DNS servers of
x.x.x.30 as primary
x.x.x.48 as secondary
and a suffix list of:
frog.com
bird.com
snake.com
orange.com
Both clients try to ping a client specified only as warthog (Ping warthog)
According to my understanding of your message that DHCP takes precedence,
For the NT client (call it electron):
it will use server x.x.x.30
it will register with x.x.x.30 as electron.frog.com (listed as 'dns suffix for this connection' and (register this connections address' and 'use this connections dns suffix'
It will first attempt to resolve
warthog.frog.com (listed as 'dns suffix for this connection')
then
warthog.frog.com again because it is the first entry in the suffix list - which suggests it shouldnt be there since its already handled by the clients suffix
warthog.bird.com
warthog.snake.com
warthog.orange.com
for the AD client (call it lepton):
it will use server x.x.x.30
it will register as lepton.grouchy.com - AD always wants to use the domain name
it will try
warthog.grouchy.com - tries its own suffix first
warthog.frog.com
warthog.bird.com
warthog.snake.com
warthog.orange.com
also in this scenario, changing the order of the server list at the client will have no effect because the order specified by DHCP takes precedence.
Is this a correct understanding?
Finally,
For the NT client, if you have 'register this connection' and 'use this connections dns suffix' checked, but 'dns suffix for this connection' is blank, what happens?
Same question for AD - I assume it doesn't care and registers as lepton.grouchy.com
For AD client,if you uncheck 'register this connection', does it not register it? That doesn't seem probable since DNS is so integral to AD. If it still registers, then that checkbox doesnt really matter, correct?
For AD client, what about the next checkbox? Won't it always register as grouchy.com regardless of what you put in that checkbox and the 'dns suffix for this connection' box? If not, you will most certainly break it by putting in the wrong thing.
For the NT client unchecking 'register this connection' truely causes it not to register.
for the NT client what suffix will it register if 'use this connection's DNS suffix' is uncheck?
for the AD client, I know (or at least think I do) any settings in group policy will override all of the local and DHCP settings correct? But in the case where group policy specifies some settings and not others (specifies suffix order but not server addresses for instance) I assume the client uses the suffix order specified by the group policy, but servers specified by DHCP, or NIC settings. Correct?
Thanks for all your help! The basics I know, but the devil is in the details and I have to know the details to really see how things should work.
k