subject:"Re\: Integrating ISC\-DHCP with\/ Bind \(and eventually Kea\)"

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

2026-02-08 Thread Philip Prindeville via bind-users

Is this going anywhere?



> On Dec 8, 2025, at 9:53 PM, Mark Andrews  wrote:
> 
> https://gitlab.isc.org/isc-projects/bind9/-/merge_requests/11314

-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list.

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

2025-12-14 Thread Philip Prindeville via bind-users

Here’s an update.  I’ve built Bind 9.20.15 with this patch backported.  And 
installed on OpenWRT.  I’ve also build ISC-DHCP with this PR merged:

https://github.com/openwrt/packages/pull/28072

My understanding was that with patch 11314 included, I wouldn’t need:

disable-empty-zone 168.192.in-addr.arpa;

but it seems I do anyway.  Do I need to apply this to a more recent version of 
Bind?  Are there other configuration lines I need to enable it?

Thanks




> On Dec 8, 2025, at 9:53 PM, Mark Andrews  wrote:
> 
> https://gitlab.isc.org/isc-projects/bind9/-/merge_requests/11314
> 
>> On 9 Dec 2025, at 08:06, Philip Prindeville  
>> wrote:
>> 
>> And if you have a patch that encompasses that “long term fix”, I’m happy to 
>> test it.
>> 
>> 
>> 
>>> On Dec 6, 2025, at 11:02 PM, Philip Prindeville via bind-users 
>>>  wrote:
>>> 
>>> Sorry, when you say “the long term fix …” is that a source code fix to 
>>> Bind?  Or a configuration fix I need to make to allow this?
>>> 
>>> 
>>> 
 On Dec 1, 2025, at 2:58 PM, Mark Andrews  wrote:
 
 Almost certainly this will be a clash between the existing automatic empty 
 zone and
 the 'rndc addzone' for 168.192.in-addr.arpa.  The long term fix will be to 
 have named
 check if the added zone is an automatic empty zone and to allow 'rndc 
 addzone’ to
 replace it.  In the mean time I would just add 168.192.in-addr.arpa to 
 named.conf or add
 'disable-empty-zone 168.192.in-addr.arpa;’
 
 Mark
 
> On 2 Dec 2025, at 07:50, Philip Prindeville via bind-users 
>  wrote:
> 
> [ Bcc: David and Noah ]
> 
> Hi,
> 
> I’m the maintainer for Kea and ISC-DHCP on OpenWRT.  The scripting to 
> take the UCI configuration files for DHCP and mangle them into Bind zone 
> transfers is here:
> 
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L136-L186
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L274
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L276
> 
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L569
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L575
> 
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L581-L606
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L694
> 
> and the glue in Bind is here:
> 
> https://github.com/openwrt/packages/blob/master/net/bind/files/bind/named.conf#L8-L9
> 
> An example is running locally here, where I have “redfish-solutions.com 
> ” and “168.192.in-addr.arpa” as the 
> domains I serve.
> 
> ; Generated by /etc/init.d/dhcpd at Mon Dec  1 13:14:10 MST 2025
> 
> ttl 3600
> 
> update add Bedroom.redfish-solutions.com. IN A 192.168.5.5
> send
> update add 5.5.168.192.in-addr.arpa. IN PTR Bedroom.redfish-solutions.com.
> send
> update add Penthouse.redfish-solutions.com. IN A 192.168.5.6
> send
> update add 6.5.168.192.in-addr.arpa. IN PTR 
> Penthouse.redfish-solutions.com.
> send
> update add switch1.redfish-solutions.com. IN A 192.168.6.3
> send
> update add 3.6.168.192.in-addr.arpa. IN PTR switch1.redfish-solutions.com.
> send
> update add usw-24-poe.redfish-solutions.com. IN A 192.168.6.4
> send
> update add 4.6.168.192.in-addr.arpa. IN PTR 
> usw-24-poe.redfish-solutions.com.
> send
> update add usw-aggregation.redfish-solutions.com. IN A 192.168.6.5
> send
> update add 5.6.168.192.in-addr.arpa. IN PTR 
> usw-aggregation.redfish-solutions.com.
> send
> update add uap-ac-pro-upstairs.redfish-solutions.com. IN A 192.168.6.6
> send
> update add 6.6.168.192.in-addr.arpa. IN PTR 
> uap-ac-pro-upstairs.redfish-solutions.com.
> send
> update add uap-u6-lr-mainfloor.redfish-solutions.com. IN A 192.168.6.7
> send
> update add 7.6.168.192.in-addr.arpa. IN PTR 
> uap-u6-lr-mainfloor.redfish-solutions.com.
> send
> update add uap-ac-pro-basement.redfish-solutions.com. IN A 192.168.6.8
> send
> update add 8.6.168.192.in-addr.arpa. IN PTR 
> uap-ac-pro-basement.redfish-solutions.com.
> send
> update add bluray3d.redfish-solutions.com. IN A 192.168.6.13
> send
> update add 13.6.168.192.in-addr.arpa. IN PTR 
> bluray3d.redfish-solutions.com.
> send
> update add bluray.redfish-solutions.com. IN A 192.168.6.14
> send
> update add 14.6.168.192.in-addr.arpa. IN PTR bluray.redfish-solutions.com.
> send
> update add macbook3.redfish-solutions.com. IN A 192.168.6.17
> send
> update add 17.6.168.192.in-addr.arpa. IN PTR 
> macbook3.redfish-solutions.com.
> send
> update add charlottes-iwatch.redfish-solutions.com. IN A 192.168.

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

2025-12-10 Thread Philip Prindeville via bind-users

Hmm…

Trying the patch.

On startup, “rndc zonestatus” returns ‘1’, so I know the zone doesn’t exist, 
and I have to “addzone” it.  Later, I try to modify it on-the-fly, and 
“zonestatus” tells me it’s an existing zone, so I “modzone” instead:


