Tinydns zone transfers

gtr33m

Hi all,

Has anyone managed to get zone transfers working on tinydns?

I'm using pfsense 2.0 RC3 and the DNS works fine, but I can't seem to get the zone transfers to work at all.

I've followed the instructions at:

http://forum.pfsense.org/index.php/topic,19828.msg102564.html#msg102564

to no avail.

The bug says it's fixed, but apparently it isn't as the allowed ip addresses were not in the tcp file.

Whenever I try a dig with AFXR at one of the allowed sites I get

;; communications error to 192.168.2.1#53: end of file

. Trying the same dig without the AFXR works fine, so it's not a connection issue.

ps aux | grep afxrdns
```gives no results, so it's safe to assume that afxrdns is not running.  Does anyone know how to start it manually so I can at least test it?

If it's completely impossible to get it working, does anyone know how else I can convert my now extensive tinydns records to bind format so that I can move the DNS to another server?

Thanks.

gtr33m

After a little more exploring I have a bit more info.

executing /var/etc/axfrdns/run

I get the message:

tcpserver: fatal: unable to bind: address already used

Which is strange because the only thing that should be running on 53 is TinyDNS and it should only be on UDP.

netstat doesn't give me any info at all, does anyone know how to check what is running on port 53 which would stop axfrdns from running?

Guest

I'm currently running into the same issue. Attempting a zone transfer ends in an "end of file" error message.

Have you figured anything out yet?

Regards,
-Jan

Guest

I found it:

Instead of adding the zone transfer database to

/etc/axfrdns
and running
tcprules tcp.cdb tcp.tmp < tcp

you have to put it into

/var/etc/axfrdns

That'll fix the end of file issue.

Hope this helps,
-Jan

gtr33m

JOL,

Thanks for the reply, but unfortunately that's not it. I already noticed that. I think that it is a change from pfsense 1 to pfsense 2. Packages were moved to /var/.

Even when done in the right location the tcp file is lost on reboot.

I believe that the patch that previously fixed the problem has been lost somewhere along the line.

Mark