On 2019/12/30 20:19, David C. Rankin wrote:
All,
edns-udp-size 512;
and I still do not eliminate the "success ... after reducing the advertised EDNS UDP packet size to 512 octets" messages that are logged. The EDNS resolution is working, but only for 512 octets (the related posts seem to indicate this is a problem largely to do with misconfigured load-balancing and failover configurations of the target machines.
I don't recall seeing much of this before a month or two ago -- so I don't know if it is at all related to the DNS over http growing pains or what...
---- DNS over http is just evil as is http over https (except for finacial/health sites, etc)..
Has anyone else run into this problem -- or have a solution? The time it takes for Bind to try from UDP size of 4096 (default) to 512 on some sites with 50 linked domains can be quite noticeable.
I had that problem back around 5 years ago -- some dns servers are just running with more conservative settings. Anyway, I include it in my bind setup...a file with entries like: server "cable.net.co" { edns-udp-size 512; }; server "catherineshefski.com" { edns-udp-size 512; }; server "chilan.com" { edns-udp-size 512; }; server "dehy.de" { edns-udp-size 512; }; server "dfwright.net" { edns-udp-size 512; }; Was going to automate it, but the static took care of most cases, so never bothered. But yeah -- that file is dated 2014 -- so it's been a problem for a while.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org