From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Sun,  7 Mar 2010 14:59:17 -0800
Message-ID: <621112A569DAE948AD25CCDCF1C075332998F9@dolly.ntdom.cupdx>
From: "Benjamin Huntsman" <BHuntsman@mail2.cu-portland.edu>
To: <9fans@9fans.net>
Subject: [9fans] Plan 9 as local DHCP/DNS server
Topicbox-Message-UUID: e3553716-ead5-11e9-9d60-3106f5b1d025

I'm trying to get a Plan 9 system set up to serve as a DHCP/DNS server =
on my local LAN.
The clients are mostly Windows systems, with some Macs, etc, thrown in.

Here are the relevant bits from /lib/ndb/local:

ipnet=3Dinternal ip=3D10.0.0.0 ipmask 255.255.0.0
    ipsubmask=3D255.255.255.0
    dns=3Dns2.test.local
    dns=3Dns1.test.local
    dnsdomain=3Dtest.local
    ipgw=3D10.0.0.1
    authdom=3Dtest.local auth=3Dns2

dom=3Dtest.local soa=3D
    refresh=3D3600 ttl=3D3600
    ns=3Dns2.test.local
    ns=3Dns1.test.local
    dnsdomain=3Dtest.local
    mb=3Dben@test.local
    mx=3Dmail1.test.local pref=3D20

ip=3D10.0.0.102 sys=3Dns2 dom=3Dns2.test.local
    ether=3D005056b31741

And in /cfg/ns2/cpurc I have:

ip/dhcpd 10.0.0.2 99
ndb/dns -s


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...

Anyone tried using Plan 9's dns and dhcpd with Windows clients and =
gotten this to work?

Many thanks in advance!

-Ben