Hi,
this PR fixes two problem with assigning dns domains for vpn interface:
At my company checkpoint returns dns servers with trailing whitespaces. Current snx-rs implementation pushes them to resolvectl in following format:
DNS Domain: ~some.domain ~\032other.domain
I modified deserialize for QuotedStringList to trim whitespaces from Vec members.
systemd-resolved has two modes to serve DNS Domain: settings:
routing domains - records prefixed with ~. If resolved gets request to resolve domain with such suffix, it only forwards request to dns server of corresponding interface.
search domains - records not prefixed with ~. Such domains are also used to suffix single-label domain names. Like if resolved gets request git it can transform it to git.some.domain and resolve it's address. More detailed description is here
It's quite common to have single-label domain links in corporate systems, so using search domains seems logical hear. This PR removes addition of ~ in front of domain suffix. However if one wants to use routing domain, it can be achieved through --search-domains parameter usage.
Hi, this PR fixes two problem with assigning dns domains for vpn interface:
DNS Domain: ~some.domain ~\032other.domain
I modified deserialize forQuotedStringList
to trim whitespaces from Vec members.DNS Domain:
settings:~
. If resolved gets request to resolve domain with such suffix, it only forwards request to dns server of corresponding interface.~
. Such domains are also used to suffix single-label domain names. Like if resolved gets requestgit
it can transform it togit.some.domain
and resolve it's address. More detailed description is hereIt's quite common to have single-label domain links in corporate systems, so using search domains seems logical hear. This PR removes addition of
~
in front of domain suffix. However if one wants to use routing domain, it can be achieved through--search-domains
parameter usage.