For the purposes of explaining the below imagine we have a computer with a Primary DNS Suffix of "corp.domain.com".
> Append primary and connection specific DNS Suffixes:
Used by the DNS Client service when making a query. That is, if the user asks for "bob" the computer will automatically append the Primary DNS Suffix (and connection specific).
e.g. "ping bob" will result in a query for "bob.corp.domain.com"
> Append parent suffixes of the primary DNS suffix:
As with the above, except this time it will create queries in this order:
ping bob
lookup: bob.corp.domain.com
lookup: bob.domain.com
It will not look for "bob.com", there's a limit to how far it will go with this. Something you can control with registry settings if you were so inclined.
It will stop if it gets a valid answer, so won't necessarily run the entire set.
> Append these DNS suffixes (in order):
For queries again. If the system had a list like this:
corp.domain.com
domain2.org
domain3.net
A query would go like this
ping bob
lookup: bob.corp.domain.com
lookup: bob.domain2.org
lookup: bob.domain3.net
As before, it will stop the moment it gets a valid answer. So if the first works it will not test the rest.
> DNS suffix for this connection:
A specific suffix for the connection rather than using a Primary DNS Suffix. Rare to see this used, but no reason you can't if you're dealing with a workgroup.
> Register this connection's addresses in DNS:
Enable / Disable dynamic updates for the adapter. Doesn't work too well half the time and you have to go into the registry. However, since you want them to register this isn't a problem.
> Use this connection's DNS suffix in DNS registration:
Again, rare to see this used, used in conjunction with a connection specific suffix.
Chris
