2 ms·
DHCP will provide a nameserver and search domain for the network you connect to, which will resolve domains in that search domain properly. There is nothing spe
by necovek 5y ago
DHCP will provide a nameserver and search domain for the network you connect to, which will resolve domains in that search domain properly. There is nothing special about that.
With systemd-resolved, the right thing happens out of the box. Without it, you've got to do something arbitrary like you describe.
It's ok to dislike systemd (there are plenty reasons to do so), but if you won't acknowledge things it does well, it's hard to take you seriously.
FWIW, I don't think having a local network (with eg. a NAS drive on it) and connecting to another (VPN) is so uncommon.
- iso1631 5y ago> DHCP will provide a nameserver and search domain for the network you connect to No, it may provide a nameserevr which I may or may not want to use. > which will resolve domains in that search domain properly It may, or may not, provide a search domain. Chances are I'll be using that domain server for all domains, or I'll choose to use my preferred server (4222, 9999 etc) My vpn on my laptop doesn't even use dhcp so not sure how that would apply. > FWIW, I don't think having a local network (with eg. a NAS drive on it) and connecting to another (VPN) is so uncommon. Bridging networks, generally not a good thing.
- necovek 5y agoThat's not bridging networks: you are instead connected to multiple networks simultaneously, whereas in bridging, you make one network over multiple interfaces. As for your configuration, it seems you are connecting to a bunch of misconfigured networks if you want to use your own prefered servers.