Dnsmasq DHCP and DNS module

[DavidePrincipi]

What we need:

• A user-friendly module with customizable IP ranges and DHCP options.
• DNS service flexibility, allowing seamless integration with Samba AD.
• DNS can now resolve host names defined by HTTP routes and TLS certificates.

Implementation proposal:

• [X] Rootfull module, with one Dnsmasq service instance
• [X] Bind to a selectable host private IP address (it's for LAN only)
• [X] Enable/Disable DHCP service
• [X] Enable/Disable DNS service (bind to port 53)
• [X] Display lease cache https://github.com/NethServer/ns8-dnsmasq/releases/tag/0.2.0
• [X] Create/edit/modify DNS A records (it's for LAN only, no CNAMEs for arbitrary hosts) https://github.com/NethServer/ns8-dnsmasq/releases/tag/0.2.0
• [x] Self-discovery of node aliases from Traefik HTTP routes configuration
  • [x] NethServer/ns8-traefik#53
  • [x] NethServer/ns8-dnsmasq#3
  • [x] NethServer/ns8-core#613
• [x] cluster-admin module UI
  • [x] NethServer/ns8-dnsmasq#2
  • [x] NethServer/ns8-dnsmasq#4
• [x] admin's manual page NethServer/ns8-docs#84
• [x] Add DNSMasq to ns8-repomd https://github.com/NethServer/ns8-repomd/commit/2e79a321ccc8b7e353343b04ef2d2ea45e65366d

Module implementation: https://github.com/NethServer/ns8-dnsmasq

See also

• https://community.nethserver.org/t/nethserver-8-is-landed-finally/22820#a-new-features-in-development-16

[Tbaile]

Best QA scenario MAY have the following prerequisites:

• Network interface manually configured from the OS
• Client connected only to the previous network interface (to avoid issues and conflicts)

Further details are given at footnotes.

QA:

1. Basic
   1. Install Module add-module ghcr.io/nethserver/dnsmasq:latest
   2. Settings page shows interface missing
   3. Interfaces available in the dropdown are only the one configured[^1]
   4. Select interface[^2] and save
   5. UI shows DHCP and DNS sections
   6. DHCP
      1. Turn on DHCP toggle
      2. Ensure start/end are already populated with values from selected interface
      3. Save
      4. Ensure that client receives an IP inside the range
      5. DNS
      6. Turn on DNS toggle
      7. Save
      8. dig a host from the client, expect none back
      9. Set a DNS server
      10. Save
      11. dig another DNS, expect response
   7. Automatic CNAMEs
      1. DNS MUST be turned on
      2. Install an application that requires an FQDN (I.E. mattermost)
      3. dig the configured FQDN, expect a CNAME record with the FQDN of the node
   8. DNS records
      1. Access the "DNS Records" page
      2. Ensure that you can add/remove A records
      3. dig from the client to verify that DNS Record is saved successfully
2. Backup/Restore/Move
   1. All functionalities are to be expected working, ensure that NO services are running when restoring/move, this is made by design, since the interface is most likely to have been moved and or renamed in the process.

[^1]: Additional network interfaces needed [^2]: Prefer using a network manually configured, so that DHCP and DNS are working properly

[nrauso]

tested all cases: VERIFIED note: have to install the latest NS8 core

[DavidePrincipi]

Do we have the admin's manual page?

[DavidePrincipi]

Released dependency in testing core 2.6.0-dev.1 (fix for clone-module) Blocked by https://github.com/NethServer/ns8-core/pull/615

[DavidePrincipi]

Released

• https://github.com/NethServer/ns8-core/releases/tag/2.6.0
• https://github.com/NethServer/ns8-traefik/releases/tag/2.2.0
• https://github.com/NethServer/ns8-dnsmasq/releases/tag/1.0.0

Added to Software Center: https://github.com/NethServer/ns8-repomd/commit/2e79a321ccc8b7e353343b04ef2d2ea45e65366d