Dec 10 15:20:28 OpenWrt2 named[21743]: received control channel command 'freeze'
Dec 10 15:20:28 OpenWrt2 named[21743]: freezing all zones: success
Dec 10 15:20:28 OpenWrt2 named[21743]: received control channel command 
'zonestatus redfish-solutions.com'
Dec 10 15:20:29 OpenWrt2 named[21743]: received control channel command 
'addzone redfish-solutions.com {
Dec 10 15:20:29 OpenWrt2 named[21743]: zone redfish-solutions.com/IN: journal 
rollforward failed: journal out of sync with zone
Dec 10 15:20:29 OpenWrt2 named[21743]: zone redfish-solutions.com/IN: not 
loaded due to errors.
Dec 10 15:20:29 OpenWrt2 named[21743]: addzone failed; reverting.
Dec 10 15:20:29 OpenWrt2 named[21743]: received control channel command 
'zonestatus 168.192.in-addr.arpa'
Dec 10 15:20:30 OpenWrt2 named[21743]: received control channel command 
'modzone 168.192.in-addr.arpa {
Dec 10 15:20:30 OpenWrt2 named[21743]: updated zone 168.192.in-addr.arpa in 
view _default via modzone
Dec 10 15:20:30 OpenWrt2 named[21743]: received control channel command 'thaw'
Dec 10 15:20:30 OpenWrt2 named[21743]: thawing all zones: success
Dec 10 15:20:31 OpenWrt2 named[21743]: client @0x7fac4a55ac00 
127.0.0.1#33741/key local-ddns: update failed: com: not authoritative for 
update zone (NOTAUTH)
Dec 10 15:20:31 OpenWrt2 named[21743]: client @0x7fac47e26800 
127.0.0.1#45353/key local-ddns: update '168.192.IN-ADDR.ARPA/IN' denied
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac47e26800 
127.0.0.1#35877/key local-ddns: update failed: com: not authoritative for 
update zone (NOTAUTH)
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac47e26800 
127.0.0.1#34759/key local-ddns: update '168.192.IN-ADDR.ARPA/IN' denied
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac4954b000 
127.0.0.1#39257/key local-ddns: update failed: com: not authoritative for 
update zone (NOTAUTH)
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac4a55ac00 
127.0.0.1#35861/key local-ddns: update '168.192.IN-ADDR.ARPA/IN' denied
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac47e26800 
127.0.0.1#38837/key local-ddns: update failed: com: not authoritative for 
update zone (NOTAUTH)
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac47e26800 
127.0.0.1#42777/key local-ddns: update '168.192.IN-ADDR.ARPA/IN' denied
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac48c17c00 
127.0.0.1#34499/key local-ddns: update failed: com: not authoritative for 
update zone (NOTAUTH)
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac47e26800 
127.0.0.1#41759/key local-ddns: update '168.192.IN-ADDR.ARPA/IN' denied
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac47e26800 
127.0.0.1#40575/key local-ddns: update failed: com: not authoritative for 
update zone (NOTAUTH)
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac4a55ac00 
127.0.0.1#43543/key local-ddns: update '168.192.IN-ADDR.ARPA/IN' denied
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac4954b000 
127.0.0.1#38711/key local-ddns: update failed: com: not authoritative for 
update zone (NOTAUTH)
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac48c17c00 
127.0.0.1#45797/key local-ddns: update '168.192.IN-ADDR.ARPA/IN' denied
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac4954b000 
127.0.0.1#40577/key local-ddns: update failed: com: not authoritative for 
update zone (NOTAUTH)
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac4954b000 
127.0.0.1#42649/key local-ddns: update '168.192.IN-ADDR.ARPA/IN' denied
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac4a55ac00 
127.0.0.1#42639/key local-ddns: update failed: com: not authoritative for 
update zone (NOTAUTH)
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac4954b000 
127.0.0.1#41337/key local-ddns: update '168.192.IN-ADDR.ARPA/IN' denied
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac48c17c00 
127.0.0.1#35377/key local-ddns: update failed: com: not authoritative for 
update zone (NOTAUTH)
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac4a55ac00 
127.0.0.1#43625/key local-ddns: update '168.192.IN-ADDR.ARPA/IN' denied
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac4a55ac00 
127.0.0.1#36305/key local-ddns: update failed: com: not authoritative for 
update zone (NOTAUTH)
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac47e26800 
127.0.0.1#34807/key local-ddns: update '168.192.IN-ADDR.ARPA/IN' denied
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac47e26800 
127.0.0.1#45203/key local-ddns: update failed: com: not authoritative for 
update zone (NOTAUTH)
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac48c17c00 
127.0.0.1#39545/key local-ddns: update '168.192.IN-ADDR.ARPA/IN' denied
Dec 10 15:20:32 OpenWrt2 named[21743]: client @0x7fac48c17c00 
127.0.0.1#36839/key local-ddns: upda

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

2025-12-08 Thread Mark Andrews

https://gitlab.isc.org/isc-projects/bind9/-/merge_requests/11314

> On 9 Dec 2025, at 08:06, Philip Prindeville  
> wrote:
> 
> And if you have a patch that encompasses that “long term fix”, I’m happy to 
> test it.
> 
> 
> 
>> On Dec 6, 2025, at 11:02 PM, Philip Prindeville via bind-users 
>>  wrote:
>> 
>> Sorry, when you say “the long term fix …” is that a source code fix to Bind? 
>>  Or a configuration fix I need to make to allow this?
>> 
>> 
>> 
>>> On Dec 1, 2025, at 2:58 PM, Mark Andrews  wrote:
>>> 
>>> Almost certainly this will be a clash between the existing automatic empty 
>>> zone and
>>> the 'rndc addzone' for 168.192.in-addr.arpa.  The long term fix will be to 
>>> have named
>>> check if the added zone is an automatic empty zone and to allow 'rndc 
>>> addzone’ to
>>> replace it.  In the mean time I would just add 168.192.in-addr.arpa to 
>>> named.conf or add
>>> 'disable-empty-zone 168.192.in-addr.arpa;’
>>> 
>>> Mark
>>> 
 On 2 Dec 2025, at 07:50, Philip Prindeville via bind-users 
  wrote:

 [ Bcc: David and Noah ]

 Hi,

 I’m the maintainer for Kea and ISC-DHCP on OpenWRT.  The scripting to take 
 the UCI configuration files for DHCP and mangle them into Bind zone 
 transfers is here:

 https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L136-L186
 https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L274
 https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L276

 https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L569
 https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L575

 https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L581-L606
 https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L694

 and the glue in Bind is here:

 https://github.com/openwrt/packages/blob/master/net/bind/files/bind/named.conf#L8-L9

 An example is running locally here, where I have “redfish-solutions.com 
 ” and “168.192.in-addr.arpa” as the domains 
 I serve.

 ; Generated by /etc/init.d/dhcpd at Mon Dec  1 13:14:10 MST 2025

 ttl 3600

 update add Bedroom.redfish-solutions.com. IN A 192.168.5.5
 send
 update add 5.5.168.192.in-addr.arpa. IN PTR Bedroom.redfish-solutions.com.
 send
 update add Penthouse.redfish-solutions.com. IN A 192.168.5.6
 send
 update add 6.5.168.192.in-addr.arpa. IN PTR 
 Penthouse.redfish-solutions.com.
 send
 update add switch1.redfish-solutions.com. IN A 192.168.6.3
 send
 update add 3.6.168.192.in-addr.arpa. IN PTR switch1.redfish-solutions.com.
 send
 update add usw-24-poe.redfish-solutions.com. IN A 192.168.6.4
 send
 update add 4.6.168.192.in-addr.arpa. IN PTR 
 usw-24-poe.redfish-solutions.com.
 send
 update add usw-aggregation.redfish-solutions.com. IN A 192.168.6.5
 send
 update add 5.6.168.192.in-addr.arpa. IN PTR 
 usw-aggregation.redfish-solutions.com.
 send
 update add uap-ac-pro-upstairs.redfish-solutions.com. IN A 192.168.6.6
 send
 update add 6.6.168.192.in-addr.arpa. IN PTR 
 uap-ac-pro-upstairs.redfish-solutions.com.
 send
 update add uap-u6-lr-mainfloor.redfish-solutions.com. IN A 192.168.6.7
 send
 update add 7.6.168.192.in-addr.arpa. IN PTR 
 uap-u6-lr-mainfloor.redfish-solutions.com.
 send
 update add uap-ac-pro-basement.redfish-solutions.com. IN A 192.168.6.8
 send
 update add 8.6.168.192.in-addr.arpa. IN PTR 
 uap-ac-pro-basement.redfish-solutions.com.
 send
 update add bluray3d.redfish-solutions.com. IN A 192.168.6.13
 send
 update add 13.6.168.192.in-addr.arpa. IN PTR 
 bluray3d.redfish-solutions.com.
 send
 update add bluray.redfish-solutions.com. IN A 192.168.6.14
 send
 update add 14.6.168.192.in-addr.arpa. IN PTR bluray.redfish-solutions.com.
 send
 update add macbook3.redfish-solutions.com. IN A 192.168.6.17
 send
 update add 17.6.168.192.in-addr.arpa. IN PTR 
 macbook3.redfish-solutions.com.
 send
 update add charlottes-iwatch.redfish-solutions.com. IN A 192.168.6.18
 send
 update add 18.6.168.192.in-addr.arpa. IN PTR 
 charlottes-iwatch.redfish-solutions.com.
 send
 update add kuiper-macbookpro.redfish-solutions.com. IN A 192.168.6.19
 send
 update add 19.6.168.192.in-addr.arpa. IN PTR 
 kuiper-macbookpro.redfish-solutions.com.
 send
 update add iphone16-philip.redfish-solutions.com. IN A 192.168.6.20
 send
 update add 20.6.168.192.in-addr.arpa. IN PTR 
 iphone16-philip.redfish-solutions.com.
 send
 update add iwatch-emily.redfish-solutions.com. IN A 192.168.6.22
 send
 update add 22.6.168.192.in-addr.arpa. IN PTR

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

