Am 23.12.2014 um 22:00 schrieb Simon Kelley:
> Try
>
> local=/virt/
>
> the extended domain= syntax is broken in some recent dnsmasq releases.
And the inotify stuff apparently broke builds on non-Linux systems (in
2.73test2). FreeBSD doesn't have that (nor sys/inotify.h), you need to
move t
also sprach Simon Kelley [2014-12-23 22:00 +0100]:
> Try
> local=/virt/
> the extended domain= syntax is broken in some recent dnsmasq releases.
Yeah, simply adding that local= line makes it work. Now I have to
figure out how to convince libvirtd of that if I want to avoid
starting my own dns
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Try
local=/virt/
the extended domain= syntax is broken in some recent dnsmasq releases.
Cheers,
Simon.
On 23/12/14 19:59, martin f krafft wrote:
> also sprach Simon Kelley [2014-12-23
> 18:14 +0100]:
>> My guess is that the SERVFAIL is co
also sprach Simon Kelley [2014-12-23 18:14 +0100]:
> My guess is that the SERVFAIL is coming from a server upstream of
> dnsmasq. Unless told to, dnsmasq "overlays" the DNS information is
> has locally onto the global DNS a record-at-a-time, not
> a domain-name at a time.
Yeah, that could be. tcp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
My guess is that the SERVFAIL is coming from a server upstream of
dnsmasq. Unless told to, dnsmasq "overlays" the DNS information is has
locally onto the global DNS a record-at-a-time, not a domain-name at a
time. So if dnsmasq knows the IPv4 address
Hey,
I am using dnsmasq from libvirt, like so:
dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf \
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
The configuration file is included below. Basically, this is a DHCP
server and DNS forwarder, but I've also configured it to turn D