Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dnsmasq DHCP and DNS module #6877

Closed
15 tasks done
DavidePrincipi opened this issue Mar 4, 2024 · 5 comments
Closed
15 tasks done

Dnsmasq DHCP and DNS module #6877

DavidePrincipi opened this issue Mar 4, 2024 · 5 comments
Assignees
Labels
verified All test cases were verified successfully

Comments

@DavidePrincipi
Copy link
Member

DavidePrincipi commented Mar 4, 2024

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:

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

See also

@Tbaile
Copy link
Contributor

Tbaile commented Mar 18, 2024

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 configured1
    4. Select interface2 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
    7. DNS
      1. Turn on DNS toggle
      2. Save
      3. dig a host from the client, expect none back
      4. Set a DNS server
      5. Save
      6. dig another DNS, expect response
    8. 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
    9. 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.

Footnotes

  1. Additional network interfaces needed

  2. Prefer using a network manually configured, so that DHCP and DNS are working properly

@DavidePrincipi DavidePrincipi added the testing Packages are available from testing repositories label Mar 18, 2024
@DavidePrincipi DavidePrincipi moved this from 🏗 In progress to 👀 Testing in NethServer Mar 18, 2024
@nrauso nrauso self-assigned this Mar 18, 2024
@nrauso
Copy link

nrauso commented Mar 25, 2024

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

@nrauso nrauso added verified All test cases were verified successfully and removed testing Packages are available from testing repositories labels Mar 25, 2024
@DavidePrincipi
Copy link
Member Author

Do we have the admin's manual page?

@DavidePrincipi
Copy link
Member Author

DavidePrincipi commented Mar 25, 2024

Released dependency in testing core 2.6.0-dev.1 (fix for clone-module)
Blocked by NethServer/ns8-core#615

@github-project-automation github-project-automation bot moved this from 👀 Testing to ✅ Done in NethServer Mar 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
verified All test cases were verified successfully
Projects
Archived in project
Development

No branches or pull requests

4 participants