CentOS - Jan 2006 - tinydns -some help needed

Is there a tinydns or dns wizard that could give me some hints, please?

I am setting up and testing tinydns, but have some problems figuring out 
how to route. I do get dnscache to listen on tinydns.  Also I do not 
understand why it will not answer the given ip (127.0.0.1) to the name 
server.

1. Both services are up running and seems to be working fine, so why no 
reply, (on the first query/reply below)?

2. I am behind a firewall/router and have dynamic ip address from my 
isp. Can I set up the name server to be dynamic or how can I solve this 
by routing?


--config info

Dnscache is listening to the local nic 192.168.1.102
tinydns is listening to the local nic 192.168.1.100

Here's the query to dnscache where no ip given back:

# dnsqr a test.example.net
1 test.example.net:
34 bytes, 1+0+0+0 records, response, noerror
query: 1 test.example.net

# dnsqr a server1.test.example.net
1 server1.test.example.net:
58 bytes, 1+1+0+0 records, response, noerror
query: 1 server1.test.example.net
answer: server1.test.example.net 86400 A 192.168.1.102

# cat /etc/dnscache/log/main/current | grep tx
@4000000043d9f8b118a12724 tx 0 1 test.example.net. test.example.net. 
7f000001 c0a80164
@4000000043d9f8b5212dcc1c tx 0 1 server1.test.example.net. 
test.example.net. c0a80164 7f000001

# cat /etc/tinydns/root/data
.test.example.net:127.0.0.1:a:259200
.1.168.192.in-addr.arpa:127.0.0.1:a:259200
=server1.test.example.net:192.168.1.102:86400

On 1/27/06, Kai Sandsengen <centos.newsgroup at sandsengen.com>
wrote:
> Is there a tinydns or dns wizard that could give me some hints, please?
Any reason you're using tinydns as opposed to bind?  I can throw a
couple sample zones your way for bind, but I've never looked at
tinydns (given that it doesn't come with centos and all :-P )

--
Jim Perrin
System Architect - UIT
Ft Gordon & US Army Signal Center