-
Notifications
You must be signed in to change notification settings - Fork 407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[axfrdns] Fails to initialize new zones due to servfail #2998
Labels
Comments
Ping @hnrgrgr, the maintainer of the AXFR+DDNS provider. |
I can't get Knot to initialize an empty zone using $ cat knot.conf
server:
listen: [::@53]
async-start: on
log:
- target: stderr
any: debug
acl:
- id: allow_all
address: ["0.0.0.0/0", "::/0"]
action: [transfer, notify, update]
zone:
# From https://www.knot-dns.cz/docs/3.4/singlehtml/index.html#example-2
- domain: test.internal.
zonefile-sync: -1
zonefile-load: none
journal-content: all
acl: allow_all
$ podman run --rm --pull=newer --volume=./knot.conf:/config/knot.conf:ro,z --publish=[::1]:53:53/udp docker.io/cznic/knot:latest /usr/sbin/knotd &
2025-01-03T06:48:17+0000 info: Knot DNS 3.4.3 starting
2025-01-03T06:48:17+0000 info: loaded configuration file '/config/knot.conf', mapsize 500 MiB
2025-01-03T06:48:17+0000 info: using UDP reuseport, incoming TCP Fast Open
2025-01-03T06:48:17+0000 info: binding to interface ::@53
2025-01-03T06:48:17+0000 info: loading 1 zones
2025-01-03T06:48:17+0000 info: [test.internal.] zone will be loaded
2025-01-03T06:48:17+0000 info: starting server
2025-01-03T06:48:17+0000 info: [test.internal.] zone not found
2025-01-03T06:48:17+0000 error: [test.internal.] zone event 'load' failed (not exists)
2025-01-03T06:48:17+0000 info: control, binding to '/rundir/knot.sock'
2025-01-03T06:48:17+0000 info: server started in the foreground, PID 1
$ dig +noall +question +answer @localhost CH TXT version.bind.
;version.bind. CH TXT
version.bind. 0 CH TXT "Knot DNS 3.4.3"
$ echo 'server localhost
zone test.internal.
update add test.internal. 300 IN SOA localhost. invalid.invalid. 300 300 300 300 300
update add test.internal. 300 IN NS localhost.
update add test.internal. 300 IN TXT "test"
send
answer' | nsupdate -d
Sending update to ::1#53
Outgoing update query:
;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 55401
;; flags:; ZONE: 1, PREREQ: 0, UPDATE: 3, ADDITIONAL: 0
;; ZONE SECTION:
;test.internal. IN SOA
;; UPDATE SECTION:
test.internal. 300 IN SOA localhost. invalid.invalid. 300 300 300 300 300
test.internal. 300 IN NS localhost.
test.internal. 300 IN TXT "test"
2025-01-03T06:48:38+0000 debug: [test.internal.] ACL, allowed, action update, remote fd11:214b:df5::834@49595 UDP
Reply from update query:
;; ->>HEADER<<- opcode: UPDATE, status: SERVFAIL, id: 55401
;; flags: qr; ZONE: 1, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0
;; ZONE SECTION:
;test.internal. IN SOA
Answer:
;; ->>HEADER<<- opcode: UPDATE, status: SERVFAIL, id: 55401
;; flags: qr; ZONE: 1, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0
;; ZONE SECTION:
;test.internal. IN SOA
$ dig +noall +question +answer +comments @localhost SOA test.internal.
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 46749
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; EDE: 24 (Invalid Data)
;; QUESTION SECTION:
;test.internal. IN SOA |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
NOTE: Have a general question? You'll get a better response on the dnscontrol-discuss email list!
Describe the bug
Using AXFR on a freshly configured zone, that does not have yet any zonedata expectedly fails with rcode2 (SERVFAIL), and therefore cannot be initialized from dnscontrol.
dnscontrol:
knot:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A nameserver without zonedata will return SERVFAIL for the zone. Ideally dnscontrol would allow applying the initial zonedata.
DNS Provider
Additional context
It starts working, once I create zonedata on the nameserver in any way:
The text was updated successfully, but these errors were encountered: