** Attachment added: "Wireshark capture of successful resolution, showing IPv6
stuff happening"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1716976/+attachment/4997138/+files/Screenshot%20from%202017-10-26%2018-36-23.png
** Summary changed:
- DNS resolver silently switches to an
This is still happening with 17.10 final. I have been digging a bit and
found something that makes me think that this is a caching / IPv6 issue.
Attached is the screenshot of a Wireshark capture of the DNS packets on
all interfaces on the affected machine (the IP address of the machine is
Sorry, sorry, it does still happen.
--
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/1716976
Title:
DNS resolver silently switches to an unknown DNS server
Status in
It looks like this has been fixed, it is not occurring anymore.
--
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/1716976
Title:
DNS resolver silently switches to an unknown
Output of systemd-resolve --status when the problem does not occur
** Attachment added: "sr-ok.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1716976/+attachment/4954625/+files/sr-ok.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Output of systemd-resolve --status when the problem occurs
** Attachment added: "sr-bad.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1716976/+attachment/4954624/+files/sr-bad.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I attached the output of systemd-resolve --status in both cases. There
is no difference. In both cases it says the DNS server is 192.168.0.2
(our local resolver), although it seems it is using another, external
DNS server after a while.
Indeed the cache seems to be flushed when changing
The caches should be flushed each time machine changes networking =/
does your system e.g. bounce between "public dns wifi network" and a
"internal dns ethernet network"?
A full output of $ systemd-resolve --status -> would be helpful to see.
Especially "when everything works correctly" and "when
Maybe interesting: systemd-resolve --status eth2 always reports the
correct, internal DNS server, even though names are incorrectly resolved
to their public IPs (I tried resolving with both dig and systemd-
resolve).
gpothier@tadzim3:~$ systemd-resolve --status eth2
Link 3 (eth2)
Current
9 matches
Mail list logo
