[PATCH 3/3] use a larger starting EDNS UDP size, and add some debug logging

[Xuan Hung]

Dear Partner !
I think this problem of me, need have version new of Bind.
I think resolver of Bind.9.9.5 have problem when response for customer.
If recusive client of My DNS increase to 4000 then resolver response servfail.

============%%-
Nguyễn Xuân Hùng
0084-966581518
P.ISP– TT CNTT – VTNet.


-----Original Message-----
From: bind-workers-bounces at lists.isc.org [mailto:bind-workers-bounces at lists.isc.org] On Behalf Of Tony Finch
Sent: Monday, July 28, 2014 6:17 PM
To: bind-workers at lists.isc.org
Subject: [PATCH 3/3] use a larger starting EDNS UDP size, and add some debug logging

---
 lib/dns/resolver.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/lib/dns/resolver.c b/lib/dns/resolver.c index 884aeb8..0b48d1a 100644
--- a/lib/dns/resolver.c
+++ b/lib/dns/resolver.c
@@ -2022,10 +2022,10 @@ resquery_send(resquery_t *query) {

 			/*
 			 * We know nothing about the peer's capabilities
-			 * so start with minimal EDNS UDP size.
+			 * so start with moderate EDNS UDP size.
 			 */
 			if (udpsize == 0U)
-				udpsize = 512;
+				udpsize = 1232;

 			if ((flags & DNS_FETCHOPT_EDNSVERSIONSET) != 0) {
 				version = flags & DNS_FETCHOPT_EDNSVERSIONMASK; @@ -2103,6 +2103,8 @@ resquery_send(resquery_t *query) {
 	 * Record the UDP EDNS size choosen.
 	 */
 	query->udpsize = udpsize;
+	isc_log_write(dns_lctx,	DNS_LOGCATEGORY_RESOLVER, DNS_LOGMODULE_RESOLVER,
+	    ISC_LOG_DEBUG(10), "fctx %p(%s): udpsize %d", fctx, fctx->info, 
+udpsize);

 	if (udpsize > 0)
 		add_triededns(fctx, &query->addrinfo->sockaddr);
--
2.1.0.rc0.187.g3b9072a

_______________________________________________
bind-workers mailing list
bind-workers at lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-workers