From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Sun, 7 Mar 2010 19:18:55 -0500 To: 9fans@9fans.net Message-ID: In-Reply-To: <621112A569DAE948AD25CCDCF1C075332998F9@dolly.ntdom.cupdx> References: <621112A569DAE948AD25CCDCF1C075332998F9@dolly.ntdom.cupdx> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Plan 9 as local DHCP/DNS server Topicbox-Message-UUID: e35a836a-ead5-11e9-9d60-3106f5b1d025 > 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