TinyDNS - dnsq failure

[shealey]

I've built DJBDNS a few times before and its always worked flawlessly - however having just built it on my FreeBSD6.1 box for a new toaster I'm stumped by a problem which has cropped up in the supporting tools.

Tinydns is now happily serving to the outside world, but the 'dnsq' tool always returns 'host unreachable' when I test the server locally, even though I am specifying the correct address for the interface on which the local tinydns server is listening.
Even more puzzling, it can't query the mirror tinydns server on the neighbour machine either. However the 'host' tool on both machines can query either nameserver no problem.

I initially built djbsns from the FreeBSD6.1 port, but having come up against this problem I backed it out and rebuilt both installs from DJB's own source code. Same problem. Might this be an issue with FreeBSD itself? I haven't yet built the dns cache - this comes after testing tinydns in Dan's instructions.

Sean.

[matt]

You aren't helping us help you. You have said nothing about your configuration, nor anything about how you tested. Search Google for "how to ask questions the smart way" and perhaps you'll get better answers.

dnsq is a very simple program, with very simple usage:

cadillac# dnsq
dnsq: usage: dnsq type name server

cadillac# dnsq a www.tnpi.net. ns1.cadillac.net.
1 www.tnpi.net:
155 bytes, 1+1+3+3 records, response, authoritative, noerror
query: 1 www.tnpi.net
answer: www.tnpi.net 3600 CNAME tnpi.net
authority: tnpi.net 14400 NS ns1.cadillac.net
authority: tnpi.net 14400 NS ns2.cadillac.net
authority: tnpi.net 14400 NS ns3.cadillac.net
additional: ns1.cadillac.net 3600 A 69.54.202.196
additional: ns2.cadillac.net 3600 A 66.249.3.135
additional: ns3.cadillac.net 3600 A 72.29.110.103

[shealey]

Yeah, sorry I'm guilty of rambling.

Here's some specifics of whats happening:

Two of my FreeBSD boxes are running Tinydns 1.05. A local 'dnsq' query of the tinydns server running on either of these boxes fails:

dnsq a mail.digitalworkshop.net 89.202.129.35
1 mail.digitalworkshop.net:
host unreachable

...where 89.202.129.35 is the external address of the box I'm running the query from. From the same box I get the same result trying to query its neighbour:

dnsq a mail.digitalworkshop.net 89.202.129.36
1 mail.digitalworkshop.net:
host unreachable

Neither box is running a firewall, and the tinydns servers on both FreeBSD boxes are answering queries both locally and to the outside world - using an alternative tool locally works just fine:

host -t A mail.digitalworkshop.net 89.202.129.35
Using domain server:
Name: 89.202.129.35
Address: 89.202.129.35#53
Aliases:

mail.digitalworkshop.net has address 89.202.129.38
mail.digitalworkshop.net has address 89.202.129.38
mail.digitalworkshop.net has address 89.202.129.38
mail.digitalworkshop.net has address 89.202.129.38
mail.digitalworkshop.net has address 89.202.129.38
mail.digitalworkshop.net has address 89.202.129.38


Although dnsq is failing on the FreeBSD boxes, it works fine on the Gentoo box we have in the same rack:

dnsq a mail.digitalworkshop.net 89.202.129.35
1 mail.digitalworkshop.net:
414 bytes, 1+6+2+14 records, response, authoritative, noerror
query: 1 mail.digitalworkshop.net
answer: mail.digitalworkshop.net 86400 A 89.202.129.38
answer: mail.digitalworkshop.net 86400 A 89.202.129.38
answer: mail.digitalworkshop.net 86400 A 89.202.129.38
answer: mail.digitalworkshop.net 86400 A 89.202.129.38
answer: mail.digitalworkshop.net 86400 A 89.202.129.38
answer: mail.digitalworkshop.net 86400 A 89.202.129.38
authority: digitalworkshop.net 259200 NS ns1.solsticehosting.net
authority: digitalworkshop.net 259200 NS ns2.solsticehosting.net
additional: ns1.solsticehosting.net 259200 A 89.202.129.35
additional: ns1.solsticehosting.net 86400 A 89.202.129.35
additional: ns1.solsticehosting.net 259200 A 89.202.129.35
additional: ns1.solsticehosting.net 259200 A 89.202.129.35
additional: ns1.solsticehosting.net 259200 A 89.202.129.35
additional: ns1.solsticehosting.net 259200 A 89.202.129.35
additional: ns1.solsticehosting.net 259200 A 89.202.129.35
additional: ns2.solsticehosting.net 259200 A 89.202.129.36
additional: ns2.solsticehosting.net 86400 A 89.202.129.36
additional: ns2.solsticehosting.net 259200 A 89.202.129.36
additional: ns2.solsticehosting.net 259200 A 89.202.129.36
additional: ns2.solsticehosting.net 259200 A 89.202.129.36
additional: ns2.solsticehosting.net 259200 A 89.202.129.36
additional: ns2.solsticehosting.net 259200 A 89.202.129.36


I've tried building both from FreeBSD ports and from Dan's own distribution with identical results.

I should probably post this query to Dan himself really...

Sean.

[shealey]

Again, for purposes of documentation -

The problem turned out to be that the 'IPv6' option had been enabled in the port build. Clearing the build options ... 'make rmconfig' ... and rebuilding solved the problem.

'dnsq' works just fine now.

[ Big thanks to Matt for pointing me in the right direction ]

Sean.