2025-12-06 Thread Philip Prindeville via bind-users

Sorry, when you say “the long term fix …” is that a source code fix to Bind?  
Or a configuration fix I need to make to allow this?



> On Dec 1, 2025, at 2:58 PM, Mark Andrews  wrote:
> 
> Almost certainly this will be a clash between the existing automatic empty 
> zone and
> the 'rndc addzone' for 168.192.in-addr.arpa.  The long term fix will be to 
> have named
> check if the added zone is an automatic empty zone and to allow 'rndc 
> addzone’ to
> replace it.  In the mean time I would just add 168.192.in-addr.arpa to 
> named.conf or add
> 'disable-empty-zone 168.192.in-addr.arpa;’
> 
> Mark
> 
>> On 2 Dec 2025, at 07:50, Philip Prindeville via bind-users 
>>  wrote:
>> 
>> [ Bcc: David and Noah ]
>> 
>> Hi,
>> 
>> I’m the maintainer for Kea and ISC-DHCP on OpenWRT.  The scripting to take 
>> the UCI configuration files for DHCP and mangle them into Bind zone 
>> transfers is here:
>> 
>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L136-L186
>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L274
>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L276
>> 
>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L569
>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L575
>> 
>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L581-L606
>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L694
>> 
>> and the glue in Bind is here:
>> 
>> https://github.com/openwrt/packages/blob/master/net/bind/files/bind/named.conf#L8-L9
>> 
>> An example is running locally here, where I have “redfish-solutions.com 
>> ” and “168.192.in-addr.arpa” as the domains I 
>> serve.
>> 
>> ; Generated by /etc/init.d/dhcpd at Mon Dec  1 13:14:10 MST 2025
>> 
>> ttl 3600
>> 
>> update add Bedroom.redfish-solutions.com. IN A 192.168.5.5
>> send
>> update add 5.5.168.192.in-addr.arpa. IN PTR Bedroom.redfish-solutions.com.
>> send
>> update add Penthouse.redfish-solutions.com. IN A 192.168.5.6
>> send
>> update add 6.5.168.192.in-addr.arpa. IN PTR Penthouse.redfish-solutions.com.
>> send
>> update add switch1.redfish-solutions.com. IN A 192.168.6.3
>> send
>> update add 3.6.168.192.in-addr.arpa. IN PTR switch1.redfish-solutions.com.
>> send
>> update add usw-24-poe.redfish-solutions.com. IN A 192.168.6.4
>> send
>> update add 4.6.168.192.in-addr.arpa. IN PTR usw-24-poe.redfish-solutions.com.
>> send
>> update add usw-aggregation.redfish-solutions.com. IN A 192.168.6.5
>> send
>> update add 5.6.168.192.in-addr.arpa. IN PTR 
>> usw-aggregation.redfish-solutions.com.
>> send
>> update add uap-ac-pro-upstairs.redfish-solutions.com. IN A 192.168.6.6
>> send
>> update add 6.6.168.192.in-addr.arpa. IN PTR 
>> uap-ac-pro-upstairs.redfish-solutions.com.
>> send
>> update add uap-u6-lr-mainfloor.redfish-solutions.com. IN A 192.168.6.7
>> send
>> update add 7.6.168.192.in-addr.arpa. IN PTR 
>> uap-u6-lr-mainfloor.redfish-solutions.com.
>> send
>> update add uap-ac-pro-basement.redfish-solutions.com. IN A 192.168.6.8
>> send
>> update add 8.6.168.192.in-addr.arpa. IN PTR 
>> uap-ac-pro-basement.redfish-solutions.com.
>> send
>> update add bluray3d.redfish-solutions.com. IN A 192.168.6.13
>> send
>> update add 13.6.168.192.in-addr.arpa. IN PTR bluray3d.redfish-solutions.com.
>> send
>> update add bluray.redfish-solutions.com. IN A 192.168.6.14
>> send
>> update add 14.6.168.192.in-addr.arpa. IN PTR bluray.redfish-solutions.com.
>> send
>> update add macbook3.redfish-solutions.com. IN A 192.168.6.17
>> send
>> update add 17.6.168.192.in-addr.arpa. IN PTR macbook3.redfish-solutions.com.
>> send
>> update add charlottes-iwatch.redfish-solutions.com. IN A 192.168.6.18
>> send
>> update add 18.6.168.192.in-addr.arpa. IN PTR 
>> charlottes-iwatch.redfish-solutions.com.
>> send
>> update add kuiper-macbookpro.redfish-solutions.com. IN A 192.168.6.19
>> send
>> update add 19.6.168.192.in-addr.arpa. IN PTR 
>> kuiper-macbookpro.redfish-solutions.com.
>> send
>> update add iphone16-philip.redfish-solutions.com. IN A 192.168.6.20
>> send
>> update add 20.6.168.192.in-addr.arpa. IN PTR 
>> iphone16-philip.redfish-solutions.com.
>> send
>> update add iwatch-emily.redfish-solutions.com. IN A 192.168.6.22
>> send
>> update add 22.6.168.192.in-addr.arpa. IN PTR 
>> iwatch-emily.redfish-solutions.com.
>> send
>> update add lucs-laptop.redfish-solutions.com. IN A 192.168.6.23
>> send
>> update add 23.6.168.192.in-addr.arpa. IN PTR 
>> lucs-laptop.redfish-solutions.com.
>> send
>> update add queenies-switch.redfish-solutions.com. IN A 192.168.6.24
>> send
>> update add 24.6.168.192.in-addr.arpa. IN PTR 
>> queenies-switch.redfish-solutions.com.
>> send
>> update add queenies-switch-lite.redfish-solutions.com. IN A 192.168.6.25
>> send
>> update add 25.6.168.192.in-addr.arpa. IN PTR 
>> queenies-switch-lite.redfish-solutions.com.
>>

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

2025-12-02 Thread Ben Scott


On 12/2/25 15:18, Philip Prindeville via bind-users wrote:

On Dec 2, 2025, at 12:37 AM, Ondřej Surý  wrote:
Nope. Automatic empty zones are kind of special (both configuration- and 
code-wise).


Not sure I understand the difference between how “redfish-solutions.com” is 
created and “168.192.in-addr.arpa”.


  BIND's built-in automatic empty zones are fundamentally different 
from "normal" zones (those loaded from a zone database or transfer). 
The code handles them as a special case.  It's not just a zone file 
that's hard-coded into the program.


  If you really want to get into gory details, grep for and 
DNS_ZONEOPT_AUTOEMPTY and DNS_ZONESTATE_AUTOMATIC in the BIND source 
code.  But this is a level of detail you almost certainly do not need.  :-)


  The following article has more information about the auto zones 
(although it does not get into the implementation, just purpose and 
configuration):


https://kb.isc.org/docs/aa-00800

  -- Ben

--
Any opinions expressed in this message are those of the author alone.
All information is provided without warranty of any kind.

--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list.

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

2025-12-02 Thread Philip Prindeville via bind-users

> On Dec 2, 2025, at 12:37 AM, Ondřej Surý  wrote:
> 
> 
>> On 2. 12. 2025, at 5:40, Philip Prindeville via bind-users 
>>  wrote:
>> 
>> That the domain exists but it’s empty?
> 
> Nope. Automatic empty zones are kind of special (both configuration- and 
> code-wise).
> 

Not sure I understand the difference between how “redfish-solutions.com” is 
created and “168.192.in-addr.arpa”.  They both go through the exact same steps.

Maybe there’s default behavior that differs?

In any case, I’m using “modzone” now and both zones can be created on startup 
and reloaded on restart.

-Philip

-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list.

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

2025-12-01 Thread Ondřej Surý

> On 2. 12. 2025, at 5:40, Philip Prindeville via bind-users 
>  wrote:
> 
> That the domain exists but it’s empty?

Nope. Automatic empty zones are kind of special (both configuration- and 
code-wise).

--
Ondřej Surý (He/Him)
[email protected]

My working hours and your working hours may be different. Please do not feel 
obligated to reply outside your normal working hours.

-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list.

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

2025-12-01 Thread Philip Prindeville via bind-users



> On Dec 1, 2025, at 5:12 PM, Mark Andrews  wrote:
> 
> 
> 
>> On 2 Dec 2025, at 10:16, Philip Prindeville 
>>  wrote:
>> 
>> I tried that and it worked. Thanks.
>> 
>> Dumb question… what if we did a “modzone” instead of an “addzone”?
> 
> Modzone works with previously added zones.


Wasn’t that the issue?  That the domain exists but it’s empty?

-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list.

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

2025-12-01 Thread Mark Andrews



> On 2 Dec 2025, at 10:16, Philip Prindeville 
>  wrote:
> 
> I tried that and it worked. Thanks.
> 
> Dumb question… what if we did a “modzone” instead of an “addzone”?

Modzone works with previously added zones.

>> On Dec 1, 2025, at 2:58 PM, Mark Andrews  wrote:
>> 
>> Almost certainly this will be a clash between the existing automatic empty 
>> zone and
>> the 'rndc addzone' for 168.192.in-addr.arpa.  The long term fix will be to 
>> have named
>> check if the added zone is an automatic empty zone and to allow 'rndc 
>> addzone’ to
>> replace it.  In the mean time I would just add 168.192.in-addr.arpa to 
>> named.conf or add
>> 'disable-empty-zone 168.192.in-addr.arpa;’
>> 
>> Mark
>> 
>>> On 2 Dec 2025, at 07:50, Philip Prindeville via bind-users 
>>>  wrote:
>>> 
>>> [ Bcc: David and Noah ]
>>> 
>>> Hi,
>>> 
>>> I’m the maintainer for Kea and ISC-DHCP on OpenWRT.  The scripting to take 
>>> the UCI configuration files for DHCP and mangle them into Bind zone 
>>> transfers is here:
>>> 
>>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L136-L186
>>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L274
>>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L276
>>> 
>>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L569
>>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L575
>>> 
>>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L581-L606
>>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L694
>>> 
>>> and the glue in Bind is here:
>>> 
>>> https://github.com/openwrt/packages/blob/master/net/bind/files/bind/named.conf#L8-L9
>>> 
>>> An example is running locally here, where I have “redfish-solutions.com 
>>> ” and “168.192.in-addr.arpa” as the domains 
>>> I serve.
>>> 
>>> ; Generated by /etc/init.d/dhcpd at Mon Dec  1 13:14:10 MST 2025
>>> 
>>> ttl 3600
>>> 
>>> update add Bedroom.redfish-solutions.com. IN A 192.168.5.5
>>> send
>>> update add 5.5.168.192.in-addr.arpa. IN PTR Bedroom.redfish-solutions.com.
>>> send
>>> update add Penthouse.redfish-solutions.com. IN A 192.168.5.6
>>> send
>>> update add 6.5.168.192.in-addr.arpa. IN PTR Penthouse.redfish-solutions.com.
>>> send
>>> update add switch1.redfish-solutions.com. IN A 192.168.6.3
>>> send
>>> update add 3.6.168.192.in-addr.arpa. IN PTR switch1.redfish-solutions.com.
>>> send
>>> update add usw-24-poe.redfish-solutions.com. IN A 192.168.6.4
>>> send
>>> update add 4.6.168.192.in-addr.arpa. IN PTR 
>>> usw-24-poe.redfish-solutions.com.
>>> send
>>> update add usw-aggregation.redfish-solutions.com. IN A 192.168.6.5
>>> send
>>> update add 5.6.168.192.in-addr.arpa. IN PTR 
>>> usw-aggregation.redfish-solutions.com.
>>> send
>>> update add uap-ac-pro-upstairs.redfish-solutions.com. IN A 192.168.6.6
>>> send
>>> update add 6.6.168.192.in-addr.arpa. IN PTR 
>>> uap-ac-pro-upstairs.redfish-solutions.com.
>>> send
>>> update add uap-u6-lr-mainfloor.redfish-solutions.com. IN A 192.168.6.7
>>> send
>>> update add 7.6.168.192.in-addr.arpa. IN PTR 
>>> uap-u6-lr-mainfloor.redfish-solutions.com.
>>> send
>>> update add uap-ac-pro-basement.redfish-solutions.com. IN A 192.168.6.8
>>> send
>>> update add 8.6.168.192.in-addr.arpa. IN PTR 
>>> uap-ac-pro-basement.redfish-solutions.com.
>>> send
>>> update add bluray3d.redfish-solutions.com. IN A 192.168.6.13
>>> send
>>> update add 13.6.168.192.in-addr.arpa. IN PTR bluray3d.redfish-solutions.com.
>>> send
>>> update add bluray.redfish-solutions.com. IN A 192.168.6.14
>>> send
>>> update add 14.6.168.192.in-addr.arpa. IN PTR bluray.redfish-solutions.com.
>>> send
>>> update add macbook3.redfish-solutions.com. IN A 192.168.6.17
>>> send
>>> update add 17.6.168.192.in-addr.arpa. IN PTR macbook3.redfish-solutions.com.
>>> send
>>> update add charlottes-iwatch.redfish-solutions.com. IN A 192.168.6.18
>>> send
>>> update add 18.6.168.192.in-addr.arpa. IN PTR 
>>> charlottes-iwatch.redfish-solutions.com.
>>> send
>>> update add kuiper-macbookpro.redfish-solutions.com. IN A 192.168.6.19
>>> send
>>> update add 19.6.168.192.in-addr.arpa. IN PTR 
>>> kuiper-macbookpro.redfish-solutions.com.
>>> send
>>> update add iphone16-philip.redfish-solutions.com. IN A 192.168.6.20
>>> send
>>> update add 20.6.168.192.in-addr.arpa. IN PTR 
>>> iphone16-philip.redfish-solutions.com.
>>> send
>>> update add iwatch-emily.redfish-solutions.com. IN A 192.168.6.22
>>> send
>>> update add 22.6.168.192.in-addr.arpa. IN PTR 
>>> iwatch-emily.redfish-solutions.com.
>>> send
>>> update add lucs-laptop.redfish-solutions.com. IN A 192.168.6.23
>>> send
>>> update add 23.6.168.192.in-addr.arpa. IN PTR 
>>> lucs-laptop.redfish-solutions.com.
>>> send
>>> update add queenies-switch.redfish-solutions.com. IN A 192.168.6.24
>>> send
>>> update add 24.6.168.192.in-addr.arpa. IN PTR 
>>> queenies-switch.re

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

2025-12-01 Thread Philip Prindeville via bind-users

I tried that and it worked. Thanks.

Dumb question… what if we did a “modzone” instead of an “addzone”?


> On Dec 1, 2025, at 2:58 PM, Mark Andrews  wrote:
> 
> Almost certainly this will be a clash between the existing automatic empty 
> zone and
> the 'rndc addzone' for 168.192.in-addr.arpa.  The long term fix will be to 
> have named
> check if the added zone is an automatic empty zone and to allow 'rndc 
> addzone’ to
> replace it.  In the mean time I would just add 168.192.in-addr.arpa to 
> named.conf or add
> 'disable-empty-zone 168.192.in-addr.arpa;’
> 
> Mark
> 
>> On 2 Dec 2025, at 07:50, Philip Prindeville via bind-users 
>>  wrote:
>> 
>> [ Bcc: David and Noah ]
>> 
>> Hi,
>> 
>> I’m the maintainer for Kea and ISC-DHCP on OpenWRT.  The scripting to take 
>> the UCI configuration files for DHCP and mangle them into Bind zone 
>> transfers is here:
>> 
>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L136-L186
>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L274
>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L276
>> 
>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L569
>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L575
>> 
>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L581-L606
>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L694
>> 
>> and the glue in Bind is here:
>> 
>> https://github.com/openwrt/packages/blob/master/net/bind/files/bind/named.conf#L8-L9
>> 
>> An example is running locally here, where I have “redfish-solutions.com 
>> ” and “168.192.in-addr.arpa” as the domains I 
>> serve.
>> 
>> ; Generated by /etc/init.d/dhcpd at Mon Dec  1 13:14:10 MST 2025
>> 
>> ttl 3600
>> 
>> update add Bedroom.redfish-solutions.com. IN A 192.168.5.5
>> send
>> update add 5.5.168.192.in-addr.arpa. IN PTR Bedroom.redfish-solutions.com.
>> send
>> update add Penthouse.redfish-solutions.com. IN A 192.168.5.6
>> send
>> update add 6.5.168.192.in-addr.arpa. IN PTR Penthouse.redfish-solutions.com.
>> send
>> update add switch1.redfish-solutions.com. IN A 192.168.6.3
>> send
>> update add 3.6.168.192.in-addr.arpa. IN PTR switch1.redfish-solutions.com.
>> send
>> update add usw-24-poe.redfish-solutions.com. IN A 192.168.6.4
>> send
>> update add 4.6.168.192.in-addr.arpa. IN PTR usw-24-poe.redfish-solutions.com.
>> send
>> update add usw-aggregation.redfish-solutions.com. IN A 192.168.6.5
>> send
>> update add 5.6.168.192.in-addr.arpa. IN PTR 
>> usw-aggregation.redfish-solutions.com.
>> send
>> update add uap-ac-pro-upstairs.redfish-solutions.com. IN A 192.168.6.6
>> send
>> update add 6.6.168.192.in-addr.arpa. IN PTR 
>> uap-ac-pro-upstairs.redfish-solutions.com.
>> send
>> update add uap-u6-lr-mainfloor.redfish-solutions.com. IN A 192.168.6.7
>> send
>> update add 7.6.168.192.in-addr.arpa. IN PTR 
>> uap-u6-lr-mainfloor.redfish-solutions.com.
>> send
>> update add uap-ac-pro-basement.redfish-solutions.com. IN A 192.168.6.8
>> send
>> update add 8.6.168.192.in-addr.arpa. IN PTR 
>> uap-ac-pro-basement.redfish-solutions.com.
>> send
>> update add bluray3d.redfish-solutions.com. IN A 192.168.6.13
>> send
>> update add 13.6.168.192.in-addr.arpa. IN PTR bluray3d.redfish-solutions.com.
>> send
>> update add bluray.redfish-solutions.com. IN A 192.168.6.14
>> send
>> update add 14.6.168.192.in-addr.arpa. IN PTR bluray.redfish-solutions.com.
>> send
>> update add macbook3.redfish-solutions.com. IN A 192.168.6.17
>> send
>> update add 17.6.168.192.in-addr.arpa. IN PTR macbook3.redfish-solutions.com.
>> send
>> update add charlottes-iwatch.redfish-solutions.com. IN A 192.168.6.18
>> send
>> update add 18.6.168.192.in-addr.arpa. IN PTR 
>> charlottes-iwatch.redfish-solutions.com.
>> send
>> update add kuiper-macbookpro.redfish-solutions.com. IN A 192.168.6.19
>> send
>> update add 19.6.168.192.in-addr.arpa. IN PTR 
>> kuiper-macbookpro.redfish-solutions.com.
>> send
>> update add iphone16-philip.redfish-solutions.com. IN A 192.168.6.20
>> send
>> update add 20.6.168.192.in-addr.arpa. IN PTR 
>> iphone16-philip.redfish-solutions.com.
>> send
>> update add iwatch-emily.redfish-solutions.com. IN A 192.168.6.22
>> send
>> update add 22.6.168.192.in-addr.arpa. IN PTR 
>> iwatch-emily.redfish-solutions.com.
>> send
>> update add lucs-laptop.redfish-solutions.com. IN A 192.168.6.23
>> send
>> update add 23.6.168.192.in-addr.arpa. IN PTR 
>> lucs-laptop.redfish-solutions.com.
>> send
>> update add queenies-switch.redfish-solutions.com. IN A 192.168.6.24
>> send
>> update add 24.6.168.192.in-addr.arpa. IN PTR 
>> queenies-switch.redfish-solutions.com.
>> send
>> update add queenies-switch-lite.redfish-solutions.com. IN A 192.168.6.25
>> send
>> update add 25.6.168.192.in-addr.arpa. IN PTR 
>> queenies-switch-lite.redfish-solutions.com.
>> send
>> update add sony-ps4.

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

2025-12-01 Thread Philip Prindeville via bind-users

I believe the “-l” option to nsupdate tells it it’s local-only mode.



> On Dec 1, 2025, at 2:55 PM, Darren Ankney  wrote:
> 
> Hi Philip,
> 
> Perhaps you need to specify the server to which nsupdate should
> connect?  I didn't see that anywhere above or in the linked scripts
> (of course, I may have just missed it, in which case, you could ignore
> this observation).  Otherwise, nsupdate might fail to discover that
> you are authoritative for 31.8.168.192.in-addr.arpa and try to send
> the update off premise.  Here is an example where I update my own
> local PTR:
> 
> sudo nsupdate -k /etc/bind/TSIG-NSUPDATE
>> server 192.168.40.142
>> update add 107.20.168.192.in-addr.arpa 3600 IN PTR 
>> dell-laser-printer.mylocal.
>> send
>> quit
> 
> Thank you,
> Darren Ankney
> 
> On Mon, Dec 1, 2025 at 3:51 PM Philip Prindeville via bind-users
>  wrote:
>> 
>> [ Bcc: David and Noah ]
>> 
>> Hi,
>> 
>> I’m the maintainer for Kea and ISC-DHCP on OpenWRT.  The scripting to take 
>> the UCI configuration files for DHCP and mangle them into Bind zone 
>> transfers is here:
>> 
>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L136-L186
>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L274
>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L276
>> 
>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L569
>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L575
>> 
>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L581-L606
>> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L694
>> 
>> and the glue in Bind is here:
>> 
>> https://github.com/openwrt/packages/blob/master/net/bind/files/bind/named.conf#L8-L9
>> 
>> An example is running locally here, where I have “redfish-solutions.com 
>> ” and “168.192.in-addr.arpa” as the domains I 
>> serve.
>> 
>> ; Generated by /etc/init.d/dhcpd at Mon Dec  1 13:14:10 MST 2025
>> 
>> ttl 3600
>> 
>> update add Bedroom.redfish-solutions.com. IN A 192.168.5.5
>> send
>> update add 5.5.168.192.in-addr.arpa. IN PTR Bedroom.redfish-solutions.com.
>> send
>> update add Penthouse.redfish-solutions.com. IN A 192.168.5.6
>> send
>> update add 6.5.168.192.in-addr.arpa. IN PTR Penthouse.redfish-solutions.com.
>> send
>> update add switch1.redfish-solutions.com. IN A 192.168.6.3
>> send
>> update add 3.6.168.192.in-addr.arpa. IN PTR switch1.redfish-solutions.com.
>> send
>> update add usw-24-poe.redfish-solutions.com. IN A 192.168.6.4
>> send
>> update add 4.6.168.192.in-addr.arpa. IN PTR usw-24-poe.redfish-solutions.com.
>> send
>> update add usw-aggregation.redfish-solutions.com. IN A 192.168.6.5
>> send
>> update add 5.6.168.192.in-addr.arpa. IN PTR 
>> usw-aggregation.redfish-solutions.com.
>> send
>> update add uap-ac-pro-upstairs.redfish-solutions.com. IN A 192.168.6.6
>> send
>> update add 6.6.168.192.in-addr.arpa. IN PTR 
>> uap-ac-pro-upstairs.redfish-solutions.com.
>> send
>> update add uap-u6-lr-mainfloor.redfish-solutions.com. IN A 192.168.6.7
>> send
>> update add 7.6.168.192.in-addr.arpa. IN PTR 
>> uap-u6-lr-mainfloor.redfish-solutions.com.
>> send
>> update add uap-ac-pro-basement.redfish-solutions.com. IN A 192.168.6.8
>> send
>> update add 8.6.168.192.in-addr.arpa. IN PTR 
>> uap-ac-pro-basement.redfish-solutions.com.
>> send
>> update add bluray3d.redfish-solutions.com. IN A 192.168.6.13
>> send
>> update add 13.6.168.192.in-addr.arpa. IN PTR bluray3d.redfish-solutions.com.
>> send
>> update add bluray.redfish-solutions.com. IN A 192.168.6.14
>> send
>> update add 14.6.168.192.in-addr.arpa. IN PTR bluray.redfish-solutions.com.
>> send
>> update add macbook3.redfish-solutions.com. IN A 192.168.6.17
>> send
>> update add 17.6.168.192.in-addr.arpa. IN PTR macbook3.redfish-solutions.com.
>> send
>> update add charlottes-iwatch.redfish-solutions.com. IN A 192.168.6.18
>> send
>> update add 18.6.168.192.in-addr.arpa. IN PTR 
>> charlottes-iwatch.redfish-solutions.com.
>> send
>> update add kuiper-macbookpro.redfish-solutions.com. IN A 192.168.6.19
>> send
>> update add 19.6.168.192.in-addr.arpa. IN PTR 
>> kuiper-macbookpro.redfish-solutions.com.
>> send
>> update add iphone16-philip.redfish-solutions.com. IN A 192.168.6.20
>> send
>> update add 20.6.168.192.in-addr.arpa. IN PTR 
>> iphone16-philip.redfish-solutions.com.
>> send
>> update add iwatch-emily.redfish-solutions.com. IN A 192.168.6.22
>> send
>> update add 22.6.168.192.in-addr.arpa. IN PTR 
>> iwatch-emily.redfish-solutions.com.
>> send
>> update add lucs-laptop.redfish-solutions.com. IN A 192.168.6.23
>> send
>> update add 23.6.168.192.in-addr.arpa. IN PTR 
>> lucs-laptop.redfish-solutions.com.
>> send
>> update add queenies-switch.redfish-solutions.com. IN A 192.168.6.24
>> send
>> update add 24.6.168.192.in-addr.arpa. IN PTR 
>> queenies-switch.redfish-solutions.com.
>> send
>> upd

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

2025-12-01 Thread Mark Andrews

Almost certainly this will be a clash between the existing automatic empty zone 
and
the 'rndc addzone' for 168.192.in-addr.arpa.  The long term fix will be to have 
named
check if the added zone is an automatic empty zone and to allow 'rndc addzone’ 
to
replace it.  In the mean time I would just add 168.192.in-addr.arpa to 
named.conf or add
'disable-empty-zone 168.192.in-addr.arpa;’

Mark

