On Sun, Nov 8, 2009 at 5:14 AM, Florian Philipp <li...@f_philipp.fastmail.net> wrote: > James schrieb: >> All, >> >> I'm trying to set up a DNS server here for a lab environment. >> >> - hijacking a TLD (linux.com let's say, as an example) >> - trying to point several Linux boxen in a sandbox with no internet >> connectivity >> >> So, here's a copy of my tinydns data file: >> >> .linux.com:172.18.109.125:a:259200 >> =server1.linux.com:14.17.108.241:86400 >> =server2.linux.com:14.17.108.242:86400 >> > [...] >> >> Inside of /etc/dnscache/root/servers/linux.com I have "127.0.0.1" so >> that the server knows to query the tinydns daemon running. >> Unfortunately, however, a "dig @<ipAddr> server1.linux.com" doesn't >> seem to work. >> >> > > What do you mean with "doesn't seem to work"? Timeout? Wrong answer? >
Well, tinydns must be bound to a different address than dnscache. If I do a dig @<tinydns ip address> server1.linux.com it responds with the correct address. However, if I put the dnscache IP address in my /etc/resolv.conf, resolution to *any* IP address (including server1.linux.com and server2.linux.com) fails. Thoughts? -j
