In article <[email protected]>, Jason Davis <[email protected]> wrote:
> Thanks guys, the issue was i just needed to put the last octect in the > zone file. That doesn't sound right. As long as the suffix matched the zone name, it shouldn't have caused the error you got. 254 IN PTR <hostname> is equivalent to 254.88.8.207.in-addr.arpa. IN PTR <hostname> if the zone name is 88.8.207.in-addr.arpa. The more common mistake is to forget the trailing ".", but then it would be treated as 254.88.8.207.in-addr.arpa.88.8.207.in-addr.arpa. IN PTR <hostname> but this still wouldn't cause the error. > > Thanks, > Jason > > On Mon, May 10, 2010 at 12:20 PM, Chris Buxton <[email protected]> > wrote: > > Your zone definition in named.conf must have a different name than > > what you expect. Check it for typos. > > > > Chris Buxton > > BlueCat Networks > > > > On 5/10/10, Jason Davis <[email protected]> wrote: > >> Hello, > >> I have setup some rdns with bind, when i try to start I get this error: > >> > >> /etc/zones/master/reverses/88.8.207.in-addr.arpa:257: ignoring > >> out-of-zone data (254.88.8.207.in-addr.arpa) > >> > >> I get it for each host in the reverse zone file. ANy idea whay Im doing > >> wrong? > >> > >> Thanks, > >> Jason > >> _______________________________________________ > >> bind-users mailing list > >> [email protected] > >> https://lists.isc.org/mailman/listinfo/bind-users > >> > > > > -- > > Sent from my mobile device > > -- Barry Margolin, [email protected] Arlington, MA *** PLEASE don't copy me on replies, I'll read them in the group ***
_______________________________________________ bind-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/bind-users
