Bug #1887
axfrdns from tinydns is not working
| Status: | New | Start date: | 09/18/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Affected version: | Affected Architecture: |
Description
I am experiencing the same problem reported in bug #119. #119 was closed a year ago, but I'm seeing the same problem in tinydns package version 1.0.6.16. This is with pfsense version 2.0-RC3.
axfrdns is reporting: "tcpserver: warning: dropping connection, unable to read tcp.cdb: file does not exist" from /var/etc/axfrdns/log/main/current.
When I check /usr/local/pkg/tinydns.inc I see there is a function, tinydns_setup_axfrdns() that is never called. I believe this was fixed in the patch attached to #119.
Am I using a stale version of tinydns? I installed it using the integrated package manager. Is there a trick to get the fixed version?
mike
axfrdns.patch
- patch to tinydns.inc for axfrdns from #119
(1.2 kB)
Associated revisions
Add protocol options for Manual Outbound NAT rules. See ticket #1887
Revert "Add protocol options for Manual Outbound NAT rules. See ticket #1887"
This reverts commit 15f2431e9dcb567754434162a62ce179c31b11ac.
This really belongs on mainline, not RELENG_1_2, since it is a new feature.
History
#1
Updated by Michael Durian over 1 year ago
- File axfrdns.patch added
I updated to 2.0-release yesterday and that introduced a new problem. Now I get "tcpserver: fatal: unable to bind: address already used" errors when axfrdns tries to start.
I did apply the attached patch, which I extracted from #119, and that creates a tcp.cdb file. I think things might work if I can figure out why tcpserver is throwing the address already used error.
mike
#2
Updated by Michael Durian over 1 year ago
Rebooting fixed the binding error and with the attached patch, axfrdns is now responding to zone transfer requests.
mike
#3 Updated by Anonymous over 1 year ago
Just upgraded to package version 1.0.6.17 on pfSense 2.0.1. DNS zone transfers are broke again.
-Jan
#4 Updated by Anonymous over 1 year ago
Sorry, turns out it's not that broken after all, after a reboot the axfrdns service started again, however:
Its still not creating the proper entries for dns zone transfers in /var/etc/axfrdns/tcp and not compiling that list into the /var/etc/axfrdns/tcp.cdb
Creating the host entries in the tcp file and manually compiling the cdb fixes the immediate problem.
Not sure where in the script that last part is going wrong.