zone transfers

Barry Margolin barmar at genuity.net
Wed May 24 18:57:28 UTC 2000


In article <003d01bfc596$e2bdf790$9f01a8c0 at 523.bakerref.com>,
Hayden Wimmer <hwimmer at bakerref.com> wrote:
>my forward file transfers but not my reverse...any hints???

Did you fix the SOA record?  The incorrect SOA record that you posted below
should cause named to reject that zone file, which prevents zone
transfers.  In general, if named detects any errors when it's loading a
zone, it makes itself non-authoritative and won't allow zone transfers.

>-----Original Message-----
>From: Barry Margolin <barmar at genuity.net>
>Newsgroups: comp.protocols.dns.bind
>To: comp-protocols-dns-bind at moderators.isc.org
><comp-protocols-dns-bind at moderators.isc.org>
>Date: Wednesday, May 24, 2000 10:51 AM
>Subject: Re: please,please help
>
>
>>In article <001901bfc580$4a639830$9f01a8c0 at 523.bakerref.com>,
>>Hayden Wimmer <hwimmer at bakerref.com> wrote:
>>>when i do nslookups i always get this in-addr.arpa
>>>for example
>>>nslookup 192.168.1.234    returns
>>>
>>>server: hemi.168.192.in-addr.arpa
>>>address: 192.168.1.248
>>>
>>>name: charger.168.192.in-addr.arpa
>>>address: 192.168.1.234
>>
>>>here is the reverse file
>>>
>>>;
>>>;  reverse mapping
>>>;
>>>;
>>>
>>>test.com. IN SOA hemi.test.com. root.hemi.test.com.(
>>
>>This should be:
>>
>>168.192.in-addr.arpa. IN SOA ...
>>
>>or:
>>
>>@ IN SOA ...
>>
>>Also, you need a space before the '('.
>>
>>>       4  ; serial
>>>  21600  ; refresh
>>>  1800  ; retry
>>>  604800  ; expire
>>>  86400 )  ; minimum
>>>
>>>
>>>;name servers
>>> IN NS hemi.test.com.
>>> IN NS supernova.test.com.
>>
>>>;reverse
>>>1.1 IN MX 10 jebwebsrv1
>>>234.1 IN MX 20 charger
>>
>>Why do you have MX records in a reverse domain?
>>
>>>248.1 IN NS hemi
>>>248.5 IN NS supernova
>>>248.5 IN  PTR supernova
>>
>>This should be:
>>
>>248.5 IN PTR supernova.test.com.
>>
>>Any name that doesn't end in "." gets the name of the zone appended to it,
>>and in this case the zone name is "168.192.in-addr.arpa".  So if you don't
>>put a fully-qualified name in the PTR records, it's treated as:
>>
>>248.5.168.192.in-addr.arpa. IN PTR supernova.168.192.in-addr.arpa.
>>
>>--
>>Barry Margolin, barmar at genuity.net
>>Genuity, Burlington, 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.
>>
>>
>
>
>
>


-- 
Barry Margolin, barmar at genuity.net
Genuity, Burlington, 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.



More information about the bind-users mailing list