name resolution problem

Greetings:

My problem is that tinydns responds to a first query, but then times 
out on subsequent ones.  The delegation seems correct:

$ dnsq a petonets.com f.gtld-servers.net
1 petonets.com:
98 bytes, 1+0+2+2 records, response, noerror
query: 1 petonets.com
authority: petonets.com 172800 NS ns1.petonets.com
authority: petonets.com 172800 NS ns2.petonets.com
additional: ns1.petonets.com 172800 A 84.78.232.127
additional: ns2.petonets.com 172800 A 84.78.232.127

Here is my data file:

$ less /etc/tinydns/root/data
+ns1.petonets.com:84.78.232.127
+ns2.petonets.com:84.78.232.127
+pinger.petonets.com:84.78.232.127
+secure.petonets.com:84.78.232.127

.petonets.com::ns1.petonets.com
.petonets.com::ns2.petonets.com
+petonets.com:84.78.232.127
+www.petonets.com:84.78.232.127
@petonets.com:84.78.232.127

84.78.232.127 is the remote IP my ISP gives me.  It is supposedly 
dynamic, but hasn't changed in 2 months.

I configured tinydns and dnscache thus:

tinydns-conf tinydns dnslog /etc/tinydns 192.168.2.103
dnscache-conf dnscache dnslog /etc/dnscache 127.0.0.1

I've configured the router to forward port 53 (UDP) to 192.168.2.103, 
which is the IP my wireless router gives the OpenBSD machine in 
question:

$ ifconfig ral0 | grep inet
         inet6 fe80::280:5aff:fe53:9305%ral0 prefixlen 64 scopeid 0x2
         inet 192.168.2.103 netmask 0xffffff00 broadcast 192.168.2.255

Here is what happens:

cd /service/tinydns/root
$ tinydns-get a petonets.com | grep answer
answer: petonets.com 86400 A 84.78.232.127

Then:
$ dnsq a petonets.com 84.78.232.127 | grep answer
answer: petonets.com 86400 A 84.78.232.127

However, when I repeat the last request it times out:
$ dnsq a petonets.com 84.78.232.127
1 petonets.com:
timed out

The logs show (19:57:05 was the successful query; the other 4 timed 
out):
2009-01-01 19:57:05.783194500 84.78.232.127:dc51:a152 + 0001 
petonets.com
2009-01-01 19:57:15.834917500 84.78.232.127:dc52:1cf5 + 0001 
petonets.com
2009-01-01 19:57:16.856856500 84.78.232.127:dc53:2150 + 0001 
petonets.com
2009-01-01 19:57:19.886800500 84.78.232.127:dc54:2bf0 + 0001 
petonets.com
2009-01-01 19:57:30.917501500 84.78.232.127:dc55:fc15 + 0001 
petonets.com

After 3 or 4 minutes, it responds correctly again.

If anyone can suggest why this might be, I would appreciate it.

Thanks for your time and trouble.

Lou Hevly
[email protected]

-- 
All the best (Adéu-siau),
Lou Hevly
[email protected]
http://visca.com