> We are reffering to the local stub resolver yes, i understand that, but i'm asking if you are talking about local traffic TO the stub resolver, or traffic FROM the stub resolver to your upstream nameserver.
If you have pcap showing the problem, please attach it. If you're not sure what I'm talking about, then you should do: $ sudo systemctl edit systemd-resolved and in the file editor it opens, add this content: [Service] Environment=SYSTEMD_LOG_LEVEL=debug then save the file and reboot. then try looking up your host again (using the local stub resolver of course). Gather the resolved logs and attach or paste them here. $ journalctl -b -u systemd-resolved --no-pager -- 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
