mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Re: Would love to see reconsideration for domain and search
Date: Mon, 26 Oct 2015 11:35:11 -0400	[thread overview]
Message-ID: <20151026153511.GE8645@brightrain.aerifal.cx> (raw)
In-Reply-To: <20151026012642.GA5627@newbook>

On Sun, Oct 25, 2015 at 06:26:43PM -0700, Isaac Dunham wrote:
> On Sat, Oct 24, 2015 at 06:02:15PM -0400, Rich Felker wrote:
> > The only place adding search support might negatively impact existing
> > musl users is by causing hostnames with no dots to be queried with the
> > (often useless and unwanted) default domain set by dhcp before
> > failing. My preference would probably be having musl default to
> > ndots=0 rather than ndots=1 so that search has to be enabled
> > explicitly. Are there any reasons this would be undesirable?
> 
> Could you explain what this all would mean to someone who has only a
> general understanding of how DNS works, a home network, and a desire
> to set up a local DNS server?
> 
> I have a couple use-cases in mind, which I think involve either the
> "search" or "domain" keywords in resolv.conf; I'll describe them in case
> they pertain.
> 
> 1: the university I attended had a bunch of resources which were available
> as sub-domains. The way DHCP/DNS/resolv.conf was set up, local sites
> (for example, http://myweb.csuchico.edu/) were available using only the
> bare subdomain (in the same example, http://myweb/); I forget whether
> they used "domain" or "search" for this. This was something I
> appreciated.

Yes, this is what adding search domain support would allow. Note that
with ndots=1, "myweb" would work, but "myweb.math" would not.

> 2: On my home network (configured via DHCP, no DNS server yet), I have a
> network printer that advertises itself using a name in the general format
> of MFC0000DEADBEEF (where 0000DEADBEEF is the MAC address, stripped of
> separators). It uses this hostname for DHCP and avahi.
> However, this name is only available for avahi clients like cups; I
> want to be able to access it by the same name from non-avahi programs
> like 'ping', 'links', etcetera, since it's rather annoying to have a
> 'magic' name that usually works in your printing daemon, but no way
> to map it to an IP for any troupleshooting/configuration tools.
> 
> Currently, I've got it set up so the printer has a static lease and I
> thus know the IP, but I want to use DNS because that's the only way all
> tools on all computers on the network will automatically know that
> MFC0000DEADBEEF is (for example) IP 192.168.255.255.
> It would be rather annoying to have some tools where I can use that name,
> and some where I need to specify "mfc0000deadbeef.local" instead.

Doing this requires dunning a local nameserver that joins the avahi
(mdns, I think) results under some domain you control with the global
dns namespace. I suspect dnsmasq or one of the other dns servers made
for home network use can do this but I haven't checked. In principle
it's even possible with BIND and some scripting to query mdns and use
the results to update dynamic dns entries but that's rather ugly.

Rich


  reply	other threads:[~2015-10-26 15:35 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22 21:24 Tim Hockin
2015-10-22 21:56 ` Rich Felker
2015-10-22 22:36   ` Tim Hockin
2015-10-22 23:00     ` Josiah Worcester
2015-10-22 23:37       ` Tim Hockin
2015-10-23  4:27         ` Rich Felker
2015-10-23  5:13           ` Tim Hockin
2015-10-23  5:31             ` Rich Felker
2015-10-23  5:37               ` Tim Hockin
2015-10-23  6:00                 ` Rich Felker
2015-10-23  6:04                   ` Tim Hockin
2016-01-29  0:57                 ` Rich Felker
2015-10-27  0:30               ` Rich Felker
2015-10-27  0:37                 ` Tim Hockin
2015-10-27  0:45                   ` Rich Felker
2015-10-27  8:11                 ` u-uy74
2015-11-28 22:48                 ` Jan Broer
2015-11-28 23:20                   ` Rich Felker
2015-11-29  3:06                     ` Jan Broer
2016-01-29  0:58                   ` Rich Felker
2015-10-26  2:14           ` Re: Would not " John Levine
2015-10-26  5:14             ` Tim Hockin
2015-10-26 16:16               ` Rich Felker
2015-10-26 17:41                 ` John Levine
2015-10-26 18:08                   ` Rich Felker
2015-10-23  8:12       ` Re: Would " u-uy74
2015-10-23  9:35         ` Laurent Bercot
2015-10-23 12:23           ` Laurent Bercot
2015-10-23 15:57           ` Tim Hockin
2015-10-23  5:26 ` Kurt H Maier
2015-10-24 21:33   ` Tim Hockin
2015-10-24 21:57     ` Kurt H Maier
2015-10-24 23:31       ` Rich Felker
2015-10-24 22:02     ` Rich Felker
2015-10-24 22:32       ` Tim Hockin
2015-10-25  8:20       ` u-uy74
2015-10-25 13:06       ` Jan Broer
2015-10-25 13:19         ` u-uy74
2015-10-25 13:39           ` Jan Broer
2015-10-25 14:08             ` u-uy74
2015-10-25 19:08         ` Rich Felker
2015-10-26  1:26       ` Isaac Dunham
2015-10-26 15:35         ` Rich Felker [this message]
2015-10-23 15:30 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=20151026153511.GE8645@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --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).