> I've just pushed 2.76rc1 to the usual places.
Wait for pl.po! :-)
(tomorrow night I'll prepare it)
--
jasiu
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Hello,
I'm using dnsmasq as a local caching resolver and some of my queries result
in large answers (~1300 bytes) that are truncated without EDNS.
When I query my local dnsmasq daemon:
dig @localhost
dig sends a query to dnsmasq using EDNS but dnsmasq forwards that query to
its upstream
Lots of good info. Thanks everybody. Some more queries.
First, I'm minded to go with Michael's choice for "enabling"
workarounds; ie do what's needed to make things work with buggy PXe
menu's when there's exactly one relevant menu entry.
Second,
.0 vs. .efi
What's not been mentioned here is
I've just pushed 2.76rc1 to the usual places.
It's been a long time since the last stable release, and there's a load
of new code that really should be in general use.
Please test this if you can. There are likely to be a few more 2.76rc
releases to finalise the current work on PXE booting UEFI,
Hi
On 05/10/2016 04:55 PM, Simon Kelley wrote:
Lots of good info. Thanks everybody. Some more queries.
First, I'm minded to go with Michael's choice for "enabling"
workarounds; ie do what's needed to make things work with buggy PXe
menu's when there's exactly one relevant menu entry.
OK, so
I just pushed my take on this to git. It's untested, and covers what I
think are the correct choices so far. Please could you all test?
I picked
1) .0 in workaround mode, to match all other situations.
2) Workaround in non-proxy mode too.
3) Workaround engaged for CAS 6,7,8,9 only.
4) sname
