On Mon, 24 Aug 2015 16:56:37 -0600 Devin Reade <[email protected]> wrote: > --On Monday, August 24, 2015 12:27:06 AM +0000 Stuart Henderson > <[email protected]> wrote: > > > Having NFS rely on DNS is not ideal. I don't see why dhcpd would > > need DNS to run at all? > > If you have a 'fixed-address' definition in a 'host' block, and > the fixed-address uses a FQDN rather than an IP, you will have > problems booting the DHCP server if no DNS server is reachable. > IIRC, the DHCP daemon will fail to start and as a consequence > the server takes a lot longer to come up. > > This burned me in the past after cold restart of everything on the > network, where the internal DNS servers come up slower than the > DHCP server. > > A solution of course is to use an IP in the fixed-address definition.
I know the only problem is I am trying to have less moving parts for the configuration as the steps to do become longer and longer when introducing changes and DNS seems like a good place to put name-to-address information ;). If it is not clear: with static IPs "fixed-address" one can register the IP in the DNS conf have dhcpd do a lookup and provide the IP address to the machine. Considering that most other software has rules based on IP etc.. it can make your life easier and things clearer ... I have had this problem since 5.7, with DNS (because I have not gotten around to migrating to the new pair), but nothing that some editing cannot fix. Nevertheless having a machine secure and functioning properly requires time and effort ... and good notes... so every step you take to deviate from the beaten path will result in a beaten head later ... but things are never as-rosy-as-you-might-like, so be it ;) "ce la vie". Cheers, George
