[yadifa-users] slave AXFR not working with yadifad 2.3.9 on FreeBSD
Eric Diaz Fernandez
eric.diaz.fernandez at eurid.eu
Wed Apr 10 10:15:29 CEST 2019
We have found what causes the issue you have reported.
It appears that FreeBSD refuses to send UDP messages with a specified source-address when the interface is not bound to ANY.
A fix for FreeBSD has been written and will be included in the next release of YADIFA.
Until the aforementioned fix is made available, listening to 0.0.0.0 should fix the issue,
Eric Diaz Fernandez
On 19/03/2019 09:48, Hiroo Ono (小野寛生) wrote:
> I am trying to use yadifa as primary and secondary name server.
> Setting primary server went well, but it did not for the secondary.
> The software and the OS is yadifa 2.3.9 / FreeBSD stable/12.
> I set up the slave zone in the configuration file.
> When the server starts, the log file shows:
> 2019-03-19 17:11:21.741354 | server | I | slave: oikumene.net. AXFR
> query to the master
> 2019-03-19 17:11:21.741481 | server | I | axfr: oikumene.net.:
> transfer will be signed with key 'master-slave.'
> 2019-03-19 17:11:21.741944 | server | E | slave: axfr query error
> for domain oikumene.net. from master at 188.8.131.52#53: Invalid
> 2019-03-19 17:11:21.741969 | server | W | slave: 184.108.40.206#53
> master failed to answer for domain oikumene.net.: retrying
> 2019-03-19 17:11:21.742067 | server | E | database: oikumene.net.:
> failed to download the zone: Invalid argument
> tcpdump of the packets to and from port 53 shows nothing. AXFR query did not
> start at all.
> I traced it with a debugger.
> from the function axfr_query (in sbin/yadifad/axfr.c line 181),
> the function tcp_input_output_stream_connect_host_address (in
> lib/dnscore/src/tcp_io_stream.c line 253) is called.
> then it calls tcp_input_output_stream_connect_sockaddr (in
> tcp_io_stream.c line 147),
> and fails at connect() (line 194).
> the errno was 2 (ENOENT: The named socket does not exist)
> Is there something wrong with my configuration?
> Or where should I take a look to solve the problem?
> I tailored down the configuration file to below (channes and loggers
> section omitted.) The problem described above persists.
> chroot off
> daemonize false
> log-path /var/log/yadifa
> pid-file /var/run/yadifad.pid
> data-path /var/yadifa
> keys-path /var/yadifa/keys
> xfr-path /var/yadifa/xfr
> listen 220.127.116.11
> allow-notify master
> log-from-start true
> domain oikumene.net
> file slaves/oikumene.net.zone
> type slave
> master 18.104.22.168 key master-slave
> include /root/admin/conf/yadifa-keys.conf
> master 22.214.171.124
> slave 126.96.36.199
> yadifa-users mailing list
> yadifa-users at mailinglists.yadifa.eu
More information about the yadifa-users