From: Matthias Urlichs <matthias@urlichs.de>
To: wireguard@lists.zx2c4.com
Subject: Re: Add local DNS forwarder to Windows client
Date: Tue, 10 Nov 2020 17:04:53 +0100 [thread overview]
Message-ID: <83e213d7-44d5-485b-3213-9bd00016b011@urlichs.de> (raw)
In-Reply-To: <CADJb3qRapO=3-fuyeS6iC8EnM34TxTxpZBr1uyVhhTmfjgOmwA@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 854 bytes --]
On 10.11.20 16:38, Yves Goergen wrote:
> This is not a solution to my problem. And I still refuse to believe
> that my problem is exotic. Every home LAN has this.
Which "every" home LAN has two resolvers, none of them being
authoritative? Mine certainly doesn't.
> So if your first DNS is up but has no reply for your query,
Define "no reply". There's more than one kind of non-reply here. If the
no-reply you're talking about is actually a "doesn't exist" reply, then
Windows is perfectly correct not to ask anybody else for a second
opinion. The net is flooded with stupid (if not to say "terminally
brain-dead") DNS queries as it is, ask any DNS provider; no need to add
even more of these.
Please elucidate why you can't use a fixed prefix like ".home" or ".lan"
for these. Cf. RFC 2606.
--
-- Matthias Urlichs
[-- Attachment #1.1.2: OpenPGP_0x72CF8E5E25B4C293_and_old_rev.asc --]
[-- Type: application/pgp-keys, Size: 48415 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2020-11-10 16:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 10:31 Yves Goergen
2020-11-10 8:14 ` Tomcsanyi, Domonkos
2020-11-10 8:44 ` Der PCFreak
2020-11-10 15:38 ` Yves Goergen
2020-11-10 16:04 ` Matthias Urlichs [this message]
2020-11-10 18:08 ` Lech Perczak
2020-11-15 18:42 ` Yves Goergen
2020-11-15 21:10 ` Matthias Urlichs
2020-11-15 21:43 ` "Tomcsányi, Domonkos"
2020-11-11 7:36 ` Der PCFreak
[not found] ` <CADJb3qTGhm8a=aAA8_6ZgEHHFyBZyOch_GRBkC1p4yym28fN-Q@mail.gmail.com>
2020-11-10 10:47 ` Fwd: " Yves Goergen
2020-11-10 22:24 ` Tomcsanyi, Domonkos
2020-11-11 11:31 Stefan Puch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83e213d7-44d5-485b-3213-9bd00016b011@urlichs.de \
--to=matthias@urlichs.de \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).