The decision to refuse zone transfer requests was in fact deliberate, as
described here:
https://github.com/systemd/systemd/commit/b30bf55d5c9942f15f27a641c2c34bbb646ec981.
Therefore, I think "Won't Fix" is the appropriate resolution here.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1854976
Title:
systemd-resolved doesn't work with "host -l" / AXFR queries
Status in systemd package in Ubuntu:
Won't Fix
Bug description:
Hello,
some time ago network-manager in Ubuntu switched from dnsmasq to
systemd-resolved.
When network-manager used dnsmasq to handle DNS, one could use "host
-l" to list all the hosts in a DNS zone, something like this:
$ host -l mydomain.lan
mydomain.lan name server mydns.mydomain.lan
host1.mydomain.lan has address x.x.x.x
host2.mydomain.lan has address x.x.x.x
host3.mydomain.lan has address x.x.x.x
host4.mydomain.lan has address x.x.x.x
[...]
That, unfortunately, no longer works since the switch to systemd-resolved, it
always fails like this:
$ host -l mydomain.lan
Host mydomain.lan not found: 4(NOTIMP)
; Transfer failed.
And I think that's because systemd-resolved is "filtering" the AXFR
queries issued by "host -l" (I checked the network traffic with tcdump
and that "NOTIMP" comes from the loopback interface).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1854976/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
