[knot-dns-users] Migration from djbdns/tinydns to knot-dns.cz
daniel.salzman at nic.cz
Thu Jan 24 09:23:04 CET 2019
1) You don't need to prepare "empty" zone with the SOA record. It's initialized automatically along with AXFR.
2) Does tinydns support IXFR? It seems that the server responds in a strange way.
If you allowed me doing zone transfer, I could look at it. It's interesting :-)
On 1/24/19 8:12 AM, Frank Matthieß wrote:
> Hello all,
> we want to migrate to a state of the art nameserver software.
> Our startingpoint is djbdns/tinydns.
> Our first step should be to to use zone transfer from tinydns to knot-dns
> I configure the knot-dns a slave:
> # knotc conf-read
> acl.id = master
> acl[master].address = 184.108.40.206
> acl[master].action = notify
> remote.id = master
> remote[master].address = 220.127.116.11
> zone.domain = vtnx.net.
> zone[vtnx.net.].master = master
> zone[vtnx.net.].acl = master
> and add a initial soa rr for that domain:
> vtnx.net. 0 SOA ns1.vtnx.net. hostmaster.vtnx.net. 1 16384 2048 1048576 2560
> This the exact soa of the running vtnx.net domain, but a diffrent serial.
> After triggering the notification from the master, i got this logging:
> Jan 24 07:53:19 ns1-neu knotd: info: [vtnx.net.] notify, incoming, 18.104.22.168 at 38668: received, serial none
> Jan 24 07:53:19 ns1-neu knotd: info: [vtnx.net.] refresh, outgoing, 22.214.171.124 at 53: remote serial 1548307450, zone is outdated
> Jan 24 07:53:19 ns1-neu knotd: warning: [vtnx.net.] IXFR, incoming, 126.96.36.199 at 53: malformed response SOA
> Jan 24 07:53:19 ns1-neu knotd: warning: [vtnx.net.] refresh, remote master not usable
> Jan 24 07:53:19 ns1-neu knotd: error: [vtnx.net.] refresh, failed (no usable master)
> What about "malformed response SOA"?
> Why is this an IXFR and no AXFR?
> - Frank
More information about the knot-dns-users