24 Led
2019
24 Led
'19
8:12
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
(2.7.6).
I configure the knot-dns a slave:
# knotc conf-read
…
acl.id = master
acl[master].address = 5.28.40.220
acl[master].action = notify
remote.id = master
remote[master].address = 5.28.40.220
…
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[26299]: info: [vtnx.net.] notify, incoming,
5.28.40.220@38668: received, serial none
Jan 24 07:53:19 ns1-neu knotd[26299]: info: [vtnx.net.] refresh, outgoing,
5.28.40.220@53: remote serial 1548307450, zone is outdated
Jan 24 07:53:19 ns1-neu knotd[26299]: warning: [vtnx.net.] IXFR, incoming,
5.28.40.220@53: malformed response SOA
Jan 24 07:53:19 ns1-neu knotd[26299]: warning: [vtnx.net.] refresh, remote master not
usable
Jan 24 07:53:19 ns1-neu knotd[26299]: error: [vtnx.net.] refresh, failed (no usable
master)
What about "malformed response SOA"?
Why is this an IXFR and no AXFR?
- Frank
--
Frank Matthieß Mail: frank.matthiess(a)virtion.de
GnuPG: 9F81 BD57 C898 6059 86AA 0E9B 6B23 DE93 01BB 63D1
virtion GmbH Stapenhorster Straße 42b, DE 33615 Bielefeld
Geschäftsführer: Michael Kutzner
Handelsregister HRB 40374, Amtsgericht Bielefeld, USt-IdNr.: DE278312983
24 Led
24 Led
8:33
Hi,
if i try to do the axfr with dig, i got this:
# dig @5.28.40.220 axfr +answer vtnx.net
; <<>> DiG 9.11.3-1ubuntu1.3-Ubuntu <<>> @5.28.40.220 axfr
+answer vtnx.net
; (1 server found)
;; global options: +cmd
vtnx.net. 2560 IN SOA ns1.vtnx.net. hostmaster.vtnx.net. 1548307450 16384 2048 1048576
2560
ns1.vtnx.net. 259200 IN A 5.28.40.220
ns2.vtnx.net. 259200 IN A 5.28.40.222
ns1.vtnx.net. 259200 IN A 5.28.40.220
ns2.vtnx.net. 259200 IN A 5.28.40.222
ns3.vtnx.net. 259200 IN A 5.28.47.254
ns1.vtnx.net. 259200 IN A 5.28.40.220
ns2.vtnx.net. 259200 IN A 5.28.40.222
ns1.vtnx.net. 259200 IN A 5.28.40.220
ns2.vtnx.net. 259200 IN A 5.28.40.222
ns3.vtnx.net. 259200 IN A 5.28.47.254
ns1.vtnx.net. 259200 IN A 5.28.40.220
ns2.vtnx.net. 259200 IN A 5.28.40.222
ns3.vtnx.net. 259200 IN A 5.28.47.254
ns1.vtnx.net. 259200 IN A 5.28.40.220
ns2.vtnx.net. 259200 IN A 5.28.40.222
ns3.vtnx.net. 259200 IN A 5.28.47.254
;; communications error to 5.28.40.220#53: end of file
vtnx.net. 2560 IN SOA ns1.vtnx.net. hostmaster.vtnx.net. 1548307450 16384 2048 1048576
2560
ns1.vtnx.net. 259200 IN A 5.28.40.220
ns2.vtnx.net. 259200 IN A 5.28.40.222
ns1.vtnx.net. 259200 IN A 5.28.40.220
ns2.vtnx.net. 259200 IN A 5.28.40.222
ns3.vtnx.net. 259200 IN A 5.28.47.254
ns1.vtnx.net. 259200 IN A 5.28.40.220
ns2.vtnx.net. 259200 IN A 5.28.40.222
ns1.vtnx.net. 259200 IN A 5.28.40.220
ns2.vtnx.net. 259200 IN A 5.28.40.222
ns3.vtnx.net. 259200 IN A 5.28.47.254
ns1.vtnx.net. 259200 IN A 5.28.40.220
ns2.vtnx.net. 259200 IN A 5.28.40.222
ns3.vtnx.net. 259200 IN A 5.28.47.254
ns1.vtnx.net. 259200 IN A 5.28.40.220
ns2.vtnx.net. 259200 IN A 5.28.40.222
ns3.vtnx.net. 259200 IN A 5.28.47.254
;; communications error to 5.28.40.220#53: end of file
- Frank
--
Frank Matthieß Mail: frank.matthiess(a)virtion.de
GnuPG: 9F81 BD57 C898 6059 86AA 0E9B 6B23 DE93 01BB 63D1
virtion GmbH Stapenhorster Straße 42b, DE 33615 Bielefeld
Geschäftsführer: Michael Kutzner
Handelsregister HRB 40374, Amtsgericht Bielefeld, USt-IdNr.: DE278312983
9:23
Hello Frank,
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 :-)
Daniel
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
(2.7.6).
I configure the knot-dns a slave:
# knotc conf-read
…
acl.id = master
acl[master].address = 5.28.40.220
acl[master].action = notify
remote.id = master
remote[master].address = 5.28.40.220
…
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[26299]: info: [vtnx.net.] notify, incoming,
5.28.40.220@38668: received, serial none
Jan 24 07:53:19 ns1-neu knotd[26299]: info: [vtnx.net.] refresh, outgoing,
5.28.40.220@53: remote serial 1548307450, zone is outdated
Jan 24 07:53:19 ns1-neu knotd[26299]: warning: [vtnx.net.] IXFR, incoming,
5.28.40.220@53: malformed response SOA
Jan 24 07:53:19 ns1-neu knotd[26299]: warning: [vtnx.net.] refresh, remote master not
usable
Jan 24 07:53:19 ns1-neu knotd[26299]: error: [vtnx.net.] refresh, failed (no usable
master)
What about "malformed response SOA"?
Why is this an IXFR and no AXFR?
- Frank
9:31
Hi,
On 2019-01-24 09:23:04, Daniel Salzman wrote:
Hello Frank,
1) You don't need to prepare "empty" zone with the SOA record. It's
initialized automatically along with AXFR.
Ok, that perfect. I'm not aware of it.
I will try it again w/o empty zone.
2) Does tinydns support IXFR? It seems that the server
responds in a strange way.
That's what I'm afraid of.
If you allowed me doing zone transfer, I could look at
it. It's interesting :-)
Please send me your source ipv4 address and i will give you the permission to do
a zonetransfer.
BTW: The used djbdns/tinydns software is version 1.05
- Frank
--
Frank Matthieß Mail: frank.matthiess(a)virtion.de
GnuPG: 9F81 BD57 C898 6059 86AA 0E9B 6B23 DE93 01BB 63D1
virtion GmbH Stapenhorster Straße 42b, DE 33615 Bielefeld
Geschäftsführer: Michael Kutzner
Handelsregister HRB 40374, Amtsgericht Bielefeld, USt-IdNr.: DE278312983
1941
days inactive
1941
days old
3 comments
2 participants
participants (2)
-
Daniel Salzman -
Frank Matthieß