Re: Requesting Update-Policy Statements Sanity Check, Please

2023-02-04 Thread duluxoz
Thanks Mark - that was the issue :-) I really, really appreciate the help Cheers Dulux-Oz On 04/02/2023 23:21, Mark Andrews wrote: Add DHCID to the list of record types permitted to be updated by the DHCP server. -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe

Re: Requesting Update-Policy Statements Sanity Check, Please

2023-02-04 Thread Mark Andrews
Add DHCID to the list of record types permitted to be updated by the DHCP server. -- Mark Andrews > On 4 Feb 2023, at 21:15, duluxoz wrote: > > Thanks Mark (& Darren & Jan-Piet), > > So I made those changes you suggested (Mark), but I'm still having issues (ie > DHCP leases are not being

Re: Requesting Update-Policy Statements Sanity Check, Please

2023-02-04 Thread duluxoz
Thanks Mark (& Darren & Jan-Piet), So I made those changes you suggested (Mark), but I'm still having issues (ie DHCP leases are not being added to the DNS zones), so I've included my Bind9 config: ~~~ acl "bogusnets" {     !"internal_hosts";     0.0.0.0/8;     10.0.0.0/8;     

Re: Requesting Update-Policy Statements Sanity Check, Please

2023-02-03 Thread Mark Andrews
You need to replace the rule type with something more appropriate for the type of update being preformed. For the updates made by the DHCP server I would use “zonesub”. “name” is fine for LetsEncrypt. update-policy {grant update-key zonesub A ;}; update-policy {grant

Re: Requesting Update-Policy Statements Sanity Check, Please

2023-02-03 Thread Mark Andrews
> On 3 Feb 2023, at 21:47, Darren Ankney wrote: > > You would probably need to attach your entire named.conf file (with > sensitive bits (keys and the like) redacted and perhaps subnets > obscured to examples such as 192.0.2.0/24, for example) before anyone > would be able to help you. > >

Re: Requesting Update-Policy Statements Sanity Check, Please

2023-02-03 Thread Jan-Piet Mens
You would probably need to attach your entire named.conf file (with sensitive bits (keys and the like) redacted named-checkconf -px is your friend: prints out the named.conf and included files in canonical form if no errors were detected and obscures shared secrets by replacing them with

Re: Requesting Update-Policy Statements Sanity Check, Please

2023-02-03 Thread Darren Ankney
You would probably need to attach your entire named.conf file (with sensitive bits (keys and the like) redacted and perhaps subnets obscured to examples such as 192.0.2.0/24, for example) before anyone would be able to help you. That being said, your update policy statements don't look correct to

Requesting Update-Policy Statements Sanity Check, Please

2023-02-02 Thread duluxoz
Hi All, I'm pretty new to configuring Bind and so it would be great if someone(s) could just check my code re: the update-policy zone command(s) below - thanks in advance. For the first zone (a regular internal forward-lookup zone) I'd like to be able to update (from Kea via ddns) the zone