<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=gb2312">
<META content="MSHTML 6.00.2900.6129" name=GENERATOR>
<STYLE>@font-face {
font-family: 宋体;
}
@font-face {
font-family: Verdana;
}
@font-face {
font-family: @宋体;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 72.0pt 90.0pt 72.0pt 90.0pt; layout-grid: 15.6pt; }
P.MsoNormal {
TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
LI.MsoNormal {
TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
DIV.MsoNormal {
TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
FONT-WEIGHT: normal; COLOR: windowtext; FONT-STYLE: normal; FONT-FAMILY: Verdana; TEXT-DECORATION: none; mso-style-type: personal-compose
}
DIV.Section1 {
page: Section1
}
UNKNOWN {
FONT-SIZE: 10pt
}
BLOCKQUOTE {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</STYLE>
</HEAD>
<BODY style="FONT-SIZE: 10pt; MARGIN: 10px; FONT-FAMILY: verdana">
<DIV><FONT face=Verdana color=#000080 size=2>
<DIV>The com zone tell us that the NSes for zq681.com is ns[3-4].wondns.com
while the NSes for wondns.com is ns[1-2].wondns.com. At the same
time, the glue for ns[1-2].wondns.com do be in the com zone. So I think it is
not neccessary for the com zone to have the glue for ns[3-4], though the
existence of the glues may be not wrong but be effective for lookup
performance.</FONT></DIV></DIV>
<DIV><FONT face=Verdana color=#c0c0c0 size=2>2011-09-13 </FONT></DIV>
<DIV><FONT face=Verdana size=2></FONT>
<DIV>
<HR>
</DIV>
<DIV><FONT color=#c0c0c0>Mingxing, Liu</FONT></DIV>
<DIV><FONT color=#c0c0c0>CNNIC</FONT></DIV>
<ADDRESS><A href="mailto:liumingxing@cnnic.cn"><FONT
color=#c0c0c0>liumingxing@cnnic.cn</FONT></A><FONT
color=#c0c0c0> </FONT></ADDRESS></DIV>
<HR color=#b5c4df SIZE=1>
<DIV><FONT face=Verdana size=2><STRONG>发件人：</STRONG> Mark Andrews </FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>发送时间：</STRONG> 2011-09-12 22:21:23
</FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>收件人：</STRONG> 刘明星：） </FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>抄送：</STRONG> carlos; dns-operations
</FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>主题：</STRONG> Re: [dns-operations] Why the
record locates in com. zone? </FONT></DIV>
<DIV><FONT face=Verdana size=2></FONT> </DIV>
<DIV><FONT face=Verdana size=2>
<DIV></DIV>
<DIV>Please go read up about glue records.</DIV>
<DIV></DIV>
<DIV>RFC 1034:</DIV>
<DIV></DIV>
<DIV>One of the goals of the zone structure is that any zone have all the</DIV>
<DIV>data required to set up communications with the name servers for any</DIV>
<DIV>subzones. That is, parent zones have all the information needed to</DIV>
<DIV>access servers for their children zones. The NS RRs that name the</DIV>
<DIV>servers for subzones are often not enough for this task since they name</DIV>
<DIV>the servers, but do not give their addresses. In particular, if the</DIV>
<DIV>name of the name server is itself in the subzone, we could be faced with</DIV>
<DIV>the situation where the NS RRs tell us that in order to learn a name</DIV>
<DIV>server's address, we should contact the server using the address we wish</DIV>
<DIV>to learn. To fix this problem, a zone contains "glue" RRs which are not</DIV>
<DIV>part of the authoritative data, and are address RRs for the servers.</DIV>
<DIV>These RRs are only necessary if the name server's name is "below" the</DIV>
<DIV>cut, and are only used as part of a referral response.</DIV>
<DIV></DIV>
<DIV>and also from RFC 1034</DIV>
<DIV></DIV>
<DIV>As the last installation step, the delegation NS RRs and glue RRs</DIV>
<DIV>necessary to make the delegation effective should be added to the parent</DIV>
<DIV>zone. The administrators of both zones should insure that the NS and</DIV>
<DIV>glue RRs which mark both sides of the cut are consistent and remain so.</DIV>
<DIV></DIV>
<DIV>So to answer your question, the address records need to be stored</DIV>
<DIV>in *both* the com and wondns.com zones and they also need to be</DIV>
<DIV>kept in the same.</DIV>
<DIV></DIV>
<DIV>Mark</DIV>
<DIV></DIV>
<DIV>In message <515833501.01129@cnnic.cn> <201109122118183171998@cnnic.cn>, "=?gb23</DIV>
<DIV>12?B?wfXD99DHo7qjqQ==?=" writes:</DIV>
<DIV>> sorry, I did not give a explicit discription about my question. The </DIV>
<DIV>> question is that in my opinion the RR "ns3.wondns.com. 172800 IN A </DIV>
<DIV>> 113.105.171.124" should not be included in the 'com.' zone but in the </DIV>
<DIV>> wondns.com zone. </DIV>
<DIV>> The zq681.com zone is authorized to the servers ns3.wondns.com zone </DIV>
<DIV>> and ns4.wondns.com. Well, at the time, one question is coming ---where </DIV>
<DIV>> should be the addresses of the two servers stored? Maybe in the com zone </DIV>
<DIV>> or maybe in the wondns.com zone. It is known that wondns.com zone is </DIV>
<DIV>> Authorized out to the two servers --ns1.wondns.com and ns2.wondns.com, so </DIV>
<DIV>> the RR "ns3.wondns.com. 172800 IN A 113.105.171.124" should exist in </DIV>
<DIV>> the wondns.com zone instead of the com zone. However, I find that the RR </DIV>
<DIV>> exists in the com zone. I want to know whether the RR should exist in the </DIV>
<DIV>> com zone.</DIV>
<DIV>> </DIV>
<DIV>> 2011-09-12 </DIV>
<DIV>> </DIV>
<DIV>> </DIV>
<DIV>> </DIV>
<DIV>> Mingxing</DIV>
<DIV>-- </DIV>
<DIV>Mark Andrews, ISC</DIV>
<DIV>1 Seymour St., Dundas Valley, NSW 2117, Australia</DIV>
<DIV>PHONE: +61 2 9871 4742 INTERNET: marka@isc.org</DIV></FONT></DIV></BODY></HTML>