In
Deji Akomolafe said:
You have a DNS server. It hosts a.mycompany.com and, say,
otherdomain.com. Your clients have a.mycompany.com for their suffixes.
You have a record called xyz in a.mycompany.com and another record
called abc in otherdomain.com
You are expecting that if you ping xyz from a client, it should
resolve to xyz.a.mycompany.com. Your testing discovers that it does.
Now you are expecting that if you ping abc, it should resolve to
abc.othercompany.com. You are expecting this to happen because you
have the zone in your DNS server, but your testing shows that it does
not?
If the above are correct, then you are looking at the "expected
behavior". This is a client side issue, and is resolved by doing what
you've just discovered - adding the appropriate suffixes to your
clients. You can add multiple suffixes automatically through the use
of GPO (if all your clients are XP or W2K3) or by script.
Deji, here's a repost of one of your own posts from Dec, 2003 with a script
you used to populate the Search Suffix, and an explanation... Remember this
one?
----------------------------------------------------------------
I use a Machine Startup Script through GPO for this purpose. I apply the GPO
at the Domain Level so all my computers get it.
I use 2 files for the process - one .bat file and one .vbs file. The bat
file is the one that is specified in the GPO as the Startup script, and all
it does is call the .vbs file which does the DNS suffix configuration.
'This is the bat file
REM //////////////////////////////////////////////////////////////////
@echo off
cscript %logonserver%\netlogon\addDNS-Suffix.vbs
:END
REM //////////////////////////////////////////////////////////////////
'This is the .vbs file
'//////////////////////////////////////////////////////////////////
On Error Resume Next
SET WSHShell = CreateObject("WScript.Shell")
WSHShell.RegWrite
"HKLM\System\CurrentControlSet\Services\TCPIP\Parameters\SearchList",
"FirstDomain.com,child.firstdomain.com,seconddomain.net,firstdomain.blah,oth
erdomain.local,etcdomain.etc", "REG_SZ"
SET WSHShell = Nothing
'//////////////////////////////////////////////////////////////////
Both files go into the the Netlogon share of one of your DCs. From here,
they will be copied over to the rest of your DCs.
HTH
--
Regards,
Ace
Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.
This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Paramount: What's up with taking Enterprise off the air??
=================================