* MacOS DNS Search Domain
@ 2020-11-20 1:26 Sune Mølgaard
2020-12-07 14:41 ` Yoshimi Takano
0 siblings, 1 reply; 2+ messages in thread
From: Sune Mølgaard @ 2020-11-20 1:26 UTC (permalink / raw)
To: wireguard
Hi all,
Being in the process of deploying, and being very happy with both
answers to questions, and, generally, performance, ease of
administration etc., I seem to be facing a slight problem.
Using wg-quick, via SystemD, on Linux, I can have multiple, in my case
two, "DNS =" entries in my client config, one with an IP address of the
DNS server to utilise, and the second with a domain name, to be applied
as the "DNS Search Domain".
This works as expected.
Under MacOS, using the GUI client from the app store, "DNS =" entries
with domain names are not accepted (is this a bug or expected
behaviour?), but I have found suggestions to issue `networksetup
-setsearchdomain XX YOUR-SEARCH.DOMAIN`
(https://www.reddit.com/r/WireGuard/comments/dlh65m/resolving_search_domains_on_a_mac/).
Substituting the correct entries for XX and YOUR-SEARCH.DOMAIN with
correct values work, inasmuch as `networksetup -getsearchdomain XX`
indicates that the correct DNS Search Domain is set correctly for the
interface, but it does not, however, seem to work IRL, meaning that
requests to a mere hostname, as opposed to an FQDN, within the search
domain result in lookup failures.
First of all, I would like to know if anyone knows how to make DNS
Search Domain work in conjunction with MacOS.
Secondly, I would like to pose the question of whether there is a bug,
code- or documentation-wise regarding how to make it work, and, thirdly,
I would like to ask if the official, MacOS, GUI client could,
conceivably, be made to accept "DNS =" entries with domain names, making
them work like wg-quick on Linux, meaning setting those entries as DNS
Search Domains.
Best regards,
Sune Mølgaard
--
How many observe Christ's birthday! How few, his precepts! O! 'tis
easier to keep holidays than commandments.
- Benjamin Franklin
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: MacOS DNS Search Domain
2020-11-20 1:26 MacOS DNS Search Domain Sune Mølgaard
@ 2020-12-07 14:41 ` Yoshimi Takano
0 siblings, 0 replies; 2+ messages in thread
From: Yoshimi Takano @ 2020-12-07 14:41 UTC (permalink / raw)
To: wireguard
Hello
I just wanted to mention that I ran in to the same issue.
The MacOS client rejects DNS settings containing non-IP hostnames such as
DNS = 1.2.3.4, example.search.domain.com
with the error "Interface’s DNS servers must be a list of
comma-separated IP addresses".
According to the wg-quick man page, non-IP hostnames (to be interpreted
as search domains) are allowed for the DNS setting.
The Windows client accepts these fine.
Best regards
Yoshimi
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-12-07 23:52 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-11-20 1:26 MacOS DNS Search Domain Sune Mølgaard
2020-12-07 14:41 ` Yoshimi Takano
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).