Want seperate machinename in SOA header, one named, 2 master domains...

[Barry Margolin]

In article <9r0a5a$r08 at pub3.rc.vix.com>,
those who know me have no need of my name  <not-a-real-address at usa.net> wrote:
>>; in master zone file for mydomainOne, 
>
>>@	1D IN SOA oneNS.mydomainOne.com.	[..stuff..]
>>	NS oneNS.mydomainOne.com
>>oneNS	A  1.2.3.4
>
>>; in master zone file for mydomainTwo
>
>>@	1D In SOA twoNS.mydomainTwo.com.	[..stuff..]
>>	NS twoNS.mydomainTwo.com.	
>>twoNS	A  1.2.3.4
>
>you can do this, bind will not puke.  the zones will have different
>information than the delegations contains, which negates the value of the
>condition (as you've explained in another message).

There's a good reason *not* to do this.  Since the NS records point to
hosts in the domain they serve, there needs to be a glue A record for the
hosts in the parent domain.  But NSI won't create glue records for both
oneNS.mydomainOne.com and twoNS.mydomainTwo.com.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.