On Sunday, 30 July 2017 16:49:35 BST Barry Scott wrote:
> On Wednesday, 26 July 2017 05:27:54 BST Tim wrote:
>
> > Tim:
>
>
> Thanks for the suggestions, they did not cover anything I had not already
> checked.
>
> I took to debugging dhcpd to see what was up and found that there is
> a error
On Wednesday, 26 July 2017 05:27:54 BST Tim wrote:
> Tim:
Thanks for the suggestions, they did not cover anything I had not already
checked.
I took to debugging dhcpd to see what was up and found that there is
a error message that appears if I compile in debug for DNS updates.
DDNS: ddns.c(160
Tim:
I think you need to tell us if your updates were on the server,
clients, or both. And what is not working. Clients not being issued IPs?
Barry Scott:
I recall having to patch things up when the client id algorithm changed a about
4 years ago. Has that happened again?
I don't know, but
> On 25 Jul 2017, at 06:48, Tim wrote:
Thanks for the reply TIm.
>
> On 24/7/2017 12:19 am, Barry Scott wrote:
>> I have a dhcod/bind combination working very nicely registering host name
>> from DHCP into DNS.
>> But after the update to F26 ddns stopped working. I see no error messages
>>
On 24/7/2017 12:19 am, Barry Scott wrote:
I have a dhcod/bind combination working very nicely registering host name from
DHCP into DNS.
But after the update to F26 ddns stopped working. I see no error messages but
did notice
that my named update log file no logger sees any messages logged into
I have a dhcod/bind combination working very nicely registering host name from
DHCP into DNS.
But after the update to F26 ddns stopped working. I see no error messages but
did notice
that my named update log file no logger sees any messages logged into it.
Is this a known problem? Or do I need
