EDNS - edns-udp-size and max-udp-size
the advertised), I also added the following to see if that would change anything: edns-udp-size 512; ... and restarted BIND. But still: --cut-- 24-Feb-2009 08:56:11.843 edns-disabled: success resolving 'rous.redbarn.org/A' (in 'redbarn.org'?) after reducing the advertised EDNS UDP packet size to 512 octets 24-Feb-2009 08:56:11.979 edns-disabled: success resolving '41.188.152.204.in-addr.arpa/PTR' (in '188.152.204.in-addr.arpa'?) after reducing the advertised EDNS UDP packet size to 512 octets 24-Feb-2009 08:56:13.863 edns-disabled: success resolving 'terra.com.br/MX' (in 'terra.com.br'?) after reducing the advertised EDNS UDP packet size to 512 octets 24-Feb-2009 08:56:14.049 edns-disabled: success resolving 'medidata.com.br/' (in 'medidata.com.br'?) after reducing the advertised EDNS UDP packet size to 512 octets 24-Feb-2009 08:56:14.119 edns-disabled: success resolving 'NS2.DNS.BR/A' (in 'br'?) after reducing the advertised EDNS UDP packet size to 512 octets 24-Feb-2009 08:56:14.351 edns-disabled: success resolving 'usern13.medidata.com.br/A' (in 'medidata.com.br'?) after reducing the advertised EDNS UDP packet size to 512 octets 24-Feb-2009 08:56:14.364 edns-disabled: success resolving 'medidata.com.br/A' (in 'medidata.com.br'?) after reducing the advertised EDNS UDP packet size to 512 octets 24-Feb-2009 08:56:14.395 edns-disabled: success resolving 'medidata.com.br/MX' (in 'medidata.com.br'?) after reducing the advertised EDNS UDP packet size to 512 octets 24-Feb-2009 08:56:14.450 edns-disabled: success resolving 'mx.terra.com.br/A' (in 'terra.com.br'?) after reducing the advertised EDNS UDP packet size to 512 octets 24-Feb-2009 08:56:17.015 edns-disabled: success resolving '20178203100.user.veloxzone.com.br/A' (in 'veloxzone.com.br'?) after reducing the advertised EDNS UDP packet size to 512 octets 24-Feb-2009 08:56:17.175 edns-disabled: success resolving '25.52.162.62.in-addr.arpa/PTR' (in '62.in-addr.arpa'?) after reducing the advertised EDNS UDP packet size to 512 octets 24-Feb-2009 08:56:17.577 edns-disabled: success resolving '77.20.103.85.in-addr.arpa/PTR' (in '85.in-addr.arpa'?) after reducing the advertised EDNS UDP packet size to 512 octets 24-Feb-2009 08:56:20.534 edns-disabled: success resolving '51.62.155.88.in-addr.arpa/PTR' (in '88.in-addr.arpa'?) after reducing the advertised EDNS UDP packet size to 512 octets 24-Feb-2009 08:56:21.016 edns-disabled: success resolving '84.7.198.81.in-addr.arpa/PTR' (in '81.in-addr.arpa'?) after reducing the advertised EDNS UDP packet size to 512 octets 24-Feb-2009 08:56:21.905 edns-disabled: success resolving '125.91.110.212.in-addr.arpa/PTR' (in '212.in-addr.arpa'?) after reducing the advertised EDNS UDP packet size to 512 octets 24-Feb-2009 08:56:22.488 edns-disabled: success resolving 'ns7.virtua.com.br/A' (in 'virtua.com.br'?) after reducing the advertised EDNS UDP packet size to 512 octets 24-Feb-2009 08:56:22.490 edns-disabled: success resolving 'ns8.virtua.com.br/A' (in 'virtua.com.br'?) after reducing the advertised EDNS UDP packet size to 512 octets --cut-- How can it reduce it from 512 that is in the config, down to 512? I was expecting to see only after disabling EDNS messages after setting the size(s) to 512. It seems to me that max-udp-size and/or edns-udp-size does not do what I want, wich is to use 512 bytes packets. OS: Solaris 10 (SunOS 5.10 13-01) BIND: 9.6.0-P1, threaded. Regards Jan Arild Lindstrøm ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: EDNS - edns-udp-size and max-udp-size
In message 200902240828.n1o8slln027...@mail42.nsc.no, Jan Arild =?iso-8859-1?
Q?Lindstr=F8m?= writes:
How can it reduce it from 512 that is in the config, down to 512?
The code just looks at the number of timeouts not at what
size was sent in the initial query. triededns512() records
when the DNS_FETCHOPT_EDNS512 has been set not when the
initial query advertised a receive buffer of 512 bytes.
if ((triededns512(fctx, query-addrinfo-sockaddr) ||
fctx-timeouts = (MAX_EDNS0_TIMEOUTS * 2))
(query-options DNS_FETCHOPT_NOEDNS0) == 0) {
query-options |= DNS_FETCHOPT_NOEDNS0;
fctx-reason = disabling EDNS;
} else if ((triededns(fctx, query-addrinfo-sockaddr) ||
fctx-timeouts = MAX_EDNS0_TIMEOUTS)
(query-options DNS_FETCHOPT_NOEDNS0) == 0) {
query-options |= DNS_FETCHOPT_EDNS512;
fctx-reason = reducing the advertised EDNS UDP packet
size to 512 octets;
}
I was expecting to see only after disabling EDNS messages after setting t=
he size(s) to 512.
It seems to me that max-udp-size and/or edns-udp-size does not do what I wa=
nt, wich is to use 512 bytes packets.
max-udp-size controls the size of packets you send.
edns-udp-size controls the size of packets you receive.
A pack trace should show you that they are working as you
wont see UDP packets over 512 bytes in either direction is
you have that set.
What you need to find out is what is causing the packet
loss. Even with a clear EDNS path you will see some of
these logged as not all timeouts are due to EDNS issues.
Mark
OS: Solaris 10 (SunOS 5.10 13-01)
BIND: 9.6.0-P1, threaded.
Regards
Jan Arild Lindstr=F8m
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: mark_andr...@isc.org
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: EDNS - edns-udp-size and max-udp-size
The code just looks at the number of timeouts not at what size was sent in the initial query. triededns512() records when the DNS_FETCHOPT_EDNS512 has been set not when the initial query advertised a receive buffer of 512 bytes. But, if the initial query uses a receive buffer of 512 bytes or less, can't we just set DNS_FETCHOPT_EDNS512 straight off and save a step? eh ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: EDNS - edns-udp-size and max-udp-size
In message 20090225002133.gb99...@isc.org, Evan Hunt writes: The code just looks at the number of timeouts not at what size was sent in the initial query. triededns512() records when the DNS_FETCHOPT_EDNS512 has been set not when the initial query advertised a receive buffer of 512 bytes. But, if the initial query uses a receive buffer of 512 bytes or less, can't we just set DNS_FETCHOPT_EDNS512 straight off and save a step? eh One could but, as was evident from the logs, it would cause named to switch back to plain DNS more often when it didn't need to. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: mark_andr...@isc.org ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
