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

Validate upstream reachability on first DNS configuration #1489

Merged
merged 2 commits into from Jan 23, 2024

Conversation

lixmal
Copy link
Contributor

@lixmal lixmal commented Jan 22, 2024

Describe your changes

This adds an availability check for each DNS server group right after receiving DNS updates from management.
If no servers of a group are available the group will be disabled.

Issue ticket number and link

When we receive an upstream DNS server, we add the address in the system without checking if the address is reachable; this may cause issues as some queries will fail and may delay peer connection if the domains served by the upstream might contain our management layer.

Checklist

  • Is it a bug fix
  • Is a typo/documentation fix
  • Is a feature enhancement
  • It is a refactor
  • Created tests that fail without the change (if possible)
  • Extended the README / documentation, if necessary

@lixmal lixmal requested a review from bcmmbaga January 22, 2024 09:16
@lixmal lixmal merged commit 88117f7 into main Jan 23, 2024
16 checks passed
@lixmal lixmal deleted the validate-upstream-dns branch January 23, 2024 16:23
Foosec pushed a commit to Foosec/netbird that referenced this pull request May 8, 2024
…1489)

* Test upstream DNS for availability as soon as they are received from management

* Use root zone for DNS tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants