dyndnsd 3.11.0 → 3.12.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 8b42d2f705687808d249c527376a3aadd9475530fd2d63504ea84af8af648c19
-  data.tar.gz: 5e8b830c3f7b5e8cbdfdaa430aab6afdb8ca73af0e94e76fa639075f812e5430
+  metadata.gz: 1291b6722535928edf7d305db50ffe5045b211b2a03425218f97fd6d6648ec4b
+  data.tar.gz: 6f9f5611f347d5f3e4dee4a0c9dd8d6fe85c6b21a36919bf39a68f872ae51e25
 SHA512:
-  metadata.gz: 4e2ab7c620f0bec2677a52a6821cdaa6a22dec7f290f6097cecee76afc033845be12fd52d3e993d07c08960c3c396f33c419359be68f71cf711613f85cfbbc2c
-  data.tar.gz: e82dd2c0df92b44b3d885537af20c87046cb64be584ff77652194d59b46510738c077e7e190766aa2ec60164ed93823360bd8da82808f8dfd867e2f690fb25f8
+  metadata.gz: c42f9a7bc3aece580177ffe50cfdcda3f7a7bc3f4ee978c3986f1abfd4cf6756f01f1c8606a852d76eb217da805c6633fa4a3df7ee76d7b95417cdb3dd8dd702
+  data.tar.gz: 1735e786ae2e77b1be0a2eb1bcb45d667836f71d9adf0268433c067296831af66674525db8c0fc961a398731d51fa7a0c3d9ff7967dd2ba326788d64e393700b

data/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 3.12.0 (December 4th, 2025)
+
+IMPROVEMENTS:
+
+- regex instead of hosts list can be used for hostname ownership
+
 ## 3.11.0 (October 2nd, 2025)
 
 IMPROVEMENTS:

data/README.md

@@ -307,6 +307,37 @@ users:
 ```
 
 
+### Matching with a regular expression
+
+Instead of relying on `hosts`, you can use `regex` to employ a regular expression, which is very useful for avoiding having to repeatedly edit the configuration file to register a new host name.
+
+```yaml
+host: "0.0.0.0"
+port: 5354
+username: "dyndnsd"
+group: "dyndnsd"
+db: "/dyndnsd/db.json"
+debug: false
+domain: "dyn.dc-air.home.arpa"
+updater:
+  name: "command_with_bind_zone"
+  params:
+    zone_file: "/nsd/zones/static/dyn.dc-air.home.arpa.zone"
+    command: "doas service nsd reload"
+    ttl: "5m"
+    dns: "ns.dc-air.home.arpa."
+    email_addr: "admin.example.org"
+users:
+  myuser:
+    password: "superhypermegas3kurepassword1234"
+    regex: '^[a-z][0-9]\.dyn\.dc\-air\.home\.arpa$'
+```
+
+However, when using `regex`, `hosts` is simply ignored if defined, so you must choose one or the other. Recommendation: use `regex` for scripts or programs and `hosts` for regular users.
+
+**Note**: Please note that when dyndnsd evaluates the regular expression, the `Regexp::EXTENDED` and `Regexp::IGNORECASE` options are used.
+
+
 ## License
 
 dyndnsd.rb is licensed under the Apache License, Version 2.0. See LICENSE for more information.

data/lib/dyndnsd/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Dyndnsd
-  VERSION = '3.11.0'
+  VERSION = '3.12.0'
 end

data/lib/dyndnsd.rb

@@ -218,9 +218,22 @@ module Dyndnsd
       # we can trust this information since user was authorized by middleware
       user = env['REMOTE_USER']
 
-      # check for hostnames that the user does not own
-      forbidden_hostnames = hostnames - @users[user].fetch('hosts', [])
-      return [422, {'X-DynDNS-Response' => 'host_forbidden'}, []] if forbidden_hostnames.any?
+      if @users[user].key?('regex')
+        pattern = @users[user].fetch('regex')
+        begin
+          regex = Regexp.new(pattern, Regexp::IGNORECASE | Regexp::EXTENDED)
+        rescue RegexpError => e
+          Dyndnsd.logger.warn "Invalid regex pattern '#{pattern}': #{e.message}"
+          return [422, {'X-DynDNS-Response' => 'host_forbidden'}, []]
+        end
+        # check for hostnames that match the regex
+        matches = hostnames.any? { |str| regex.match?(str) }
+        return [422, {'X-DynDNS-Response' => 'host_forbidden'}, []] if !matches
+      else
+        # check for hostnames that the user does not own
+        forbidden_hostnames = hostnames - @users[user].fetch('hosts', [])
+        return [422, {'X-DynDNS-Response' => 'host_forbidden'}, []] if forbidden_hostnames.any?
+      end
 
       if params['offline'] == 'YES'
         myips = []

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: dyndnsd
 version: !ruby/object:Gem::Version
-  version: 3.11.0
+  version: 3.12.0
 platform: ruby
 authors:
 - Christian Nicolai
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2025-10-02 00:00:00.000000000 Z
+date: 2025-12-04 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: async
@@ -274,14 +274,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 3.7.0
+        version: 3.8.0
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 3.7.0
+        version: 3.8.0
 - !ruby/object:Gem::Dependency
   name: solargraph
   requirement: !ruby/object:Gem::Requirement