Wrong domain DNS suffix being used.

[Simon]

A server is attaching its local domain suffix instead of the trusted domain
that should be added:

Server1 in abc.com domain should know that Server2 is located in xyz.com
domain but when I try and ping the server it tries Server2.abc.com

All advice welcomed,

Rgds, Simon.

 

[Chriss3 [MVP]]

You can specify the DNS Suffix used as an DHCP Option or as a GPO Setting.

--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services

No email replies please - reply in the newsgroup

 

[Herb Martin]

A server is attaching its local domain suffix instead of the trusted domain
that should be added:

Servers (or any computers) don't control the suffix through
trusts or any such similar relationship.

Server1 in abc.com domain should know that Server2 is located in xyz.com
domain but when I try and ping the server it tries Server2.abc.com

"Should know"??? How?

Suffix search lists are MERELY a convenience for users
and aren't really related to Windows Domains or really
must related to DNS itself (except for client behavior.)

If you wish to add additional suffixes then you must do
that on the NIC -> IP properties -> Advanced -> DNS,
or (as Chris3 says) using a GPO to accomplish the same
idea.

What precisely is your situation?

 

[ptwilliams]

DHCP can only be used to provide the primary DNS suffix though. What you
require is a DNS Suffix Search list. For this you either have to manually
add these entries (advanced TCP/IP settings, DNS), or use some kind of
script to write these values to the registry.

We use a kix script that is called as part of the logon script to do this in
our multi-domain environments.

I'll dig out the registry key and value and post it back...


--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

You can specify the DNS Suffix used as an DHCP Option or as a GPO Setting.

--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services

No email replies please - reply in the newsgroup

 

[Simon]

I have added both Domain suffixes in the NIC's settings. As for your
question - should know, how? That is the perfect summary of my problem - How
does a domain controller know that server1 is in domain1... surely this is
standard AD information and not something I have to set in some search
list??

 

[Simon]

I have just carried out a test mirroring the servers settings in another
site and that server attached the correct dns suffix. I believe the error is
occurring because the server with the error resides on a subnet which uses
NAT.

 

[Herb Martin]

I have added both Domain suffixes in the NIC's settings. As for your
question - should know, how? That is the perfect summary of my problem - How
does a domain controller know that server1 is in domain1...

I was repeating your question, thus the extra question
marks. You seemed to think it "should know" and if
so how do you think it does?

surely this is
standard AD information and not something I have to set in some search
list??

You don't have to set it in one domain, but outside
of that domain it doesn't "know".

Suffixs additonal is a convenience that DNS CLIENTS
do -- so the users doesn't have to type.

(You could of course do a search in the GC for a
forest wide name but this doesn't apply to "client
DNS requests" anyway.)

Part of your misundstanding (or expectation) may
be that you are mixing Active Directory and DNS.
AD uses DNS for name resolution (and even location)
but DNS does not use AD for such.

 

[ptwilliams]

surely this is standard AD information and not something I have to set in

some search list??

Not at all. You are trying to resolve the name server1. How do you resolve
this? Well DNS is a hierarchical database of names, and works by delegating
authority to servers that hold a subset of the database. So, the name
server1 is meaningless. server1.domain-name.com. is helpful. But how does
your client know which namespace the name you are typing in belongs too? It
doesn't, so it uses a search suffix list to try multiple combinations. For
example, with the default settings in a domain called child.domain-name.com
the DNS resolver (the client software) would first try
server1.child.domain-name.com. and if that didn't resolve it would try
server1.domain-name.com.

At no point is this information obvious to any non-human being ;-)

Remember it's quite valid to have server1.child.domain-name.com,
server1.domain-name.com, server1.com, and server1.domain.com, etc.

The locator list is essential in multi-domain environments.


--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

I have added both Domain suffixes in the NIC's settings. As for your
question - should know, how? That is the perfect summary of my problem - How
does a domain controller know that server1 is in domain1... surely this is
standard AD information and not something I have to set in some search
list??