small sibling glue records help
cet1 at hermes.cam.ac.uk
Wed Dec 19 16:54:50 UTC 2007
On Dec 19 2007, Alan Clegg wrote:
>Anatoly Pugachev wrote:
>> Can someone explain me, what does mean:
>> 18-Dec-2007 13:34:10.856 zone dom1.ru/IN: avgust.dom1.ru/NS 'ns.sub1.dom1.ru'
>> has no SIBLING GLUE address records (A or AAAA)
>> Does that mean, that i should add A record for ns.sub1.dom1.ru into dom1.ru
>> zone file?
>> I already have
>> $ORIGIN dom1.ru
>> sub1 NS ns1.zone.ru.
>> NS ns2.zone.ru.
>What this message means is that the nameservers (pointed to by the NS
>records) reside within the zone for which they are authoritative. For
>the nameserver of the zone above (in this case dom1.ru) to be able to
>provide a response including the IP addresses of the nameservers for the
>subordinate zone, you need the IP addresses in the parent.
>In other words, yes, you should add A records for the nameservers that
>live within the zone in question. I'm thinking that your example is
> $ORIGIN dom1.ru
[corrected as in later post]
> sub1 NS ns1.sub1.dom1.ru.
> NS ns2.sub1.dom1.ru.
>In this case, you need to add:
> ns1.sub1.dom1.ru. IN A x.y.z.a
> ns2.sub1.dom1.ru. IN A l.m.n.o
>to the dom1.ru zone file. (that's the "glue")
Yup, but as regards BIND 9.4.x error messages, that would be an absence
of "REQUIRED GLUE", not of "SIBLING GLUE". To get the original message,
the OP would have to have something like
avgust NS ns.sub1.dom1.ru.
; ... and maybe some others ...
; and another delegation:
sub1 NS ...
where the NS's for sub1 don't necessarily include ns.sub1.dom1.ru.
That is, the NS records for one child zone refer to names in a
_different_ child zone. The parent zone needs to have glue in this
case as well.
Of course, it would be easier to answer questions like this if the
OP hadn't used obfusticated names.
Email: cet1 at cam.ac.uk
More information about the bind-users