Hello everybody,

I have installed Vegadns (Version 0.9.9) successful and added a local Test
Zone.

TLD: test.org

+a.ns.test.org:192.168.10.2:3600
+www.test.org:192.168.9.29:3600
&test.org::a.ns.test.org:3600
Ztest.org:a.ns.test.org.:hostmaster.test.org.::16384:2048:1048576:2560:86400

The internal tinydns is running under 192.168.10.3 and the internal dnscache
is running under 192.168.10.2 Both IP Addresses are located at the same
Machine with IP Aliasing.

When I ask tinydns with the dig command I get the correct results. Since it
is a local domain, I want my internal dnscache to query this domain. The
internal dnscache is also used by people to surf the internet.

So I have to put test.org manually in the dnscache /root/servers with the IP
Address of tinydns.

My question is now, is it possible when I create a TLD with Vegadns that the
program also write the TLD entry to the DNSCACHE, 

(f.E. echo "192.168.10.3" >> test.org  - in the /root/servers directory)

so that other people can add a new domain with vegadns, but do not have to
add a entry in the dnscache /root/servers directory manually, because they
are not used to a Unix Machine.

I tried the following thing...

I want to teach the dnscache that he should first query the internal DNS for
all queries. So I put 192.168.10.3 into the @ file under the dnscache
/root/servers. But when I use my dnscache to query the test.org domain I get
not my internal IP address. I get the official IP Address of it. This is not
good. It seems that my internal dnscache do not ask my internal dns server
for the ip and go directly outside to the TLD root DNS servers....

So is there a possibility to tell dnscache to always query the internal dns
server and if this zone is not present, try to reach another DNS Cache (i.e.
my Provider's one).

Another possibility would be to force Vegadns to write the data it writes
into the data file 

#test.org
+a.ns.test.org:192.168.10.2:3600
+www.test.org:192.168.9.29:3600
&test.org::a.ns.test.org:3600
Ztest.org:a.ns.test.org.:hostmaster.test.org.::16384:2048:1048576:2560:86400
 
also to the dnscache /root/servers directory and take the #test.org, strip
of the # and create this file with the IP Address of the & Record. Can I do
that by modifying the update-data.sh? (I am not so good at scripting so I
tried it with the forward DNS Cache)

Is this assumption right?... Many many questions... I know.... :-)

But I hope somebody can give me a hint to the both possibilities.

Best, and thanks for reading this long posting

Robert

Reply via email to