> No, this is my first attempt with named and dhcpd. Each one seems
> to be fine separately but getting them to talk has been a stumbling
> block.
Then you'll have to share pieces of your configuration, so we can see
what is going on there.
Maybe also share the information that you used to set i
To: greg.st...@sungard.com
Cc: freebsd-questions@freebsd.org
Subject: Re: Release-7.0 named and dhcpd
Hi Greg,
> The desktops that grab an address from the DHCP pool are not getting
> added in for named resolution. I am apparently missing something
> with the communication between
Hi Greg,
> The desktops that grab an address from the DHCP pool are not getting
> added in for named resolution. I am apparently missing something
> with the communication between named and dhcpd. Any help would be
> appreciated.
There are many reasons why the dhcpd cannot communicate with name
I am getting the following messages on a bind server running Release-7.0:
Mar 11 23:05:56 nameserver named[674]: client 192.168.xxx.xxx#49165: update
'domain.local/IN' denied
Mar 11 23:05:56 nameserver dhcpd: if desktop.domain.local IN A rrset doesn't
exist add desktop.domain.local 1800 IN A 19