> On 2 Dec 2025, at 07:50, Philip Prindeville via bind-users 
>  wrote:
> 
> [ Bcc: David and Noah ]
> 
> Hi,
> 
> I’m the maintainer for Kea and ISC-DHCP on OpenWRT.  The scripting to take 
> the UCI configuration files for DHCP and mangle them into Bind zone transfers 
> is here:
> 
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L136-L186
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L274
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L276
> 
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L569
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L575
> 
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L581-L606
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L694
> 
> and the glue in Bind is here:
> 
> https://github.com/openwrt/packages/blob/master/net/bind/files/bind/named.conf#L8-L9
> 
> An example is running locally here, where I have “redfish-solutions.com 
> ” and “168.192.in-addr.arpa” as the domains I 
> serve.
> 
> ; Generated by /etc/init.d/dhcpd at Mon Dec  1 13:14:10 MST 2025
> 
> ttl 3600
> 
> update add Bedroom.redfish-solutions.com. IN A 192.168.5.5
> send
> update add 5.5.168.192.in-addr.arpa. IN PTR Bedroom.redfish-solutions.com.
> send
> update add Penthouse.redfish-solutions.com. IN A 192.168.5.6
> send
> update add 6.5.168.192.in-addr.arpa. IN PTR Penthouse.redfish-solutions.com.
> send
> update add switch1.redfish-solutions.com. IN A 192.168.6.3
> send
> update add 3.6.168.192.in-addr.arpa. IN PTR switch1.redfish-solutions.com.
> send
> update add usw-24-poe.redfish-solutions.com. IN A 192.168.6.4
> send
> update add 4.6.168.192.in-addr.arpa. IN PTR usw-24-poe.redfish-solutions.com.
> send
> update add usw-aggregation.redfish-solutions.com. IN A 192.168.6.5
> send
> update add 5.6.168.192.in-addr.arpa. IN PTR 
> usw-aggregation.redfish-solutions.com.
> send
> update add uap-ac-pro-upstairs.redfish-solutions.com. IN A 192.168.6.6
> send
> update add 6.6.168.192.in-addr.arpa. IN PTR 
> uap-ac-pro-upstairs.redfish-solutions.com.
> send
> update add uap-u6-lr-mainfloor.redfish-solutions.com. IN A 192.168.6.7
> send
> update add 7.6.168.192.in-addr.arpa. IN PTR 
> uap-u6-lr-mainfloor.redfish-solutions.com.
> send
> update add uap-ac-pro-basement.redfish-solutions.com. IN A 192.168.6.8
> send
> update add 8.6.168.192.in-addr.arpa. IN PTR 
> uap-ac-pro-basement.redfish-solutions.com.
> send
> update add bluray3d.redfish-solutions.com. IN A 192.168.6.13
> send
> update add 13.6.168.192.in-addr.arpa. IN PTR bluray3d.redfish-solutions.com.
> send
> update add bluray.redfish-solutions.com. IN A 192.168.6.14
> send
> update add 14.6.168.192.in-addr.arpa. IN PTR bluray.redfish-solutions.com.
> send
> update add macbook3.redfish-solutions.com. IN A 192.168.6.17
> send
> update add 17.6.168.192.in-addr.arpa. IN PTR macbook3.redfish-solutions.com.
> send
> update add charlottes-iwatch.redfish-solutions.com. IN A 192.168.6.18
> send
> update add 18.6.168.192.in-addr.arpa. IN PTR 
> charlottes-iwatch.redfish-solutions.com.
> send
> update add kuiper-macbookpro.redfish-solutions.com. IN A 192.168.6.19
> send
> update add 19.6.168.192.in-addr.arpa. IN PTR 
> kuiper-macbookpro.redfish-solutions.com.
> send
> update add iphone16-philip.redfish-solutions.com. IN A 192.168.6.20
> send
> update add 20.6.168.192.in-addr.arpa. IN PTR 
> iphone16-philip.redfish-solutions.com.
> send
> update add iwatch-emily.redfish-solutions.com. IN A 192.168.6.22
> send
> update add 22.6.168.192.in-addr.arpa. IN PTR 
> iwatch-emily.redfish-solutions.com.
> send
> update add lucs-laptop.redfish-solutions.com. IN A 192.168.6.23
> send
> update add 23.6.168.192.in-addr.arpa. IN PTR 
> lucs-laptop.redfish-solutions.com.
> send
> update add queenies-switch.redfish-solutions.com. IN A 192.168.6.24
> send
> update add 24.6.168.192.in-addr.arpa. IN PTR 
> queenies-switch.redfish-solutions.com.
> send
> update add queenies-switch-lite.redfish-solutions.com. IN A 192.168.6.25
> send
> update add 25.6.168.192.in-addr.arpa. IN PTR 
> queenies-switch-lite.redfish-solutions.com.
> send
> update add sony-ps4.redfish-solutions.com. IN A 192.168.6.26
> send
> update add 26.6.168.192.in-addr.arpa. IN PTR sony-ps4.redfish-solutions.com.
> send
> update add Lucs-iPhone.redfish-solutions.com. IN A 192.168.6.27
> send
> update add 27.6.168.192.in-addr.arpa. IN PTR 
> Lucs-iPhone.redfish-solutions.com.
> send
>

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

2025-12-01 Thread Darren Ankney

Hi Philip,

Perhaps you need to specify the server to which nsupdate should
connect?  I didn't see that anywhere above or in the linked scripts
(of course, I may have just missed it, in which case, you could ignore
this observation).  Otherwise, nsupdate might fail to discover that
you are authoritative for 31.8.168.192.in-addr.arpa and try to send
the update off premise.  Here is an example where I update my own
local PTR:

sudo nsupdate -k /etc/bind/TSIG-NSUPDATE
> server 192.168.40.142
> update add 107.20.168.192.in-addr.arpa 3600 IN PTR dell-laser-printer.mylocal.
> send
> quit

Thank you,
Darren Ankney

On Mon, Dec 1, 2025 at 3:51 PM Philip Prindeville via bind-users
 wrote:
>
> [ Bcc: David and Noah ]
>
> Hi,
>
> I’m the maintainer for Kea and ISC-DHCP on OpenWRT.  The scripting to take 
> the UCI configuration files for DHCP and mangle them into Bind zone transfers 
> is here:
>
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L136-L186
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L274
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L276
>
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L569
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L575
>
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L581-L606
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L694
>
> and the glue in Bind is here:
>
> https://github.com/openwrt/packages/blob/master/net/bind/files/bind/named.conf#L8-L9
>
> An example is running locally here, where I have “redfish-solutions.com 
> ” and “168.192.in-addr.arpa” as the domains I 
> serve.
>
> ; Generated by /etc/init.d/dhcpd at Mon Dec  1 13:14:10 MST 2025
>
> ttl 3600
>
> update add Bedroom.redfish-solutions.com. IN A 192.168.5.5
> send
> update add 5.5.168.192.in-addr.arpa. IN PTR Bedroom.redfish-solutions.com.
> send
> update add Penthouse.redfish-solutions.com. IN A 192.168.5.6
> send
> update add 6.5.168.192.in-addr.arpa. IN PTR Penthouse.redfish-solutions.com.
> send
> update add switch1.redfish-solutions.com. IN A 192.168.6.3
> send
> update add 3.6.168.192.in-addr.arpa. IN PTR switch1.redfish-solutions.com.
> send
> update add usw-24-poe.redfish-solutions.com. IN A 192.168.6.4
> send
> update add 4.6.168.192.in-addr.arpa. IN PTR usw-24-poe.redfish-solutions.com.
> send
> update add usw-aggregation.redfish-solutions.com. IN A 192.168.6.5
> send
> update add 5.6.168.192.in-addr.arpa. IN PTR 
> usw-aggregation.redfish-solutions.com.
> send
> update add uap-ac-pro-upstairs.redfish-solutions.com. IN A 192.168.6.6
> send
> update add 6.6.168.192.in-addr.arpa. IN PTR 
> uap-ac-pro-upstairs.redfish-solutions.com.
> send
> update add uap-u6-lr-mainfloor.redfish-solutions.com. IN A 192.168.6.7
> send
> update add 7.6.168.192.in-addr.arpa. IN PTR 
> uap-u6-lr-mainfloor.redfish-solutions.com.
> send
> update add uap-ac-pro-basement.redfish-solutions.com. IN A 192.168.6.8
> send
> update add 8.6.168.192.in-addr.arpa. IN PTR 
> uap-ac-pro-basement.redfish-solutions.com.
> send
> update add bluray3d.redfish-solutions.com. IN A 192.168.6.13
> send
> update add 13.6.168.192.in-addr.arpa. IN PTR bluray3d.redfish-solutions.com.
> send
> update add bluray.redfish-solutions.com. IN A 192.168.6.14
> send
> update add 14.6.168.192.in-addr.arpa. IN PTR bluray.redfish-solutions.com.
> send
> update add macbook3.redfish-solutions.com. IN A 192.168.6.17
> send
> update add 17.6.168.192.in-addr.arpa. IN PTR macbook3.redfish-solutions.com.
> send
> update add charlottes-iwatch.redfish-solutions.com. IN A 192.168.6.18
> send
> update add 18.6.168.192.in-addr.arpa. IN PTR 
> charlottes-iwatch.redfish-solutions.com.
> send
> update add kuiper-macbookpro.redfish-solutions.com. IN A 192.168.6.19
> send
> update add 19.6.168.192.in-addr.arpa. IN PTR 
> kuiper-macbookpro.redfish-solutions.com.
> send
> update add iphone16-philip.redfish-solutions.com. IN A 192.168.6.20
> send
> update add 20.6.168.192.in-addr.arpa. IN PTR 
> iphone16-philip.redfish-solutions.com.
> send
> update add iwatch-emily.redfish-solutions.com. IN A 192.168.6.22
> send
> update add 22.6.168.192.in-addr.arpa. IN PTR 
> iwatch-emily.redfish-solutions.com.
> send
> update add lucs-laptop.redfish-solutions.com. IN A 192.168.6.23
> send
> update add 23.6.168.192.in-addr.arpa. IN PTR 
> lucs-laptop.redfish-solutions.com.
> send
> update add queenies-switch.redfish-solutions.com. IN A 192.168.6.24
> send
> update add 24.6.168.192.in-addr.arpa. IN PTR 
> queenies-switch.redfish-solutions.com.
> send
> update add queenies-switch-lite.redfish-solutions.com. IN A 192.168.6.25
> send
> update add 25.6.168.192.in-addr.arpa. IN PTR 
> queenies-switch-lite.redfish-solutions.com.
> send
> update add sony-ps4.redfish-solutions.com. IN A 192.168.6.26
> send
> update add 26.6.168.192.in-addr.arpa. IN

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

