From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
To: "cygwin-patches@cygwin.com" <cygwin-patches@cygwin.com>
Cc: Corinna Vinschen <corinna-cygwin@cygwin.com>
Subject: RE: [PATCH] CYGWIN: Fix resolver debugging output
Date: Mon, 1 Feb 2021 15:46:50 +0000 [thread overview]
Message-ID: <DM8PR09MB70952B27AFDF02848ABB50C7A5B69@DM8PR09MB7095.namprd09.prod.outlook.com> (raw)
In-Reply-To: <20210201150209.GP375565@calimero.vinschen.de>
> Except, the value has no meaning for ipv6.
It'll print all 0's :-) But:
minires does not make use of the _ext field. It does use the conventional nsaddr_list (which is IPv4),
but only if Windows native DNS API is not used: "osquery"(aka use_os)=0.
For debugging purposes, that is enough and very convenient (yet the output needed some tune-up, which I suggested in my patch).
But for practical purposes, only Windows API should be used in regular applications (which is the default, anyways, since
/etc/resolv.conf is not routinely provided, so "osquery=1" implicitly).
I'm not sure if improvements to use _ext by the minires own code would be any beneficial.
Having said that, AAAA replies should be made understood by the minires-if-os shim code
(and I can provide a patch for that, too).
next prev parent reply other threads:[~2021-02-01 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 19:29 Anton Lavrentiev
2021-02-01 10:34 ` Corinna Vinschen
2021-02-01 14:23 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-02-01 15:02 ` Corinna Vinschen
2021-02-01 15:46 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C] [this message]
2021-02-01 19:02 ` Corinna Vinschen
2021-02-02 18:02 ` Brian Inglis
2021-02-02 19:38 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
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=DM8PR09MB70952B27AFDF02848ABB50C7A5B69@DM8PR09MB7095.namprd09.prod.outlook.com \
--to=lavr@ncbi.nlm.nih.gov \
--cc=corinna-cygwin@cygwin.com \
--cc=cygwin-patches@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).