Maintained by: NLnet Labs

[Unbound-users] unbound fail to resolve a PTR

sca at andreasschulze.de
Tue Jun 24 09:28:31 CEST 2014


Hello,

unbound fail to resolve a specific PTR while other (most!) do work.
I noticed that one because my MTA rejects a message with "can't find  
reverse hostname" ...

$ restart_unbound_to_enforce_an_empty_cache
$ dig 224.243.93.193.in-addr.arpa. PTR

; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> 224.243.93.193.in-addr.arpa. PTR
;; global options: +cmd
;; connection timed out; no servers could be reached


but using the +trace option it looks better:
$ dig 224.243.93.193.in-addr.arpa. PTR +trace

; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> 224.243.93.193.in-addr.arpa. PTR +trace
;; global options: +cmd
.                       518377  IN      NS      h.root-servers.net.
.                       518377  IN      NS      i.root-servers.net.
.                       518377  IN      NS      j.root-servers.net.
.                       518377  IN      NS      k.root-servers.net.
.                       518377  IN      NS      l.root-servers.net.
.                       518377  IN      NS      m.root-servers.net.
.                       518377  IN      NS      a.root-servers.net.
.                       518377  IN      NS      b.root-servers.net.
.                       518377  IN      NS      c.root-servers.net.
.                       518377  IN      NS      d.root-servers.net.
.                       518377  IN      NS      e.root-servers.net.
.                       518377  IN      NS      f.root-servers.net.
.                       518377  IN      NS      g.root-servers.net.
;; Received 228 bytes from ::1#53(::1) in 3072 ms

in-addr.arpa.           172800  IN      NS      a.in-addr-servers.arpa.
in-addr.arpa.           172800  IN      NS      b.in-addr-servers.arpa.
in-addr.arpa.           172800  IN      NS      c.in-addr-servers.arpa.
in-addr.arpa.           172800  IN      NS      d.in-addr-servers.arpa.
in-addr.arpa.           172800  IN      NS      e.in-addr-servers.arpa.
in-addr.arpa.           172800  IN      NS      f.in-addr-servers.arpa.
;; Received 421 bytes from 2001:503:c27::2:30#53(2001:503:c27::2:30)  
in 1558 ms

193.in-addr.arpa.       86400   IN      NS      ns3.nic.fr.
193.in-addr.arpa.       86400   IN      NS      pri.authdns.ripe.net.
193.in-addr.arpa.       86400   IN      NS      sec1.apnic.net.
193.in-addr.arpa.       86400   IN      NS      sec3.apnic.net.
193.in-addr.arpa.       86400   IN      NS      sns-pb.isc.org.
193.in-addr.arpa.       86400   IN      NS      tinnie.arin.net.
;; Received 201 bytes from 196.216.169.10#53(196.216.169.10) in 765 ms

243.93.193.in-addr.arpa. 172800 IN      NS      ns2.cloud4you.biz.
243.93.193.in-addr.arpa. 172800 IN      NS      ns1.cloud4you.biz.
;; Received 94 bytes from 202.12.29.59#53(202.12.29.59) in 554 ms

224.243.93.193.in-addr.arpa. 86400 IN   PTR     relay2.netsol4u.de.
;; Received 77 bytes from 193.93.242.42#53(193.93.242.42) in 10 ms

$ cat /etc/unbound/unbound.conf
server:
         chroot: /var/lib/unbound
         do-daemonize: no
         extended-statistics: yes
         logfile: ""
         log-queries: yes
         pidfile: ""
         rrset-roundrobin: yes
         statistics-interval: 3600
         statistics-cumulative: yes
         use-caps-for-id: yes
         val-log-level: 2
         val-permissive-mode: yes
         trust-anchor: ". DS 19036 8 2  
49AAC11D7B6F6446702E54A1607371607A1A41855200FD2CE1CDDE32F24E8FB5"
         access-control: ::1 allow_snoop
         interface: ::1

$ cat /etc/resolv.conf
nameserver ::1

Any pointers to solve that issue?

Thanks
Andreas