This is caused by network-manager pushing ~. as the search domain. This effectively makes resolved ignore the DNS servers I configured. I could fix this by adding Domains=~. to resolved.conf, but I don't know, this does not feel right - network-manager essentially breaks a resolved feature.
** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1812744 Title: resolved uses only per-link dns servers Status in network-manager package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I configured multiple DNS servers in the DNS= option. The manual page says: "DNS requests are sent to one of the listed DNS servers in parallel to suitable per-link DNS servers" What I see however, is that each DNS request is sent twice to the same server, e.g.: connect(15, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 16) = 0 connect(16, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 16) = 0 If a per-link server is pushed by network-manager, it's always that one. Since my per-link server can lag a lot, that is annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1812744/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp