From Fedora Project Wiki
No edit summary |
|||
| Line 7: | Line 7: | ||
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. | 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. | ||
== 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. | |||
<pre> | |||
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 | |||
</pre> | |||
Revision as of 01:01, 22 April 2015
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.
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