Feature #16732
closed
Add check for CoreDNS when configuring DNS Resolver or Forwarder
0%
Description
If you enable CoreDNS on port 53, and then attempt to enable DNS Resolver on the same port, you get:
If you repeat the same procedure with DNS Forwarder, it saves successfully without error/warning but dnsmasq service is down.
Files
Updated by Kris Phillips 10 days ago
- File Screenshot_20260517_153840.png Screenshot_20260517_153840.png added
- Status changed from New to Resolved
This is resolved in newer versions of Nexus with CoreDNS. The "Easy Setup" button will disable either unbound or dnsmasq, if they are running, as well as implement any other changes to activate it.
See attached screenshot.
Marking Resolved.
Updated by → luckman212 10 days ago
Is CoreDNS replacing Unbound in 26.07? Is that available to test yet?
Updated by Jim Pingle 9 days ago
→ luckman212 wrote in #note-2:
Is CoreDNS replacing Unbound in 26.07? Is that available to test yet?
No. Though part of its functionality is to act as a DNS forwarder, and for very basic setups it could use CoreDNS alone, there are many things Unbound can do beyond its current capabilities. Currently the recommended setup is to have clients hit CoreDNS first and then use Unbound as its upstream source for queries that make it through CoreDNS filtering and so on.