From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Plan 9 as local DHCP/DNS server
Date: Sun, 7 Mar 2010 19:18:55 -0500 [thread overview]
Message-ID: <a5ce2140939fff050bb73798fcbc5e24@brasstown.quanstro.net> (raw)
In-Reply-To: <621112A569DAE948AD25CCDCF1C075332998F9@dolly.ntdom.cupdx>
> Now, it hands out DHCP addresses to my Windows clients, and, I can ping ns2.test.local by name, but, cannot ping the short name, ns2.
> This is because the client doesn't receive a "Connection-specific DNS suffix" from dhcpd. (You can see this in from "ipconfig /all").
> I thought that is what the dnsdomain tuple was for, but apparently not? ns1 is a FreeBSD host on which I can run ISC DHCPD, and it correctly hands Windows clients a connection-specific DNS suffix, but I'd rather keep both DNS and DHCP on a Plan 9 system...
grepping the source, dns does dnsdomain like this
but dhcpd doesn't know anything about it. i'd
appreicate a patch myself. dhcpd needs to be
capable of supporting non-plan 9 clients.
- erik
prev parent reply other threads:[~2010-03-08 0:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-07 22:59 Benjamin Huntsman
2010-03-08 0:18 ` erik quanstrom [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=a5ce2140939fff050bb73798fcbc5e24@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).