[dns-operations] Why the record locates in com. zone?

刘明星:) liumingxing at cnnic.cn
Thu Sep 15 03:32:42 UTC 2011


I have read up about the materials about glue records.
Indeed, parent zones should have all the information needed to access servers for their children zone. However, when the RRs 
zq681.com. IN NS ns3.wondns.com.
wondns.com. IN NS ns1.wondns.com
ns1.wondns.com IN A x.x.x.x
exist in com zone while the RR 
ns3.wondns.com. IN A X.X.X.X
does not exist in com zone, the resolution of zq681.com is ok, though there are more lookups because the RR 
ns3.wondns.com. IN A X.X.X.X
can be found in wondns.com zone.

Mingxing, Liu
liumingxing at cnnic.cn 

发件人: Mark Andrews 
发送时间: 2011-09-12  22:21:23 
收件人: 刘明星:) 
抄送: carlos; dns-operations 
主题: Re: [dns-operations] Why the record locates in com. zone? 
Please go read up about glue records.
RFC 1034:
One of the goals of the zone structure is that any zone have all the
data required to set up communications with the name servers for any
subzones.  That is, parent zones have all the information needed to
access servers for their children zones.  The NS RRs that name the
servers for subzones are often not enough for this task since they name
the servers, but do not give their addresses.  In particular, if the
name of the name server is itself in the subzone, we could be faced with
the situation where the NS RRs tell us that in order to learn a name
server's address, we should contact the server using the address we wish
to learn.  To fix this problem, a zone contains "glue" RRs which are not
part of the authoritative data, and are address RRs for the servers.
These RRs are only necessary if the name server's name is "below" the
cut, and are only used as part of a referral response.
and also from RFC 1034
As the last installation step, the delegation NS RRs and glue RRs
necessary to make the delegation effective should be added to the parent
zone.  The administrators of both zones should insure that the NS and
glue RRs which mark both sides of the cut are consistent and remain so.
So to answer your question, the address records need to be stored
in *both* the com and wondns.com zones and they also need to be
kept in the same.
In message <515833501.01129 at cnnic.cn> <201109122118183171998 at cnnic.cn>, "=?gb23
12?B?wfXD99DHo7qjqQ==?=" writes:
>       sorry, I did not give a explicit discription about my question. The 
> question is that in my opinion the RR "ns3.wondns.com.  172800 IN A 
>" should not be included in the 'com.' zone but in the 
> wondns.com zone. 
>       The zq681.com zone is authorized to the servers ns3.wondns.com zone 
> and ns4.wondns.com. Well, at the time, one question is coming ---where 
> should be the addresses of the two servers stored? Maybe in the com zone 
> or maybe in the wondns.com zone. It is known that wondns.com zone is 
> Authorized out to the two servers --ns1.wondns.com and ns2.wondns.com, so 
> the  RR "ns3.wondns.com.  172800 IN A" should exist in 
> the wondns.com zone instead of the com zone. However, I find that the RR 
> exists in the com zone. I want to know whether the RR should exist in the 
> com zone.
> 2011-09-12 
> Mingxing
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at isc.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dns-oarc.net/pipermail/dns-operations/attachments/20110915/43de3872/attachment.html>

More information about the dns-operations mailing list