From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] dns not running
Date: Sun, 3 Dec 2000 16:08:08 -0500 [thread overview]
Message-ID: <20001203210809.62D03199F0@mail.cse.psu.edu> (raw)
>you always have an IP address 127.0.0.1 and running
>a dns is always a good idea as long as it implements
>a cache as per BIND. speeds up DNS lookups.
actually, we assign no special meaning to the 127 network in our stack.
You thinking Unix?
> i've never liked ip/ipconfig. i like the dns config
> files, but was horrified to learn that it finds the
> hostname (never documented) by ethernet address.
Dns doesn't use the ether address for anything.
The only place we connect an ethernet address and
an ip one is in dhcpd. We use the ether address to
identify a system that's bootping or dhcping. That's
only if you're trying to give a static address to a
system. Since we run our systems diskless (or as close
as we can get) that's the only bit of information that
a bootping system reliably has to identify itself.
ndb/cs will use the ether address to figure out
the system name only if all of the above are true
1) /env/sysname doesn't contain a name
2) the ip address doesn't map to a name in the database
3) dhcp didn't leave a name in /net/ndb
next reply other threads:[~2000-12-03 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-03 21:08 presotto [this message]
2000-12-03 21:27 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2000-12-04 17:45 forsyth
2000-12-04 22:05 ` William Staniewicz
2000-12-03 21:32 presotto
2000-12-03 1:16 Russ Cox
2000-12-03 20:52 ` Boyd Roberts
2000-12-04 17:28 ` William Staniewicz
2000-12-02 10:30 William Staniewicz
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=20001203210809.62D03199F0@mail.cse.psu.edu \
--to=presotto@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).