-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Ihsan, The SOA record below indicates that unbound is operating a block on 168.192.in-addr.arpa. You can disable the block with: local-zone: "168.192.in-addr.arpa." nodefault Or only for 192.168.42.0/24 with: local-zone: "42.168.192.in-addr.arpa." transparent Best regards, Wouter Ihsan Dogan wrote: > But if send the query to the Unbound resolver, I don't get an answer: > ihsan at kraftbuech:~$ dig -t ns 42.168.192.in-addr.arpa. @192.168.42.2 > > ; <<>> DiG 9.4.3-P1 <<>> -t ns 42.168.192.in-addr.arpa. @192.168.42.2 > ;; global options: printcmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 57169 > ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 > > ;; QUESTION SECTION: > ;42.168.192.in-addr.arpa. IN NS > > ;; AUTHORITY SECTION: > 168.192.in-addr.arpa. 10800 IN SOA localhost. nobody.invalid. 1 3600 > 1200 604800 10800 > > ;; Query time: 5 msec > ;; SERVER: 192.168.42.2#53(192.168.42.2) > ;; WHEN: Sun May 17 12:05:54 2009 > ;; MSG SIZE rcvd: 100 > > > > Ihsan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkoRCIUACgkQkDLqNwOhpPhrDwCfR23h/OcPOD2NWWR7ytKZ13Eq iJQAn09ffxHfe55T/ulfoZlJTzbfWDZd =fQmj -----END PGP SIGNATURE-----