![]() |
|
|||||||
| Notices |
![]() |
|
|
Thread Tools | Display Modes |
|
|
#1 |
|
Guest
Posts: n/a
|
Multiple stub zones - set preference? Weird...
We have 3 AD-integrated stub zones (forest-wide):
corp.company.net (AD Domain) company.net (AD Forest Root) oldcompany.com (Legacy, phasing this out) All 3 stubzones have the same server as SOA: DNSServer01.oldcompany.com Our AD DNS Server is ServerDC01.corp.company.net We have a host: Server01 Server01 has a record (same IP) Server01.oldcompany.com and Server01.corp.company.net, both of which resolve to the same IP. When I do a NSLookup on our AD server, it always returns the record on the stub zone oldcompany.com instead of the stub zone for the domainn corp.company.net even though the SOA has both. How do I set a preference condition to say if there's a record in the zone corp.company.net to return that instead of the record in oldcompany.com? I thought this would be automatic considering the DNS suffixes on both the client and server both have corp.company.net above oldcompany.com AND the AD DNS server itself is joined to the corp.company.net domain. What gives? |
|
|
|
#2 |
|
Guest
Posts: n/a
|
Re: Multiple stub zones - set preference? Weird...
Read inline please.
In news:, Mark Z. <> wrote: > We have 3 AD-integrated stub zones (forest-wide): > corp.company.net (AD Domain) > company.net (AD Forest Root) > oldcompany.com (Legacy, phasing this out) > > All 3 stubzones have the same server as SOA: > DNSServer01.oldcompany.com > Our AD DNS Server is ServerDC01.corp.company.net > > We have a host: Server01 > Server01 has a record (same IP) Server01.oldcompany.com and > Server01.corp.company.net, both of which resolve to the same IP. > > When I do a NSLookup on our AD server, it always returns the record > on the stub zone oldcompany.com instead of the stub zone for the > domainn corp.company.net even though the SOA has both. > > How do I set a preference condition to say if there's a record in the > zone corp.company.net to return that instead of the record in > oldcompany.com? > I thought this would be automatic considering the DNS suffixes on > both the client and server both have corp.company.net above > oldcompany.com AND the AD DNS server itself is joined to the > corp.company.net domain. > > What gives? This is determined by the DNS Suffix search order, the default order is, Primary DNS suffix, Connection DNS suffix, then parent names of the Primary DNS suffix. You have the option of creating the suffixes and orders of your choice in TCP/IP Properties, or by creating a custom DNS suffix search list in a Group Policy. -- Best regards, Kevin D. Goodknecht Sr. [MVP] Hope This Helps =================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue, to respond directly to me remove the nospam. from my email address. =================================== =================================== Use Outlook Express?... Get OE_Quotefix: It will strip signature out and more =================================== Keep a back up of your OE settings and folders with OEBackup: =================================== |
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|
< Windows Help - MS Office Help - Hardware Support >
| New To Site? | Need Help? |