| 1 |
James schrieb: |
| 2 |
> All, |
| 3 |
> |
| 4 |
> I'm trying to set up a DNS server here for a lab environment. |
| 5 |
> |
| 6 |
> - hijacking a TLD (linux.com let's say, as an example) |
| 7 |
> - trying to point several Linux boxen in a sandbox with no internet connectivity |
| 8 |
> |
| 9 |
> So, here's a copy of my tinydns data file: |
| 10 |
> |
| 11 |
> .linux.com:172.18.109.125:a:259200 |
| 12 |
> =server1.linux.com:14.17.108.241:86400 |
| 13 |
> =server2.linux.com:14.17.108.242:86400 |
| 14 |
> |
| 15 |
[...] |
| 16 |
> |
| 17 |
> Inside of /etc/dnscache/root/servers/linux.com I have "127.0.0.1" so |
| 18 |
> that the server knows to query the tinydns daemon running. |
| 19 |
> Unfortunately, however, a "dig @<ipAddr> server1.linux.com" doesn't |
| 20 |
> seem to work. |
| 21 |
> |
| 22 |
> |
| 23 |
|
| 24 |
What do you mean with "doesn't seem to work"? Timeout? Wrong answer? |
Archives