2025-12-01 Thread Greg Choules via bind-users

Hi Philip.
Your named.conf is.. minimal. Do you have an allow-update statement in
there anywhere?
The rest of your BIND config and some logs might be helpful.

Cheers, Greg

On Mon, 1 Dec 2025 at 20:51, Philip Prindeville via bind-users <
[email protected]> wrote:

> [ Bcc: David and Noah ]
>
> Hi,
>
> I’m the maintainer for Kea and ISC-DHCP on OpenWRT.  The scripting to take
> the UCI configuration files for DHCP and mangle them into Bind zone
> transfers is here:
>
>
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L136-L186
>
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L274
>
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L276
>
>
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L569
>
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L575
>
>
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L581-L606
>
> https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L694
>
> and the glue in Bind is here:
>
>
> https://github.com/openwrt/packages/blob/master/net/bind/files/bind/named.conf#L8-L9
>
> An example is running locally here, where I have “redfish-solutions.com <
> http://redfish-solutions.com/>” and “168.192.in-addr.arpa” as the domains
> I serve.
>
> ; Generated by /etc/init.d/dhcpd at Mon Dec  1 13:14:10 MST 2025
>
> ttl 3600
>
> update add Bedroom.redfish-solutions.com. IN A 192.168.5.5
> send
> update add 5.5.168.192.in-addr.arpa. IN PTR Bedroom.redfish-solutions.com.
> send
> update add Penthouse.redfish-solutions.com. IN A 192.168.5.6
> send
> update add 6.5.168.192.in-addr.arpa. IN PTR
> Penthouse.redfish-solutions.com.
> send
> update add switch1.redfish-solutions.com. IN A 192.168.6.3
> send
> update add 3.6.168.192.in-addr.arpa. IN PTR switch1.redfish-solutions.com.
> send
> update add usw-24-poe.redfish-solutions.com. IN A 192.168.6.4
> send
> update add 4.6.168.192.in-addr.arpa. IN PTR
> usw-24-poe.redfish-solutions.com.
> send
> update add usw-aggregation.redfish-solutions.com. IN A 192.168.6.5
> send
> update add 5.6.168.192.in-addr.arpa. IN PTR
> usw-aggregation.redfish-solutions.com.
> send
> update add uap-ac-pro-upstairs.redfish-solutions.com. IN A 192.168.6.6
> send
> update add 6.6.168.192.in-addr.arpa. IN PTR
> uap-ac-pro-upstairs.redfish-solutions.com.
> send
> update add uap-u6-lr-mainfloor.redfish-solutions.com. IN A 192.168.6.7
> send
> update add 7.6.168.192.in-addr.arpa. IN PTR
> uap-u6-lr-mainfloor.redfish-solutions.com.
> send
> update add uap-ac-pro-basement.redfish-solutions.com. IN A 192.168.6.8
> send
> update add 8.6.168.192.in-addr.arpa. IN PTR
> uap-ac-pro-basement.redfish-solutions.com.
> send
> update add bluray3d.redfish-solutions.com. IN A 192.168.6.13
> send
> update add 13.6.168.192.in-addr.arpa. IN PTR
> bluray3d.redfish-solutions.com.
> send
> update add bluray.redfish-solutions.com. IN A 192.168.6.14
> send
> update add 14.6.168.192.in-addr.arpa. IN PTR bluray.redfish-solutions.com.
> send
> update add macbook3.redfish-solutions.com. IN A 192.168.6.17
> send
> update add 17.6.168.192.in-addr.arpa. IN PTR
> macbook3.redfish-solutions.com.
> send
> update add charlottes-iwatch.redfish-solutions.com. IN A 192.168.6.18
> send
> update add 18.6.168.192.in-addr.arpa. IN PTR
> charlottes-iwatch.redfish-solutions.com.
> send
> update add kuiper-macbookpro.redfish-solutions.com. IN A 192.168.6.19
> send
> update add 19.6.168.192.in-addr.arpa. IN PTR
> kuiper-macbookpro.redfish-solutions.com.
> send
> update add iphone16-philip.redfish-solutions.com. IN A 192.168.6.20
> send
> update add 20.6.168.192.in-addr.arpa. IN PTR
> iphone16-philip.redfish-solutions.com.
> send
> update add iwatch-emily.redfish-solutions.com. IN A 192.168.6.22
> send
> update add 22.6.168.192.in-addr.arpa. IN PTR
> iwatch-emily.redfish-solutions.com.
> send
> update add lucs-laptop.redfish-solutions.com. IN A 192.168.6.23
> send
> update add 23.6.168.192.in-addr.arpa. IN PTR
> lucs-laptop.redfish-solutions.com.
> send
> update add queenies-switch.redfish-solutions.com. IN A 192.168.6.24
> send
> update add 24.6.168.192.in-addr.arpa. IN PTR
> queenies-switch.redfish-solutions.com.
> send
> update add queenies-switch-lite.redfish-solutions.com. IN A 192.168.6.25
> send
> update add 25.6.168.192.in-addr.arpa. IN PTR
> queenies-switch-lite.redfish-solutions.com.
> send
> update add sony-ps4.redfish-solutions.com. IN A 192.168.6.26
> send
> update add 26.6.168.192.in-addr.arpa. IN PTR
> sony-ps4.redfish-solutions.com.
> send
> update add Lucs-iPhone.redfish-solutions.com. IN A 192.168.6.27
> send
> update add 27.6.168.192.in-addr.arpa. IN PTR
> Lucs-iPhone.redfish-solutions.com.
> send
> update add fire-blue.redfish-solutions.com. IN A 192.168.6.28
> send
> update add 28.6.168.192.in-addr.arpa. IN PTR
> fire-blue.redfish-solutions.com.
> send
> update add fire-purple.redfish-soluti

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

Re: Integrating ISC-DHCP with/ Bind (and eventually Kea)

15 matches

Site Navigation

Mail list logo

Footer information