[yadifa-users] slave AXFR not working with yadifad 2.3.9 on FreeBSD

[Eric Diaz Fernandez]

Dear Sir,


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,


Best regards,


Eric Diaz Fernandez


On 19/03/2019 09:48, Hiroo Ono (小野寛生) wrote:
> hello,
>
> 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 61.192.162.206#53: Invalid
> argument
> 2019-03-19 17:11:21.741969 | server   | W | slave: 61.192.162.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.
> ----------------------------
> <main>
>         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                  160.16.110.128
>
>         allow-notify            master
>         log-from-start          true
> </main>
>
> <zone>
>         domain          oikumene.net
>         file            slaves/oikumene.net.zone
>         type            slave
>         master          61.192.162.206 key master-slave
> </zone>
>
> include         /root/admin/conf/yadifa-keys.conf
>
> <acl>
>         master          61.192.162.206
>         slave           160.16.110.128
> </acl>
> -------------------------------------------------
> _______________________________________________
> yadifa-users mailing list
> yadifa-users at mailinglists.yadifa.eu
> http://www.yadifa.eu/mailman/listinfo/yadifa-users