Comment 26 for bug 1754671
Revision history for this message
| Till Kamppeter (till-kamppeter) wrote | #26 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I have now done the test under [Test Case] in the initial description of this bug report.
I have a completely updated (including -proposed) Bionic machine (real iron, a Lenovo X1 Carbon 2nd gen from 2015) with network-manager 1.10.14-0ubuntu1
I have configured the Canonical VPN, both UK and US. I have turned on only the UK one. It is configured to be used only for the internal destinations on both IPv4 and IPv6.
The system in this configuration I have rebooted to be assure that all processes including the kernel are using the newest software.
Then I have followed the instructions of the test case.
When running "dig <a Canonical-internal host name>" I get immediately an answer with exit code 0 ("echo $?"), so the request was successful.
When I look into the "tcpdump" terminals, the host name gets polled through both interfaces, but naturally the answer only comes from the DNS of the VPN.
So to my understanding the bug is not fixed as the private host name gets also sent to the public DNS.
"systemd-resolve --status" lists the VPN DNS first, as link 4 and afterwards the public DNS as link3.