From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] dhcp & metanames
Date: Sun, 7 Mar 2004 08:54:03 -0500 [thread overview]
Message-ID: <88c6e77a3e4ca429414a39724d4fc4c3@plan9.bell-labs.com> (raw)
In-Reply-To: <200403071349.i27DnZru079594@adat.davidashen.net>
[-- Attachment #1: Type: text/plain, Size: 115 bytes --]
It's wrong. Unfortunately, I don't vet the wiki. People put in whatever
accidentally worked. I'll go change it.
[-- Attachment #2: Type: message/rfc822, Size: 3287 bytes --]
From: David Tolpin <dvd@davidashen.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] dhcp & metanames
Date: Sun, 7 Mar 2004 17:49:35 +0400 (AMT)
Message-ID: <200403071349.i27DnZru079594@adat.davidashen.net>
> We ask dhcp for a hostname and a domain. For the latter, dhcp's
> seem to differ in what they give back, i.e., the FQDN of the machine,
> the FQDN domain name that the machine is in, or that FQDN starting
> with a '.'. Ipconfig tries to deal with the situation, clearly
> not well enough. I'll try to do better but, if the server doesn't
> return the hostname, its hard to guess. the dom=.davidashen.net
> clearly indicates that we only got the domain and not the hostname.
> This is a effect of the spread of windows where the hostname is
> always in local storage and diskless boot is not really considered.
I have no Windows server in my network; the dhcp server sends domain
names.
I have only done that (the leading dot) because
http://www.cs.bell-labs.com/wiki/plan9/Mail_configuration/
in the last paragraph says:
This name is generated from either the site enviroment var, or if that is not
set, by appending the sending machines domain to its system name. The domain is
picked up from the dom= attribute from /lib/ndb/local. The dom= attribut should
be of the form dom=.machine.com (NB: leading dot).
If it is wrong, I'll change it to the fqdn.
next prev parent reply other threads:[~2004-03-07 13:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 10:08 Tiit Lankots
2004-03-07 12:58 ` David Presotto
2004-03-07 13:13 ` David Tolpin
2004-03-07 13:23 ` David Presotto
2004-03-07 13:49 ` David Tolpin
2004-03-07 13:54 ` David Presotto [this message]
2004-03-07 13:15 Tiit Lankots
2004-03-07 13:35 ` David Presotto
2004-03-07 13:51 ` David Tolpin
2004-03-07 13:18 Tiit Lankots
2004-03-07 13:53 Tiit Lankots
2004-03-07 13:58 Tiit Lankots
2004-03-07 15:55 ` David Presotto
2004-03-08 14:23 ` Derek Fawcus
2004-03-07 14:04 Tiit Lankots
2004-03-07 14:13 ` David Tolpin
2004-03-07 14:31 Tiit Lankots
2004-03-07 15:31 ` David Tolpin
2004-03-07 15:49 Tiit Lankots
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=88c6e77a3e4ca429414a39724d4fc4c3@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--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).