| 1 |
All, |
| 2 |
|
| 3 |
I'm trying to set up a DNS server here for a lab environment. |
| 4 |
|
| 5 |
- hijacking a TLD (linux.com let's say, as an example) |
| 6 |
- trying to point several Linux boxen in a sandbox with no internet connectivity |
| 7 |
|
| 8 |
So, here's a copy of my tinydns data file: |
| 9 |
|
| 10 |
.linux.com:172.18.109.125:a:259200 |
| 11 |
=server1.linux.com:14.17.108.241:86400 |
| 12 |
=server2.linux.com:14.17.108.242:86400 |
| 13 |
|
| 14 |
I've been following instructions on the following two pages in order |
| 15 |
to get some guidance on where I'm going with this: |
| 16 |
|
| 17 |
http://www.fredshack.com/docs/djbdns.html |
| 18 |
http://wiki.vpslink.com/HOWTO:_Setup_a_DNS_server_with_tinydns |
| 19 |
|
| 20 |
Inside of /etc/dnscache/root/servers/linux.com I have "127.0.0.1" so |
| 21 |
that the server knows to query the tinydns daemon running. |
| 22 |
Unfortunately, however, a "dig @<ipAddr> server1.linux.com" doesn't |
| 23 |
seem to work. |
| 24 |
|
| 25 |
Thoughts? Ideas? |
| 26 |
|
| 27 |
Thanks! |
| 28 |
-j |
Archives