On 12 October 2017 at 14:55, Matthias Fratz <[email protected]> wrote: > As for ubuntu.com, that was only as an example to show a situations when > things break. I really just copied what the original submitter used -- I > should probably have used example.com instead though, that's less > confusing. > > My concrete situation is that the server delivers only inf.uni- > konstanz.de because that's what matches the university's organizational > structure. (And having it changed it is not an option.) I put the other > two (disy.inf.uni-konstanz.de and uni-konstanz.de) in the search path > long ago because I regularly connect to hosts in those domains. Saves a > lot of typing errors, and AFAIK it's not an uncommon use case for the > search path. But this broke DNS resolution for disy.inf.uni-konstanz.de > and uni-konstanz.de (probably because they're not in any per-interface > search path) on upgrade to 17.04, and got me to this bug. > > As far as I can tell now, the bug should only affect users on or > upgrading to zesty who have manually configured a search path using > resolvconf, and artful users who configure one in resolved.conf. That's > clearly a minority of users. > > I certainly agree to the "only send queries to the right nameserver" > part. That makes sense, as does UseDomains and setting it to true by > default. What I find troubling is that it seems to just swallow the > query when there's no interface matching a search path entry. That > doesn't agree with the documentation of either Domains= or UseDomains=, > which both suggest that one can have search paths not associated with an > interface. But I guess that's a bug in the systemd-resolved and not in > Ubuntu, so I'll probably just report it upstream. >
I'd rather report the bug upstream myself, as upstream prefer downstream distributions to curate these things. Clearly, as an end-user you cannot fix DHCP server config if it provides insufficient search paths. So you are saying that you have a.example.com domain configured on the link, with a nameserver W.X.Y.Z which can also resolve b.example.com domains and you want it to do so, and when setting Domains in resolved.conf it does not result in resolving b.example.com domains in addition to a.example.com domains? I'm not sure if this is a bug or a feature =)))))) The right answer is probably to have per-link configuration encoded in netplan/networkd/networkmanager, but that might be annoying to do if one connects to said network over wifi, over usb ethernet on different usb ports, and multiple vlan end-points. As I guess on such a network all of these connections are valid, and all of them will receive incomplete search list and it would be convenient to set a global list. I'll play around with this. -- Regards, Dimitri. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714803 Title: Search list in resolv.conf breaks resolving for that domain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1714803/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
