> FWIW there is another weirdness of windows, the windows DHCP server doesn't
> communicate with the DNS server on windows, it expects the client to send an
> Inform packet to the DHCP server telling it of the clients chosen name.
i guess that's the great thing about standards — there are so
many
It looks from my reading from of dhcpd.c that you could just tweek
windows (the registry I assume) and make windows ask for the domain,
in which case dhcpd should supply it.
If you hate this idea then I think the change to add windows specific
dhcp options would be easy - there is already a specia
>> (because it supplies the correct info for non-Plan 9 hosts).
>
>What info did your hosts need that Plan 9's dhcpd didn't supply?
Specifically, Plan 9's dhcpd does not supply a context-specific DNS suffix (ie,
default domain name), which Windows systems need in order to resolve hosts by
short
> (because it supplies the correct info for non-Plan 9 hosts).
What info did your hosts need that Plan 9's dhcpd didn't supply?
Hi!
I'm trying to set up an application(don't ask :) ) on my LAN that
more-or-less requires the ability to perform dynamic updates of DNS. I'm
currently using a Plan 9 system to serve DNS, but DHCP is being served by a
FreeBSD machine (because it supplies the correct info for non-Plan 9 host
