Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

ignoring out-of-zone data (254.88.8.207.in-addr.arpa)

1,250 views

Skip to first unread message

unread,

May 10, 2010, 1:48:44 PM5/10/10

to bind-...@lists.isc.org

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

unread,

May 10, 2010, 2:20:34 PM5/10/10

to Jason Davis, bind-...@lists.isc.org

Your zone definition in named.conf must have a different name than
what you expect. Check it for typos.

Chris Buxton
BlueCat Networks

> _______________________________________________
> bind-users mailing list
> bind-...@lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>

--
Sent from my mobile device

unread,

May 10, 2010, 2:21:56 PM5/10/10

to Chris Buxton, bind-...@lists.isc.org

Thanks guys, the issue was i just needed to put the last octect in the
zone file.

Thanks,
Jason

unread,

May 10, 2010, 8:43:58 PM5/10/10

to comp-protoc...@isc.org

> 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.

--
Barry Margolin, bar...@alum.mit.edu
Arlington, MA
*** PLEASE don't copy me on replies, I'll read them in the group ***

0 new messages