Closing that bug since the submitter debugged it and found out it was
not a systemd issue. Those who have other DNS problems please register a
new bug
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs
I have a similar issue (dns server running on a DSL router). The router
assigns hostnames ending in .home
Seems to break resolution for the systemd-resolved as well (only working
sometimes).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Any news on this?
I have many hosts with this error.
My server is a plain Bind.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795913
Title:
Systemd Resolver works unreliable to local DNS Names
To
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795913
Title:
Sy
After some more digging I found this behavior roots from the DNS
Resolver running on the Router (a Turris Omnia)
Local hosts get a name xxx.home.example.com from fixed DHCP leases and
the knot resolver (kresd) on the Turris responds with the local IPv4
Address for this hosts.
Queries for IPv6 Add
