On Mon, Oct 13, 2014 at 05:47:29PM +0100, Ian Jackson
<[email protected]> wrote:
> In conjecture that the submitter had inconsistent forward and reverse
That was probably the case.
> DNS. adns by default (ie if you don't say `-t ptr-') insists that
> every address returned has a matching forward entry.
Adns doesn't do that, as at least test1.laendle resolves to 10.0.0.255,
but wasn't returned, so it failed for this ptr record.
# adnshost -i 10.0.0.255
Error during DNS PTR lookup for 255.0.0.10.in-addr.arpa: Inconsistent
resource records in DNS
# host 10.0.0.255
255.0.0.10.in-addr.arpa domain name pointer test2.laendle.
255.0.0.10.in-addr.arpa domain name pointer test1.laendle.
# host test1.laendle
test1.laendle has address 10.0.0.255
test1.laendle has IPv6 address 3ffe:1900:4545:2:240::f7e1
Besides, adns should follow the RFCs by default, that is, return the ptr
records when requested and follow cname chains instead of erroring out for
valid zone data (google.de was unresolvable for years by adns until they
recently changed their DNS setup), instead of imposing its own unrealistic
standards on the internet - no other resolver fails this way.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / [email protected]
-=====/_/_//_/\_,_/ /_/\_\
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
