To repro on azure instance:
ddstreet@lp1886128:~$ systemd-resolve --status | grep Servers
DNS Servers: 168.63.129.16
ddstreet@lp1886128:~$ dig +retries=0 +timeout=1 +short +tcp @168.63.129.16
toomany100.ddstreet.org
;; connection timed out; no servers could be reached
;; Connection to 168.63.129.16#53(168.63.129.16) for toomany100.ddstreet.org
failed: timed out.
tcp does work with external dns servers, e.g.:
ddstreet@lp1886128:~$ dig +retries=0 +timeout=1 +short +tcp @8.8.8.8
toomany100.ddstreet.org | head -5
10.254.201.0
10.254.201.1
10.254.201.18
10.254.201.19
10.254.201.2
note that the TCP packets to 168.63.129.16 do not make it out of the instance;
they don't show up in the tcpdump at all, although TCP packets to 168.63.129.15
or 168.63.129.17 *do* show up. So there is something specific to that ip
address that's causing TCP packets to get lost inside the instance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886128
Title:
systemd-resolved does not resolve address due to udp payload size.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1886128/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
