mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Jan Broer <jasiu.79@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Re: Re: Would love to see reconsideration for domain and search
Date: Fri, 23 Oct 2015 20:03:35 +0200	[thread overview]
Message-ID: <CA+MmhbPws+7xRecu0bC-9meFf2q2mc_mP+2cB0iOtA+UXrfo1Q@mail.gmail.com> (raw)
In-Reply-To: <CA+MmhbNCZ7S8_9euE2rJjMe0S76DM7Lgo5CQvwvt7qOa4V_r+g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 941 bytes --]

> On Thu, Oct 22, 2015 at 10:37:53PM -0700, Tim Hockin wrote:
> > I saw from a different thread that musl doesn't or didn't do TCP
> > fallbacks - is that still the case?  I know we need that for things
> > like large multi-SRV sets (which I do not expect libc to support), and
> > we have some people who have large A sets (which I do expect libc to
> > support).

>Indeed. The only way you can overflow the UDP size limit with the
>records the stub resolver uses is with a max-length CNAME pointing to
>a max or near-max length record with little or no overlap to allow for
>compression.

Most DNS servers are actually well able to send records greater than
512 bytes over UDP. This is part of the EDNS0 DNS extension. I think
it's worth discussing to implement EDNS0 in the musl resolver.
Codewise you just have to set the UDP receive buffer to the desired
size and include an OPT RR in every query indicating the supported max
UDP size.

[-- Attachment #2: Type: text/html, Size: 1184 bytes --]

  parent reply	other threads:[~2015-10-23 18:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23 15:30 Jan Broer
2015-10-23 16:01 ` Tim Hockin
2015-10-23 17:40   ` Jan Broer
2015-10-23 18:02     ` Tim Hockin
2015-10-23 18:03     ` Jan Broer [this message]
2015-10-23 18:29     ` Rich Felker
2015-10-23 21:27       ` Jan Broer

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=CA+MmhbPws+7xRecu0bC-9meFf2q2mc_mP+2cB0iOtA+UXrfo1Q@mail.gmail.com \
    --to=jasiu.79@gmail.com \
    --cc=musl@lists.openwall.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).