© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Any five second delay in name resolution is most likely caused by this open bug in systemd-resolved:
https:/
The root cause is a delay when resolved has to downgrade the feature set of its requests to upstream DNS servers. It correctly discovers a compatible feature set, but doesn't implement the discovered feature set until the next new query attempt. The retry logic is supposed to handle this, but the bug is that it goes crazy and retries with a known not working feature set until the max retry counter is hit. Then 5 seconds later, a new attempt is made, and works perfectly, the compatible feature set is used on the first attempt of the new query.