-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
John Blinka wrote:
** server can't find 104.1.168.192.in-addr.arpa: NXDOMAIN
That seems pretty clear ... :)
As you probably know from reading the djb docs, the jobs of recursive
resolving and authoritative nameserving are separate. You appear to be
using 192.168.1.254 as a recursive resolver, so I presume that's the IP
address where you're running dnscache. It's telling you that it doesn't
know who is authoritative for 192.168.1.104.
You must tell it who to ask by adding a file
/etc/dnscache/root/servers/104.1.168.192.in-addr.arpa (or an appropriate
subnet thereof, such as 1.168.192.in-addr.arpa). The content of that
file should be the IP address of tinydns (which cannot be the same IP
address as dnscache), which will then know how to find your hosts by IP
address.
Similarly, there needs to be a file
/etc/dnscache/root/servers/yourdomain.blah, with the same contents, for
forward lookups.
I cheat and run tinydns on 127.0.0.1, and dnscache on the public IP
address, which is incorrect because only my dnscache can reach it.
Nevertheless, it works well for me internally, since my internal hosts
all use the same (my) dns resolver. Ergo, I have a file
/etc/dnscache/root/servers/1.168.192.in-addr.arpa which contains the
line 127.0.0.1.
Cheers -d
- --
David Talkington
PGP key: http://www.prairienet.org/~dtalk/004B8F8B.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFFy+vw5FKhdwBLj4sRAsatAJ9qAVB17AQlp19xlIH2rSgcw1kbqQCbBnuU
22L+UtZPXoWYEgczQ3suP60=
=OEFU
-----END PGP SIGNATURE-----
--
[email protected] mailing list
