Need enforcing...

rjbarlow

Hi MS techies,

is correct to say that what is marked in red is relatd to dynamically register over a DNS server a client and nothing has to do with DNS queries sent by this one?


Thank You.

rj

dynamik

The red box isn't related to dynamic registrations. You can specify alternate suffixes for the connection, which might be useful in a multihomed machine that is connected to multiple networks.

The other two options in the green box are related to dynamic registration.

It doesn't have anything to do with queries sent by that machine though.

rjbarlow

Mmm, I can't figure it out at all, I must say...

Can You provide an example of its utility?

If it's a strange or rare case leave it drop.

dynamik

Sure. Suppose you have a Windows 2003 machine setup as a router between domains. You have domain1.company.com and domain2.company.com, and one NIC is connected to each of them. Let's say that this machine is a member of domain1.company.com. If you do not use a connection specific suffix for a connection, it will register that connection with the suffix of the domain that the machine is in. Maybe you want to have the connection that is connected to domain2.company.com to be registered with that suffix in DNS.

i.e. if the machine is named router in domain1.company.com

No connection specific suffixes
nic1: router.domain1.company.com (default)
nic2: router.domain1.company.com (default)

Connection specific suffix on the second connection
nic1: router.domain1.company.com (default)
nic2: router.domain2.company.com

edit: This might be a bit easier to understand with the diagram: http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/cnet/cncf_imp_tyhp.mspx?mfr=true

rjbarlow

OK, I think I begin to understand its possible use, thanks much dynamic for the great explanation and for the link too!