From Fedora Project Wiki
m (Spichugi moved page Talk:Changes/Default Local DNS Resolver to Changes/Openldap 25/Default Local DNS Resolver) |
m (Kevin moved page Changes/Openldap 25/Default Local DNS Resolver to Talk:Changes//Default Local DNS Resolver: undoing previous move) |
(No difference)
| |
Latest revision as of 20:09, 25 October 2021
relation to dnssec-trigger(d)?
what's the relation to dnssec-triggerd?
Running DNS server
How will this impact running an existing DNS server? Is it only checking DNSSEC record not resolving hostname? I don't want this clobbering an existing DNS server for full resolution. As long as you can disable dnssec-triggerd im fine with this. I run PowerDNS and they will soon have DNSSEC support for recursor then I don't need dnssec-triggerd locally (or remotely if I allow my DNS server to allow external recursion).
What about libvirt dnsmasq?
Libvirt runs it's own instance of dnsmasq which already listens on 127.0.0.1:53 by default. This will need adjusting.
tcp 0 0 192.168.122.1:53 0.0.0.0:* LISTEN 1839/dnsmasq tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 1689/dnsmasq udp 0 0 192.168.122.1:53 0.0.0.0:* 1839/dnsmasq udp 0 0 127.0.0.1:53 0.0.0.0:* 1689/dnsmasq udp 0 0 0.0.0.0:67 0.0.0.0:* 1839/dnsmasq