Kevin,
I don't think there is a flaw in your logic. You are probably 50% right.
DNSMASQ is so flexible and useful it has found two significant homes and
a bunch of other neat uses.
Top however, (1) as a single point entry router caching DNS
(ex 192.168.1.1 / X.X.X.X -> 8.8.4.4), and (2) as a l
Eric Luehrsen (ericluehr...@hotmail.com) wrote on Sun, Oct 18, 2015 at
03:35:22AM BRST:
> dhcp-option=option6:dns-server,[::]
>
>
> >>> This is correct but not necessary, dnsmasq does it by default.
> This CAN BE necessary, depending. This option has a valid use case with
> SLAAC+DHCPV6 (s
Hi Simon & list,
Ok, here's the controversial idea. Can we consider enabling
'bogus-priv' by default and have an additional option say 'allow-priv'
to now disable?
My feeling is that not forwarding 'link-local' type requests upstream by
default is a cleaner way of having things configured. Bear
Hi Simon,
I wonder if I could encourage you to look at extending the 'bogus-priv'
option to include some IPv6 zones? In essence dnsmasq is currently
forwarding ipv6 link-local reverse queries when in reality root servers
aren't going to know anything. Looking in the archives I see ipv6
reverses
I made some changes to dnsmasq (patch below) that remove the PXE menu system
(the option 43 stuff) if there’s only one menu entry and put the boot file name
and server address directly into the file and siaddr fields. This works fine
for BIOS systems, but doesn’t work for UEFI either.
Next thing
