Hi Alec,
Have you tried setting `--dhcp-option=option6:dns-server,[fd00::]` for auto
fill in of ULA or `--dhcp-option=option6:dns-server,[::]` auto ~ GA?
By default dnsmasq will send [fe80::] LL in RA and DHCPv6, but some clients do
not like DNS on LL. It also can break down in some
On Mon, Jan 16, 2017 at 1:11 PM, Simon Kelley wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Host makes A, and MX queries and it's the reply to the MX that's
> failing. This all works fine here (dnsmasq and host both running on
> the same x86_64
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Host makes A, and MX queries and it's the reply to the MX that's
failing. This all works fine here (dnsmasq and host both running on
the same x86_64 host. The reply to the MX query looks like this.
; (1 server found)
;; global options: +cmd
I am testing the dnsmasq-full build on current lede-project head, and
enabled dnssec. Then :
root@dancer:/# host flent-fremont.bufferbloat.net
flent-fremont.bufferbloat.net has address 23.239.20.41
flent-fremont.bufferbloat.net has IPv6 address 2600:3c01::f03c:91ff:fe50:48d4
;; Got bad packet:
On Mon, Jan 16, 2017 at 02:10:05PM +0100, Beniamino Galvani wrote:
>
> In the next version of NetworkManager (1.6) it will be possible to
> show the DNS configuration in the output of 'nmcli' [1], as:
>
Ah, now that seems to be a sensible approach. :-)
--
Chris Green
On Mon, Jan 16, 2017 at 08:36:05AM +0200, Lars Noodén wrote:
> Thanks. That's it. I somehow missed it there in the manual page:
>
> When it receives a SIGUSR1, dnsmasq writes statistics
> to the system log. … For each upstream server
> it gives the number of queries