An AXFR is not a normal end-user operation, and for most public DNS
servers these queries are denied for security reasons. I don't think
it's reasonable to expect an AXFR query to work against your local
forwarding resolver; I think it was accidental that this worked under
dnsmasq.
You should be able to execute a 'host -l' against an actual
authoritative nameserver for the domain, if the nameserver is configured
to support this, by listing its name as an additional argument to 'host'
i.e.:
host -l mydomain.lan mydns.mydomain.lan
So I think this bug should be closed as 'wontfix', but I'm leaving it
for the systemd maintainers to make that determination.
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854976
Title:
systemd-resolved doesn't work with "host -l" / AXFR queries
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1854976/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
