<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
Hello,<BR>
<BR>
thanks for this quick answer.<BR>
I am a liitle bit lost...<BR>
<BR>
What is the starting and ending SOA record?<BR>
<BR>
In the original zone, there is ony one SOA record...<BR>
<BR>
Hugo,<BR>
<BR>
<BR> <BR>
<DIV>
<DIV id=SkyDrivePlaceholder></DIV>> Date: Mon, 19 Mar 2012 10:41:22 -0700<BR>> From: michael@rancid.berkeley.edu<BR>> To: hugobxl@hotmail.com<BR>> CC: bind-users@lists.isc.org<BR>> Subject: Re: zone transfer with DIG: SOA duplicate<BR>> <BR>> On 03/19/12 10:33, hugo hugoo wrote:<BR>> > Dear all,<BR>> ><BR>> > I have this strange behaviour when I do a zone transfer with the<BR>> > following commande:<BR>> ><BR>> > dig @name_server zone_name AXFR<BR>> ><BR>> ><BR>> > ==> I received 2 SOA records (duplicates).<BR>> ><BR>> > One SOA record is at the end of the received information.<BR>> ><BR>> ><BR>> > Is this normal?<BR>> <BR>> Yes.<BR>> <BR>> In recent versions of dig, you can use the following option, as <BR>> documented in the man page:<BR>> <BR>> +[no]onesoa<BR>> Print only one (starting) SOA record when performing an <BR>> AXFR. The<BR>> default is to print both the starting and ending SOA records.<BR>> <BR>> <BR>> michael<BR></DIV> </div></body>
</html>