mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Yuri Kanivetsky <yuri.kanivetsky@gmail.com>
Cc: musl@lists.openwall.com
Subject: Re: [musl] getaddrinfo() fails for domains with no AAAA records (regression?)
Date: Tue, 27 Jul 2021 10:41:35 -0400	[thread overview]
Message-ID: <20210727144135.GP13220@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAMhVC3bvaMNyAWeSqaxi5NZPur9u6N1=17C4e5kzdm4S7e6tSQ@mail.gmail.com>

On Tue, Jul 27, 2021 at 05:21:14PM +0300, Yuri Kanivetsky wrote:
> Well, the way it looks... they (registrar) aren't gonna fix this. But
> the problem is only with wildcard RRs, so bearable.
> 
> By the way, do you know which dns servers are buggy, and which are not?

As far as I know, there's no actual DNS software that's open source or
commercially offered that has this kind of severe problem. It only
happens when the hosting provider has rolled their own broken software
or made in-house hacks to existing software to break it.

If your registrar is really this bad, you should probably move or at
least use them only as a registrar (not a DNS host) and delegate the
DNS hosting to someone who doesn't botch it so bad.

Rich



> On Fri, Jul 23, 2021 at 11:45 PM Laurent Bercot
> <ska-dietlibc@skarnet.org> wrote:
> >
> >
> >   I wrote a tool some time ago that was precisely designed to work
> > around buggy DNS servers incorrectly returning NXDOMAIN, precisely
> > because such a need was expressed in Alpine.
> >
> >   This tool is called dnsfunnel, and is available here:
> > https://skarnet.org/software/dnsfunnel/
> >
> >   It is also available in Alpine, in testing/ - it has been rotting there
> > for months because I asked Alpine people to test it in situations
> > involving actual buggy servers (my own infrastructure is not exposed
> > to this problem), but my request apparently got lost in the void.
> >
> >   If there is motivation to actually work around incorrect NXDOMAINs,
> > it may be a good idea to bring this back to life and actually test
> > dnsfunnel in real situations where it could be useful, so it can
> > properly be packaged in Alpine and set up for users who need it.
> >
> > --
> >   Laurent
> >

      reply	other threads:[~2021-07-27 14:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 12:58 Yuri Kanivetsky
2021-07-19 13:22 ` Florian Weimer
2021-07-19 18:51   ` Yuri Kanivetsky
2021-07-19 19:29     ` Shiz
2021-07-19 19:47     ` Érico Nogueira
2021-07-19 21:08   ` Rich Felker
2021-07-19 21:07 ` Olivier A.
2021-07-19 21:12   ` Rich Felker
2021-07-23 20:25     ` Yuri Kanivetsky
2021-07-23 20:33       ` Yuri Kanivetsky
2021-07-23 20:45       ` Laurent Bercot
2021-07-27 14:21         ` Yuri Kanivetsky
2021-07-27 14:41           ` Rich Felker [this message]

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=20210727144135.GP13220@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    --cc=yuri.kanivetsky@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).