On Fri, 2018-01-19 at 14:54 +0000, Tony Finch wrote: > > Those responses look like referrals from the root servers to the .com > servers;
Ahhh. Right. That makes sense. > I would expect you to see `named` repeating the queries as it > follows the iterative resolution algorithm. Indeed. I will looking further down the log then... So, between that initial: 19-Jan-2018 09:06:18.893 resquery 0x7f1010f3bd90 (fctx 0x7f1010f23d90(www.google.com/A)): response is just the referrals to .com for that query and the referrals to .com for the subsequent ns[1-4].google.com queries before we get to: 19-Jan-2018 09:06:18.967 client 10.75.22.32#21585 (www.google.com): query failed (SERVFAIL) for www.google.com/IN/A at query.c:7007 19-Jan-2018 09:06:18.967 client 10.75.22.32#21585 (www.google.com): error 19-Jan-2018 09:06:18.967 client 10.75.22.32#21585 (www.google.com): send 19-Jan-2018 09:06:18.967 client 10.75.22.32#21585 (www.google.com): sendto 19-Jan-2018 09:06:18.967 client 10.75.22.32#21585 (www.google.com): senddone 19-Jan-2018 09:06:18.967 client 10.75.22.32#21585 (www.google.com): next 19-Jan-2018 09:06:18.967 client 10.75.22.32#21585 (www.google.com): ns_client_detach: ref = 0 19-Jan-2018 09:06:18.967 client 10.75.22.32#21585 (www.google.com): endrequest 19-Jan-2018 09:06:18.967 fetch completed at resolver.c:7415 for www.google.com/A in 0.547099: SERVFAIL/success [domain:com,referral:1,restart:0,qrysent:0,timeout:0,lame:0,neterr:0,badresp:0,adberr:0,findfail:0,valfail:0] 19-Jan-2018 09:06:18.967 fetch 0x7f1012541cd0 (fctx 0x7f1010f23d90(www.google.com/A)): destroyfetch 19-Jan-2018 09:06:18.967 client 10.75.22.32#1145 (www.google.com): query failed (SERVFAIL) for www.google.com/IN/A at query.c:7007 19-Jan-2018 09:06:18.967 client 10.75.22.32#1145 (www.google.com): error 19-Jan-2018 09:06:18.967 client 10.75.22.32#1145 (www.google.com): send 19-Jan-2018 09:06:18.967 client 10.75.22.32#1145 (www.google.com): sendto 19-Jan-2018 09:06:18.967 client 10.75.22.32#1145 (www.google.com): senddone 19-Jan-2018 09:06:18.967 client 10.75.22.32#1145 (www.google.com): next 19-Jan-2018 09:06:18.967 client 10.75.22.32#1145 (www.google.com): ns_client_detach: ref = 0 19-Jan-2018 09:06:18.967 client 10.75.22.32#1145 (www.google.com): endrequest 19-Jan-2018 09:06:18.968 fetch 0x7f102c5def88 (fctx 0x7f1010f23d90(www.google.com/A)): destroyfetch 19-Jan-2018 09:06:18.968 fctx 0x7f1010f23d90(www.google.com/A): shutdown 19-Jan-2018 09:06:18.968 fetch 0x7f10125423f0 (fctx 0x7f1010d86e80(ns1.google.com/A)): destroyfetch 19-Jan-2018 09:06:18.968 fctx 0x7f1010d86e80(ns1.google.com/A): shutdown 19-Jan-2018 09:06:18.968 adb: fetch of 'ns1.google.com' A failed: SERVFAIL 19-Jan-2018 09:06:18.968 DNS_EVENT_ADBNOMOREADDRESSES 19-Jan-2018 09:06:18.968 cfan: skipping find 0x7f10228d7630 19-Jan-2018 09:06:18.968 fetch 0x7f10191e91e8 (fctx 0x7f1010d88a40(ns1.google.com/AAAA)): destroyfetch 19-Jan-2018 09:06:18.968 fctx 0x7f1010d88a40(ns1.google.com/AAAA): shutdown 19-Jan-2018 09:06:18.968 adb: fetch of 'ns1.google.com' AAAA failed: SERVFAIL 19-Jan-2018 09:06:18.968 DNS_EVENT_ADBNOMOREADDRESSES 19-Jan-2018 09:06:18.968 cfan: processing find 0x7f10228d7630 19-Jan-2018 09:06:18.968 sending event 0x7f10228d76b8 to task 0x7f10247a2f10 for find 0x7f10228d7630 19-Jan-2018 09:06:18.968 fetch 0x7f102069a2d0 (fctx 0x7f1010a83a60(ns2.google.com/A)): destroyfetch 19-Jan-2018 09:06:18.968 fctx 0x7f1010a83a60(ns2.google.com/A): shutdown 19-Jan-2018 09:06:18.968 adb: fetch of 'ns2.google.com' A failed: SERVFAIL 19-Jan-2018 09:06:18.968 DNS_EVENT_ADBNOMOREADDRESSES 19-Jan-2018 09:06:18.968 cfan: skipping find 0x7f10208679e0 19-Jan-2018 09:06:18.968 fetch 0x7f10206998b0 (fctx 0x7f1010a83ea0(ns2.google.com/AAAA)): destroyfetch 19-Jan-2018 09:06:18.968 fctx 0x7f1010a83ea0(ns2.google.com/AAAA): shutdown 19-Jan-2018 09:06:18.968 adb: fetch of 'ns2.google.com' AAAA failed: SERVFAIL 19-Jan-2018 09:06:18.968 DNS_EVENT_ADBNOMOREADDRESSES 19-Jan-2018 09:06:18.968 cfan: processing find 0x7f10208679e0 19-Jan-2018 09:06:18.968 sending event 0x7f1020867a68 to task 0x7f10247a2f10 for find 0x7f10208679e0 19-Jan-2018 09:06:18.968 fetch 0x7f102112d400 (fctx 0x7f1010b6bee0(ns3.google.com/AAAA)): destroyfetch 19-Jan-2018 09:06:18.970 fctx 0x7f1010b6bee0(ns3.google.com/AAAA): shutdown 19-Jan-2018 09:06:18.970 adb: fetch of 'ns3.google.com' AAAA failed: SERVFAIL 19-Jan-2018 09:06:18.970 DNS_EVENT_ADBNOMOREADDRESSES 19-Jan-2018 09:06:18.970 cfan: skipping find 0x7f102309fc10 19-Jan-2018 09:06:18.971 client fd31:aeb1:48df:0:e5f4:253a:6c1f:b73d#16975 (wifi-test.mobidia.com): query failed (SERVFAIL) for wifi-test.mobidia.com/IN/A at query.c:7007 19-Jan-2018 09:06:18.971 client fd31:aeb1:48df:0:e5f4:253a:6c1f:b73d#16975 (wifi-test.mobidia.com): error 19-Jan-2018 09:06:18.971 client fd31:aeb1:48df:0:e5f4:253a:6c1f:b73d#16975 (wifi-test.mobidia.com): send 19-Jan-2018 09:06:18.971 client fd31:aeb1:48df:0:e5f4:253a:6c1f:b73d#16975 (wifi-test.mobidia.com): sendto 19-Jan-2018 09:06:18.971 client fd31:aeb1:48df:0:e5f4:253a:6c1f:b73d#16975 (wifi-test.mobidia.com): senddone 19-Jan-2018 09:06:18.971 client fd31:aeb1:48df:0:e5f4:253a:6c1f:b73d#16975 (wifi-test.mobidia.com): next 19-Jan-2018 09:06:18.971 client fd31:aeb1:48df:0:e5f4:253a:6c1f:b73d#16975 (wifi-test.mobidia.com): ns_client_detach: ref = 0 19-Jan-2018 09:06:18.971 client fd31:aeb1:48df:0:e5f4:253a:6c1f:b73d#16975 (wifi-test.mobidia.com): endrequest 19-Jan-2018 09:06:18.971 fetch completed at resolver.c:7415 for wifi-test.mobidia.com/A in 0.583117: SERVFAIL/success [domain:com,referral:1,restart:0,qrysent:0,timeout:0,lame:0,neterr:0,badresp:0,adberr:0,findfail:0,valfail:0] 19-Jan-2018 09:06:18.972 fetch 0x7f102069a060 (fctx 0x7f1023af0b10(wifi-test.mobidia.com/A)): destroyfetch 19-Jan-2018 09:06:18.972 fctx 0x7f1023af0b10(wifi-test.mobidia.com/A): shutdown 19-Jan-2018 09:06:18.972 checkhints: unable to get root NS rrset from cache: not found 19-Jan-2018 09:06:18.974 fetch 0x7f10206998f8 (fctx 0x7f101094e3e0(./NS)): destroyfetch 19-Jan-2018 09:06:18.974 fctx 0x7f101094e3e0(./NS): shutdown 19-Jan-2018 09:06:18.974 fctx 0x7f1010f12610(www.google.com/A): start 19-Jan-2018 09:06:18.974 fctx 0x7f1010f12610(www.google.com/A): try 19-Jan-2018 09:06:18.974 fctx 0x7f1010f12610(www.google.com/A): cancelqueries 19-Jan-2018 09:06:18.974 fctx 0x7f1010f12610(www.google.com/A): getaddresses 19-Jan-2018 09:06:18.974 fctx 0x7f1010f12610(www.google.com/A): query 19-Jan-2018 09:06:18.974 resquery 0x7f1010f3bd90 (fctx 0x7f1010f12610(www.google.com/A)): send 19-Jan-2018 09:06:18.975 resquery 0x7f1010f3bd90 (fctx 0x7f1010f12610(www.google.com/A)): sent 19-Jan-2018 09:06:18.975 fctx 0x7f1010f23d90(www.google.com/A): doshutdown 19-Jan-2018 09:06:18.975 fctx 0x7f1010f23d90(www.google.com/A): stopeverything 19-Jan-2018 09:06:18.975 fctx 0x7f1010f23d90(www.google.com/A): cancelqueries 19-Jan-2018 09:06:18.975 fctx 0x7f1010f23d90(www.google.com/A): unlink 19-Jan-2018 09:06:18.976 fctx 0x7f1010f23d90(www.google.com/A): destroy 19-Jan-2018 09:06:18.976 resquery 0x7f1010f3bd90 (fctx 0x7f1010f12610(www.google.com/A)): udpconnected 19-Jan-2018 09:06:18.976 resquery 0x7f1010f3bd90 (fctx 0x7f1010f12610(www.google.com/A)): senddone Shouldn't I have seen at least some referrals from a .com NS to the google.com NSes similar to the referrals from the root server to the .com NSes? Cheers, b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users