| 1 |
On Sun, Nov 8, 2009 at 5:14 AM, Florian Philipp |
| 2 |
<lists@f_philipp.fastmail.net> wrote: |
| 3 |
> James schrieb: |
| 4 |
>> All, |
| 5 |
>> |
| 6 |
>> I'm trying to set up a DNS server here for a lab environment. |
| 7 |
>> |
| 8 |
>> - hijacking a TLD (linux.com let's say, as an example) |
| 9 |
>> - trying to point several Linux boxen in a sandbox with no internet connectivity |
| 10 |
>> |
| 11 |
>> So, here's a copy of my tinydns data file: |
| 12 |
>> |
| 13 |
>> .linux.com:172.18.109.125:a:259200 |
| 14 |
>> =server1.linux.com:14.17.108.241:86400 |
| 15 |
>> =server2.linux.com:14.17.108.242:86400 |
| 16 |
>> |
| 17 |
> [...] |
| 18 |
>> |
| 19 |
>> Inside of /etc/dnscache/root/servers/linux.com I have "127.0.0.1" so |
| 20 |
>> that the server knows to query the tinydns daemon running. |
| 21 |
>> Unfortunately, however, a "dig @<ipAddr> server1.linux.com" doesn't |
| 22 |
>> seem to work. |
| 23 |
>> |
| 24 |
>> |
| 25 |
> |
| 26 |
> What do you mean with "doesn't seem to work"? Timeout? Wrong answer? |
| 27 |
> |
| 28 |
|
| 29 |
Well, tinydns must be bound to a different address than dnscache. |
| 30 |
|
| 31 |
If I do a dig @<tinydns ip address> server1.linux.com it responds with |
| 32 |
the correct address. |
| 33 |
|
| 34 |
However, if I put the dnscache IP address in my /etc/resolv.conf, |
| 35 |
resolution to *any* IP address (including server1.linux.com and |
| 36 |
server2.linux.com) fails. |
| 37 |
|
| 38 |
Thoughts? |
| 39 |
-j |
Archives