[Touch-packages] [Bug 1854976] Re: systemd-resolved doesn't work with "host -l" / AXFR queries

2023-06-12 Thread Nick Rosbrook
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

[Touch-packages] [Bug 1854976] Re: systemd-resolved doesn't work with "host -l" / AXFR queries

2020-02-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1854976] Re: systemd-resolved doesn't work with "host -l" / AXFR queries

2019-12-03 Thread ghomem
Hi, I work with Jose Manuel Santamaria Lema. Thank you for taking your time to review. Perhaps we should be a little cautious in regards what we call "normal" and "reasonable". During the last 20+ years of Linux people able were to do "host -l" against servers that were configured to allow so -

[Touch-packages] [Bug 1854976] Re: systemd-resolved doesn't work with "host -l" / AXFR queries

2019-12-03 Thread Steve Langasek
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