> 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
