|
just as an FYI:
If you specify suffix search list it will override
the searching of appending the parent suffix of primary DNS suffix.
So if you just specify:
domain2.domain1.com
domain3.domain1.com
and not
domain1.com
it will not search domain1.com since it is not
specified in the Suffix Search List.
So if you want to still search the parent
suffix, be sure to include it in the SSL.
Jef
----- Original Message -----
Sent: Monday, July 31, 2006 4:13 AM
Subject: Re: [ActiveDir] DNS suffix
resolution..
I assume you are using WINS and the DCs of child and parent
domains are registered there. Therefore the netbios names are
resolving.
What happens when you try to ping the FQDN of the child domain server?
Does that work? I think your issue is you want the child domain suffix to be
appended automatically. My understanding is that it doesnt happen by default.
However the reverse is true. If you are in a child domain and ping or attempt
to resolve a name, it tries its own domain suffix before attempting to append
the parent domain suffixes. This is true as long as you havent disabled the
default behaviour, havent modified this through GPOs etc...
You can also specify a list of search suffixes to go through in a certain
order if you wish.
M@
On 7/30/06, HBooGz
<[EMAIL PROTECTED]> wrote:
I have a Forrest with one forest root and one child domain. The
child domain is running windows 2000 SP4 and the HQ sites are running
windows 2003 R2 standard. I have the the child domain controller
setup as an AD-integrated zone and i have the 2003 DNS servers setup to
receive that zone as a secondary zone. if i don't include the suffix
search order on the nic cards' dns entry page, i just resolve the netbios
names of the hosts at the remote site. for example. hq = company.comchild domain =
sales.company.comwhen i initiate a ping from any
host at HQ to a host in the child domain i only resolve the netbios name.
how can i resolve this ? I've tried setting up dns name
delegation in the past when i was running a full 2000 domain, but that name
resolution never worked right and it wasn't
timely. thanks, -- HBooGz:\>
|
