Jan 20 22:12:22 rdns4m01 pdns_recursor[10815]: PowerDNS Recursor 3.6.2 (jenkins@autotest.powerdns.com) (C) 2001-2014 PowerDNS.COM BV Jan 20 22:12:22 rdns4m01 pdns_recursor[10815]: Using 64-bits mode. Built on 20141031140810 by mockbuild@, gcc 4.4.7 20120313 (Red Hat 4.4.7-11). Jan 20 22:12:22 rdns4m01 pdns_recursor[10815]: PowerDNS comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it according to the terms of the GPL version 2. Jan 20 22:12:22 rdns4m01 pdns_recursor[10815]: Reading random entropy from '/dev/urandom' Jan 20 22:12:22 rdns4m01 pdns_recursor[10815]: Done parsing 1 allow-from ranges from file '/etc/pdns-recursor/clients.acl' - overriding 'allow-from' setting Jan 20 22:12:22 rdns4m01 pdns_recursor[10815]: Will not send queries to: 127.0.0.0/8, 10.0.0.0/8, 100.64.0.0/10, 169.254.0.0/16, 192.168.0.0/16, 172.16.0.0/12, ::1/128, fe80::/10, 0.0.0.0, :: Jan 20 22:12:22 rdns4m01 pdns_recursor[10815]: PowerDNS Recursor itself will distribute queries over threads Jan 20 22:12:22 rdns4m01 pdns_recursor[10815]: NOT using IPv6 for outgoing queries - set 'query-local-address6=::' to enable Jan 20 22:12:22 rdns4m01 pdns_recursor[10815]: Inserting rfc 1918 private space zones Jan 20 22:12:22 rdns4m01 pdns_recursor[10815]: Listening for UDP queries on 127.0.0.1:53 Jan 20 22:12:22 rdns4m01 pdns_recursor[10815]: Listening for UDP queries on 186.16.16.26:53 Jan 20 22:12:22 rdns4m01 pdns_recursor[10815]: Listening for UDP queries on 186.16.16.16:53 Jan 20 22:12:22 rdns4m01 pdns_recursor[10815]: Enabled TCP data-ready filter for (slight) DoS protection Jan 20 22:12:22 rdns4m01 pdns_recursor[10815]: Listening for TCP queries on 127.0.0.1:53 Jan 20 22:12:22 rdns4m01 pdns_recursor[10815]: Listening for TCP queries on 186.16.16.26:53 Jan 20 22:12:22 rdns4m01 pdns_recursor[10815]: Listening for TCP queries on 186.16.16.16:53 Jan 20 22:12:22 rdns4m01 pdns_recursor[10815]: Calling daemonize, going to background Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: Set effective group id to 497 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: Set effective user id to 497 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: Insufficient number of filedescriptors available for max-mthreads*threads setting! (2048 < 34816), reducing max-mthreads to 481 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: Launching 17 threads Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: Done priming cache with root hints Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: Done priming cache with root hints Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: Done priming cache with root hints Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: Done priming cache with root hints Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: Done priming cache with root hints Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: Enabled 'epoll' multiplexer Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: Done priming cache with root hints Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: Done priming cache with root hints Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: Done priming cache with root hints Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: Done priming cache with root hints Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: Done priming cache with root hints Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: Done priming cache with root hints Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: Done priming cache with root hints Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: Done priming cache with root hints Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: Done priming cache with root hints Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: Done priming cache with root hints Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: Done priming cache with root hints Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: Done priming cache with root hints Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: No cache hit for '.|NS', trying to find an appropriate NS record Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: No cache hit for '.|NS', trying to find an appropriate NS record Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: Checking if we have NS in cache for '.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: No cache hit for '.|NS', trying to find an appropriate NS record Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: Checking if we have NS in cache for '.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'a.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'a.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: No cache hit for '.|NS', trying to find an appropriate NS record Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: Checking if we have NS in cache for '.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: Checking if we have NS in cache for '.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: No cache hit for '.|NS', trying to find an appropriate NS record Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: Checking if we have NS in cache for '.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'a.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'b.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: No cache hit for '.|NS', trying to find an appropriate NS record Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'a.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: No cache hit for '.|NS', trying to find an appropriate NS record Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: Checking if we have NS in cache for '.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: No cache hit for '.|NS', trying to find an appropriate NS record Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS in cache for '.', but needs glue (a.root-servers.net.) which we miss or is expired Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'b.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: No cache hit for '.|NS', trying to find an appropriate NS record Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: Checking if we have NS in cache for '.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: No cache hit for '.|NS', trying to find an appropriate NS record Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: Checking if we have NS in cache for '.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: Checking if we have NS in cache for '.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'a.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: No cache hit for '.|NS', trying to find an appropriate NS record Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: Checking if we have NS in cache for '.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'c.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'a.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: No cache hit for '.|NS', trying to find an appropriate NS record Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: Checking if we have NS in cache for '.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'a.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'a.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'b.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'b.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'c.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'd.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'e.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: No cache hit for '.|NS', trying to find an appropriate NS record Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: Checking if we have NS in cache for '.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'd.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'b.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'b.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'a.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: No cache hit for '.|NS', trying to find an appropriate NS record Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: Checking if we have NS in cache for '.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS in cache for '.', but needs glue (e.root-servers.net.) which we miss or is expired Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'f.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'f.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'b.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'c.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'd.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'e.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'f.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS in cache for '.', but needs glue (g.root-servers.net.) which we miss or is expired Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'i.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'j.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'k.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'l.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'm.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: We have NS in cache for '.' (flawedNSSet=1) Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: Cache consultations done, have 11 NS to contact Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: Nameservers: c.root-servers.net.(0.00ms), m.root-servers.net.(0.00ms), f.root-servers.net.(0.00ms), Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: a.root-servers.net.(0.00ms), b.root-servers.net.(0.00ms), j.root-servers.net.(0.00ms), Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: d.root-servers.net.(0.00ms), l.root-servers.net.(0.00ms), k.root-servers.net.(0.00ms), Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: e.root-servers.net.(0.00ms), i.root-servers.net.(0.00ms) Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: Trying to resolve NS 'c.root-servers.net.' (1/11) Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: c.root-servers.net.: Looking for CNAME cache hit of 'c.root-servers.net.|CNAME' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: c.root-servers.net.: No CNAME cache hit of 'c.root-servers.net.|CNAME' found Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: c.root-servers.net.: Found cache hit for A: 192.203.230.10[ttl=3600000] Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: Resolved '.' NS c.root-servers.net. to: 192.203.230.10 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: Trying IP 192.203.230.10:53, asking '.|NS' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: Checking if we have NS in cache for '.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'a.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'b.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'c.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'd.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'e.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'a.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS in cache for '.', but needs glue (b.root-servers.net.) which we miss or is expired Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS in cache for '.', but needs glue (c.root-servers.net.) which we miss or is expired Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS in cache for '.', but needs glue (c.root-servers.net.) which we miss or is expired Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'c.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: No cache hit for '.|NS', trying to find an appropriate NS record Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: Checking if we have NS in cache for '.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'a.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'g.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'b.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'g.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'h.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'c.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'd.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'b.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: No cache hit for '.|NS', trying to find an appropriate NS record Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: Checking if we have NS in cache for '.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'a.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'd.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'c.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'b.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'c.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'h.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'a.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'i.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'e.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'b.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'b.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'c.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'd.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'f.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'f.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'a.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'd.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'e.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'd.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'd.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'c.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'i.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'e.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'f.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'g.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'h.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'j.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'd.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'j.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'k.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'f.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'c.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'd.root-servers.net.' Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:22 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'e.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'c.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'k.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'e.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'i.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS in cache for '.', but needs glue (l.root-servers.net.) which we miss or is expired Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS in cache for '.', but needs glue (m.root-servers.net.) which we miss or is expired Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'e.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'f.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS in cache for '.', but needs glue (k.root-servers.net.) which we miss or is expired Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'l.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: We have NS in cache for '.' (flawedNSSet=1) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'f.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'g.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'b.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS in cache for '.', but needs glue (f.root-servers.net.) which we miss or is expired Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'b.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'c.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'g.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'i.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'j.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'k.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'g.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'c.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'f.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'e.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'l.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'g.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'd.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'e.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'e.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'm.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'm.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'e.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'f.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'd.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS in cache for '.', but needs glue (f.root-servers.net.) which we miss or is expired Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'g.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'l.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'g.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'h.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'e.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'm.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: We have NS in cache for '.' (flawedNSSet=1) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'f.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'g.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'h.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'i.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'h.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'i.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: We have NS in cache for '.' (flawedNSSet=1) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'j.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Cache consultations done, have 11 NS to contact Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'h.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS in cache for '.', but needs glue (i.root-servers.net.) which we miss or is expired Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'j.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'f.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'h.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Cache consultations done, have 12 NS to contact Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'k.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'l.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'j.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'h.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'g.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: We have NS in cache for '.' (flawedNSSet=1) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'k.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'g.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS in cache for '.', but needs glue (f.root-servers.net.) which we miss or is expired Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'h.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'i.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Cache consultations done, have 11 NS to contact Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'l.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'i.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Cache consultations done, have 9 NS to contact Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'i.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'h.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'i.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'j.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'k.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'l.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'g.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'g.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Nameservers: k.root-servers.net.(0.00ms), b.root-servers.net.(0.00ms), l.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'j.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'k.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'm.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'h.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'k.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS in cache for '.', but needs glue (l.root-servers.net.) which we miss or is expired Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'm.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'i.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'j.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'l.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'j.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS in cache for '.', but needs glue (h.root-servers.net.) which we miss or is expired Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'i.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: We have NS in cache for '.' (flawedNSSet=1) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Nameservers: e.root-servers.net.(0.00ms), i.root-servers.net.(0.00ms), k.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: We have NS in cache for '.' (flawedNSSet=1) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Nameservers: m.root-servers.net.(0.00ms), b.root-servers.net.(0.00ms), j.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'm.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: We have NS in cache for '.' (flawedNSSet=1) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Cache consultations done, have 12 NS to contact Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'k.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'l.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'm.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'j.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'l.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'j.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'k.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'k.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Cache consultations done, have 11 NS to contact Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'm.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: e.root-servers.net.(0.00ms), c.root-servers.net.(0.00ms), m.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: i.root-servers.net.(0.00ms), j.root-servers.net.(0.00ms), g.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'i.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Cache consultations done, have 11 NS to contact Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'm.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'l.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'm.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'l.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: We have NS in cache for '.' (flawedNSSet=0) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: We have NS in cache for '.' (flawedNSSet=1) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: a.root-servers.net.(0.00ms), d.root-servers.net.(0.00ms) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Nameservers: d.root-servers.net.(0.00ms), k.root-servers.net.(0.00ms), m.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Cache consultations done, have 12 NS to contact Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: We have NS in cache for '.' (flawedNSSet=1) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'm.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Nameservers: e.root-servers.net.(0.00ms), c.root-servers.net.(0.00ms), a.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: a.root-servers.net.(0.00ms), g.root-servers.net.(0.00ms), j.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'j.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'k.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: We have NS in cache for '.' (flawedNSSet=1) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'h.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: j.root-servers.net.(0.00ms), a.root-servers.net.(0.00ms), d.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Nameservers: a.root-servers.net.(0.00ms), e.root-servers.net.(0.00ms), b.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: g.root-servers.net.(0.00ms), k.root-servers.net.(0.00ms), a.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: g.root-servers.net.(0.00ms), f.root-servers.net.(0.00ms), b.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: h.root-servers.net.(0.00ms), c.root-servers.net.(0.00ms) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: g.root-servers.net.(0.00ms), h.root-servers.net.(0.00ms), d.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying to resolve NS 'k.root-servers.net.' (1/11) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: k.root-servers.net.: Looking for CNAME cache hit of 'k.root-servers.net.|CNAME' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: k.root-servers.net.: No CNAME cache hit of 'k.root-servers.net.|CNAME' found Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS in cache for '.', but needs glue (l.root-servers.net.) which we miss or is expired Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying to resolve NS 'e.root-servers.net.' (1/11) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: e.root-servers.net.: Looking for CNAME cache hit of 'e.root-servers.net.|CNAME' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: e.root-servers.net.: No CNAME cache hit of 'e.root-servers.net.|CNAME' found Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'm.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: f.root-servers.net.(0.00ms), e.root-servers.net.(0.00ms), i.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'i.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: We have NS in cache for '.' (flawedNSSet=0) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: k.root-servers.net.: Found cache hit for A: 193.0.14.129[ttl=3600000] Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Resolved '.' NS k.root-servers.net. to: 193.0.14.129 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: b.root-servers.net.(0.00ms), i.root-servers.net.(0.00ms), f.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Cache consultations done, have 13 NS to contact Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Cache consultations done, have 11 NS to contact Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: e.root-servers.net.: Found cache hit for A: 192.203.230.10[ttl=3600000] Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Cache consultations done, have 13 NS to contact Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: h.root-servers.net.(0.00ms), l.root-servers.net.(0.00ms) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying to resolve NS 'd.root-servers.net.' (1/11) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: d.root-servers.net.: Looking for CNAME cache hit of 'd.root-servers.net.|CNAME' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: d.root-servers.net.: No CNAME cache hit of 'd.root-servers.net.|CNAME' found Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Cache consultations done, have 11 NS to contact Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: We have NS in cache for '.' (flawedNSSet=1) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Resolved '.' NS e.root-servers.net. to: 192.203.230.10 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying IP 193.0.14.129:53, asking '.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying IP 192.203.230.10:53, asking '.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Nameservers: d.root-servers.net.(0.00ms), e.root-servers.net.(0.00ms), f.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: We have NS in cache for '.' (flawedNSSet=1) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Cache consultations done, have 11 NS to contact Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: l.root-servers.net.(0.00ms), f.root-servers.net.(0.00ms), c.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Cache consultations done, have 11 NS to contact Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Nameservers: l.root-servers.net.(0.00ms), a.root-servers.net.(0.00ms), d.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: d.root-servers.net.: Found cache hit for A: 192.112.36.4[ttl=3600000] Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Resolved '.' NS d.root-servers.net. to: 192.112.36.4 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'j.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Nameservers: d.root-servers.net.(0.00ms), e.root-servers.net.(0.00ms), g.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying IP 192.112.36.4:53, asking '.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: i.root-servers.net.(0.00ms), l.root-servers.net.(0.00ms), f.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'k.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: k.root-servers.net.(0.00ms), a.root-servers.net.(0.00ms), g.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Nameservers: l.root-servers.net.(0.00ms), k.root-servers.net.(0.00ms), a.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: i.root-servers.net.(0.00ms), h.root-servers.net.(0.00ms), d.root-servers.net.(0.00ms) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Nameservers: h.root-servers.net.(0.00ms), k.root-servers.net.(0.00ms), a.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Nameservers: k.root-servers.net.(0.00ms), a.root-servers.net.(0.00ms), j.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying to resolve NS 'm.root-servers.net.' (1/12) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: m.root-servers.net.: Looking for CNAME cache hit of 'm.root-servers.net.|CNAME' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: m.root-servers.net.: No CNAME cache hit of 'm.root-servers.net.|CNAME' found Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: f.root-servers.net.(0.00ms), m.root-servers.net.(0.00ms), i.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Nameservers: m.root-servers.net.(0.00ms), k.root-servers.net.(0.00ms), g.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS (with ip, or non-glue) in cache for '.' -> 'l.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: within bailiwick: 1, in cache, ttl=3600000 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: NS in cache for '.', but needs glue (m.root-servers.net.) which we miss or is expired Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Nameservers: f.root-servers.net.(0.00ms), g.root-servers.net.(0.00ms), i.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: m.root-servers.net.(0.00ms), e.root-servers.net.(0.00ms), j.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: We have NS in cache for '.' (flawedNSSet=1) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: j.root-servers.net.(0.00ms), k.root-servers.net.(0.00ms), m.root-servers.net.(0.00ms) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: h.root-servers.net.(0.00ms), j.root-servers.net.(0.00ms), l.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: g.root-servers.net.(0.00ms), i.root-servers.net.(0.00ms), h.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: c.root-servers.net.(0.00ms), b.root-servers.net.(0.00ms) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying to resolve NS 'e.root-servers.net.' (1/12) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: e.root-servers.net.: Looking for CNAME cache hit of 'e.root-servers.net.|CNAME' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: c.root-servers.net.(0.00ms), g.root-servers.net.(0.00ms), e.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: f.root-servers.net.(0.00ms), d.root-servers.net.(0.00ms), c.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: c.root-servers.net.(0.00ms), l.root-servers.net.(0.00ms), m.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: e.root-servers.net.: No CNAME cache hit of 'e.root-servers.net.|CNAME' found Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: m.root-servers.net.: Found cache hit for A: 202.12.27.33[ttl=3600000] Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Resolved '.' NS m.root-servers.net. to: 202.12.27.33 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying IP 202.12.27.33:53, asking '.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Cache consultations done, have 12 NS to contact Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: h.root-servers.net.(0.00ms), m.root-servers.net.(0.00ms), g.root-servers.net.(0.00ms) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: j.root-servers.net.(0.00ms), i.root-servers.net.(0.00ms), c.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying to resolve NS 'd.root-servers.net.' (1/11) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: d.root-servers.net.: Looking for CNAME cache hit of 'd.root-servers.net.|CNAME' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: b.root-servers.net.(0.00ms) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying to resolve NS 'l.root-servers.net.' (1/13) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: e.root-servers.net.(0.00ms), h.root-servers.net.(0.00ms), d.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: d.root-servers.net.: No CNAME cache hit of 'd.root-servers.net.|CNAME' found Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: f.root-servers.net.(0.00ms), c.root-servers.net.(0.00ms), h.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: l.root-servers.net.: Looking for CNAME cache hit of 'l.root-servers.net.|CNAME' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: a.root-servers.net.(0.00ms), h.root-servers.net.(0.00ms), j.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: l.root-servers.net.: No CNAME cache hit of 'l.root-servers.net.|CNAME' found Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: l.root-servers.net.: Found cache hit for A: 199.7.83.42[ttl=3600000] Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: d.root-servers.net.: Found cache hit for A: 202.12.27.33[ttl=3600000] Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Resolved '.' NS d.root-servers.net. to: 202.12.27.33 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying IP 202.12.27.33:53, asking '.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying to resolve NS 'a.root-servers.net.' (1/9) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: a.root-servers.net.: Looking for CNAME cache hit of 'a.root-servers.net.|CNAME' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: a.root-servers.net.: No CNAME cache hit of 'a.root-servers.net.|CNAME' found Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: j.root-servers.net.(0.00ms), k.root-servers.net.(0.00ms), h.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: b.root-servers.net.(0.00ms), a.root-servers.net.(0.00ms), j.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: b.root-servers.net.(0.00ms) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying to resolve NS 'l.root-servers.net.' (1/13) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: l.root-servers.net.: Looking for CNAME cache hit of 'l.root-servers.net.|CNAME' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: l.root-servers.net.: No CNAME cache hit of 'l.root-servers.net.|CNAME' found Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: l.root-servers.net.: Found cache hit for A: 199.7.83.42[ttl=3600000] Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: e.root-servers.net.(0.00ms), b.root-servers.net.(0.00ms), k.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: e.root-servers.net.: Found cache hit for A: 202.12.27.33[ttl=3600000] Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: l.root-servers.net.(0.00ms), m.root-servers.net.(0.00ms), c.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Nameservers: e.root-servers.net.(0.00ms), i.root-servers.net.(0.00ms), f.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: d.root-servers.net.(0.00ms), k.root-servers.net.(0.00ms), l.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: m.root-servers.net.(0.00ms), c.root-servers.net.(0.00ms) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying to resolve NS 'f.root-servers.net.' (1/11) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: f.root-servers.net.: Looking for CNAME cache hit of 'f.root-servers.net.|CNAME' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: f.root-servers.net.: No CNAME cache hit of 'f.root-servers.net.|CNAME' found Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: f.root-servers.net.: Found cache hit for A: 192.5.5.241[ttl=3600000] Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Resolved '.' NS f.root-servers.net. to: 192.5.5.241 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying IP 192.5.5.241:53, asking '.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Resolved '.' NS l.root-servers.net. to: 199.7.83.42 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying IP 199.7.83.42:53, asking '.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Resolved '.' NS e.root-servers.net. to: 202.12.27.33 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying IP 202.12.27.33:53, asking '.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: b.root-servers.net.(0.00ms), l.root-servers.net.(0.00ms), e.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Resolved '.' NS l.root-servers.net. to: 199.7.83.42 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying IP 199.7.83.42:53, asking '.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: b.root-servers.net.(0.00ms), i.root-servers.net.(0.00ms) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: a.root-servers.net.: Found cache hit for A: 198.41.0.4[ttl=3600000] Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: i.root-servers.net.(0.00ms), f.root-servers.net.(0.00ms) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying to resolve NS 'd.root-servers.net.' (1/11) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: d.root-servers.net.: Looking for CNAME cache hit of 'd.root-servers.net.|CNAME' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: d.root-servers.net.: No CNAME cache hit of 'd.root-servers.net.|CNAME' found Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: d.root-servers.net.: Found cache hit for A: 128.63.2.53[ttl=3600000] Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: b.root-servers.net.(0.00ms), h.root-servers.net.(0.00ms), j.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: d.root-servers.net.(0.00ms), b.root-servers.net.(0.00ms), j.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Resolved '.' NS d.root-servers.net. to: 128.63.2.53 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying IP 128.63.2.53:53, asking '.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Resolved '.' NS a.root-servers.net. to: 198.41.0.4 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying IP 198.41.0.4:53, asking '.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying to resolve NS 'k.root-servers.net.' (1/11) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: k.root-servers.net.: Looking for CNAME cache hit of 'k.root-servers.net.|CNAME' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: k.root-servers.net.: No CNAME cache hit of 'k.root-servers.net.|CNAME' found Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: d.root-servers.net.(0.00ms), m.root-servers.net.(0.00ms), g.root-servers.net.(0.00ms) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: k.root-servers.net.: Found cache hit for A: 193.0.14.129[ttl=3600000] Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: c.root-servers.net.(0.00ms), a.root-servers.net.(0.00ms), g.root-servers.net.(0.00ms) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying to resolve NS 'e.root-servers.net.' (1/12) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: e.root-servers.net.: Looking for CNAME cache hit of 'e.root-servers.net.|CNAME' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: e.root-servers.net.: No CNAME cache hit of 'e.root-servers.net.|CNAME' found Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: l.root-servers.net.(0.00ms), i.root-servers.net.(0.00ms) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying to resolve NS 'h.root-servers.net.' (1/12) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: h.root-servers.net.: Looking for CNAME cache hit of 'h.root-servers.net.|CNAME' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: h.root-servers.net.: No CNAME cache hit of 'h.root-servers.net.|CNAME' found Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Resolved '.' NS k.root-servers.net. to: 193.0.14.129 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying IP 193.0.14.129:53, asking '.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: e.root-servers.net.: Found cache hit for A: 192.203.230.10[ttl=3600000] Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Resolved '.' NS e.root-servers.net. to: 192.203.230.10 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying to resolve NS 'm.root-servers.net.' (1/11) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: m.root-servers.net.: Looking for CNAME cache hit of 'm.root-servers.net.|CNAME' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: m.root-servers.net.: No CNAME cache hit of 'm.root-servers.net.|CNAME' found Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: m.root-servers.net.: Found cache hit for A: 202.12.27.33[ttl=3600000] Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Resolved '.' NS m.root-servers.net. to: 202.12.27.33 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying IP 202.12.27.33:53, asking '.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying IP 192.203.230.10:53, asking '.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: h.root-servers.net.: Found cache hit for A: 128.63.2.53[ttl=3600000] Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Resolved '.' NS h.root-servers.net. to: 128.63.2.53 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Trying IP 128.63.2.53:53, asking '.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Got 28 answers from c.root-servers.net. (192.203.230.10), rcode=0 (No Error), aa=1, in 187ms Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|a.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|b.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|c.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|d.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|e.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|f.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|g.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|h.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|i.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|j.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|k.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|l.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|m.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|A|198.41.0.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|A|192.228.79.201' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'c.root-servers.net.|A|192.33.4.12' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'd.root-servers.net.|A|199.7.91.13' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'e.root-servers.net.|A|192.203.230.10' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'f.root-servers.net.|A|192.5.5.241' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'g.root-servers.net.|A|192.112.36.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'h.root-servers.net.|A|128.63.2.53' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'i.root-servers.net.|A|192.36.148.17' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'j.root-servers.net.|A|192.58.128.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'k.root-servers.net.|A|193.0.14.129' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'l.root-servers.net.|A|199.7.83.42' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'm.root-servers.net.|A|202.12.27.33' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|AAAA|2001:503:ba3e::2:30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|AAAA|2001:500:84::b' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: determining status after receiving this packet Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'a.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'b.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'c.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'd.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'e.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'f.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'g.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'h.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'i.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'j.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'k.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'l.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'm.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: status=got results, this level of recursion done Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: Refreshed . records Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Got 28 answers from l.root-servers.net. (199.7.83.42), rcode=0 (No Error), aa=1, in 203ms Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|a.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|b.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|c.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|d.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|e.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|f.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|g.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|h.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|i.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|j.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|k.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|l.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|m.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|A|198.41.0.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|A|192.228.79.201' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'c.root-servers.net.|A|192.33.4.12' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'd.root-servers.net.|A|199.7.91.13' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'e.root-servers.net.|A|192.203.230.10' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'f.root-servers.net.|A|192.5.5.241' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'g.root-servers.net.|A|192.112.36.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'h.root-servers.net.|A|128.63.2.53' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'i.root-servers.net.|A|192.36.148.17' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'j.root-servers.net.|A|192.58.128.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'k.root-servers.net.|A|193.0.14.129' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'l.root-servers.net.|A|199.7.83.42' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'm.root-servers.net.|A|202.12.27.33' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|AAAA|2001:503:ba3e::2:30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|AAAA|2001:500:84::b' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: determining status after receiving this packet Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'a.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'b.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'c.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'd.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'e.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'f.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'g.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'h.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'i.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'j.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'k.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'l.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'm.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: status=got results, this level of recursion done Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: Refreshed . records Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Got 28 answers from e.root-servers.net. (192.203.230.10), rcode=0 (No Error), aa=1, in 206ms Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|a.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Got 28 answers from f.root-servers.net. (192.5.5.241), rcode=0 (No Error), aa=1, in 206ms Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|b.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|j.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|h.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|c.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|f.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|d.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|a.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|e.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|e.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|c.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|f.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|d.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|g.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|m.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|i.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|h.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|i.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|g.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|k.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|j.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|l.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|k.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|b.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|A|198.41.0.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|l.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|A|192.228.79.201' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'c.root-servers.net.|A|192.33.4.12' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|m.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'd.root-servers.net.|A|199.7.91.13' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'e.root-servers.net.|A|192.203.230.10' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|A|198.41.0.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'f.root-servers.net.|A|192.5.5.241' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|A|192.228.79.201' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'g.root-servers.net.|A|192.112.36.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'c.root-servers.net.|A|192.33.4.12' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'd.root-servers.net.|A|199.7.91.13' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'h.root-servers.net.|A|128.63.2.53' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'e.root-servers.net.|A|192.203.230.10' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'f.root-servers.net.|A|192.5.5.241' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'i.root-servers.net.|A|192.36.148.17' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'g.root-servers.net.|A|192.112.36.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'j.root-servers.net.|A|192.58.128.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'h.root-servers.net.|A|128.63.2.53' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'k.root-servers.net.|A|193.0.14.129' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'l.root-servers.net.|A|199.7.83.42' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'i.root-servers.net.|A|192.36.148.17' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'm.root-servers.net.|A|202.12.27.33' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'j.root-servers.net.|A|192.58.128.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|AAAA|2001:503:ba3e::2:30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'k.root-servers.net.|A|193.0.14.129' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|AAAA|2001:500:84::b' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'l.root-servers.net.|A|199.7.83.42' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'm.root-servers.net.|A|202.12.27.33' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|AAAA|2001:503:ba3e::2:30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|AAAA|2001:500:84::b' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: determining status after receiving this packet Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'j.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'h.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'f.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'a.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'e.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'c.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: determining status after receiving this packet Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'a.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'b.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'c.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'd.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'e.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'f.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'g.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'd.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'm.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'i.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'g.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'k.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'l.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'b.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: status=got results, this level of recursion done Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'h.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'i.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: Refreshed . records Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'j.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'k.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'l.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'm.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: status=got results, this level of recursion done Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: Refreshed . records Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Got 28 answers from k.root-servers.net. (193.0.14.129), rcode=0 (No Error), aa=1, in 210ms Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|a.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|b.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|c.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|d.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|e.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|f.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|g.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|h.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|i.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|j.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|k.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|l.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|m.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|A|198.41.0.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|A|192.228.79.201' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'c.root-servers.net.|A|192.33.4.12' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'd.root-servers.net.|A|199.7.91.13' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'e.root-servers.net.|A|192.203.230.10' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'f.root-servers.net.|A|192.5.5.241' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'g.root-servers.net.|A|192.112.36.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'h.root-servers.net.|A|128.63.2.53' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'i.root-servers.net.|A|192.36.148.17' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'j.root-servers.net.|A|192.58.128.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'k.root-servers.net.|A|193.0.14.129' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'l.root-servers.net.|A|199.7.83.42' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'm.root-servers.net.|A|202.12.27.33' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|AAAA|2001:503:ba3e::2:30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|AAAA|2001:500:84::b' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: determining status after receiving this packet Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'a.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'b.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'c.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'd.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'e.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'f.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'g.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'h.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'i.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'j.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'k.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'l.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'm.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: status=got results, this level of recursion done Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: Refreshed . records Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Got 28 answers from l.root-servers.net. (199.7.83.42), rcode=0 (No Error), aa=1, in 213ms Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|a.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|b.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|c.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|d.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|e.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|f.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|g.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|h.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|i.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|j.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|k.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|l.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|m.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|A|198.41.0.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|A|192.228.79.201' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'c.root-servers.net.|A|192.33.4.12' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'd.root-servers.net.|A|199.7.91.13' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'e.root-servers.net.|A|192.203.230.10' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'f.root-servers.net.|A|192.5.5.241' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'g.root-servers.net.|A|192.112.36.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'h.root-servers.net.|A|128.63.2.53' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'i.root-servers.net.|A|192.36.148.17' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'j.root-servers.net.|A|192.58.128.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'k.root-servers.net.|A|193.0.14.129' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'l.root-servers.net.|A|199.7.83.42' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'm.root-servers.net.|A|202.12.27.33' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|AAAA|2001:503:ba3e::2:30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|AAAA|2001:500:84::b' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: determining status after receiving this packet Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'a.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'b.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'c.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'd.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'e.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'f.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'g.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'h.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'i.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'j.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'k.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'l.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'm.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: status=got results, this level of recursion done Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: Refreshed . records Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Got 28 answers from e.root-servers.net. (192.203.230.10), rcode=0 (No Error), aa=1, in 213ms Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|a.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|b.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Got 28 answers from k.root-servers.net. (193.0.14.129), rcode=0 (No Error), aa=1, in 214ms Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|a.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|b.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|c.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|d.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|e.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|f.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|c.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|g.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|h.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|i.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|j.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|k.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|l.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|m.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|A|198.41.0.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|A|192.228.79.201' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'c.root-servers.net.|A|192.33.4.12' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'd.root-servers.net.|A|199.7.91.13' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'e.root-servers.net.|A|192.203.230.10' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'f.root-servers.net.|A|192.5.5.241' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|d.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|e.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'g.root-servers.net.|A|192.112.36.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'h.root-servers.net.|A|128.63.2.53' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'i.root-servers.net.|A|192.36.148.17' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'j.root-servers.net.|A|192.58.128.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'k.root-servers.net.|A|193.0.14.129' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'l.root-servers.net.|A|199.7.83.42' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'm.root-servers.net.|A|202.12.27.33' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|AAAA|2001:503:ba3e::2:30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|AAAA|2001:500:84::b' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|f.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|g.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: determining status after receiving this packet Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'a.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'b.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'c.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'd.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'e.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'f.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'g.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'h.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'i.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'j.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'k.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'l.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'm.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: status=got results, this level of recursion done Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|h.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: Refreshed . records Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|i.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|j.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|k.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|l.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|m.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|A|198.41.0.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|A|192.228.79.201' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'c.root-servers.net.|A|192.33.4.12' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'd.root-servers.net.|A|199.7.91.13' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'e.root-servers.net.|A|192.203.230.10' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'f.root-servers.net.|A|192.5.5.241' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'g.root-servers.net.|A|192.112.36.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'h.root-servers.net.|A|128.63.2.53' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'i.root-servers.net.|A|192.36.148.17' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'j.root-servers.net.|A|192.58.128.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'k.root-servers.net.|A|193.0.14.129' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'l.root-servers.net.|A|199.7.83.42' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'm.root-servers.net.|A|202.12.27.33' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|AAAA|2001:503:ba3e::2:30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|AAAA|2001:500:84::b' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: determining status after receiving this packet Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'a.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'b.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'c.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'd.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'e.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'f.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'g.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'h.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'i.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'j.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'k.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'l.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'm.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: status=got results, this level of recursion done Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: Refreshed . records Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Got 28 answers from d.root-servers.net. (192.112.36.4), rcode=0 (No Error), aa=1, in 217ms Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|f.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|d.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|g.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|c.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|b.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|e.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|l.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|k.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|m.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|h.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|i.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|j.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|a.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|A|198.41.0.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|A|192.228.79.201' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'c.root-servers.net.|A|192.33.4.12' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'd.root-servers.net.|A|199.7.91.13' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'e.root-servers.net.|A|192.203.230.10' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'f.root-servers.net.|A|192.5.5.241' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'g.root-servers.net.|A|192.112.36.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'h.root-servers.net.|A|128.63.2.53' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'i.root-servers.net.|A|192.36.148.17' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'j.root-servers.net.|A|192.58.128.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'k.root-servers.net.|A|193.0.14.129' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'l.root-servers.net.|A|199.7.83.42' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'm.root-servers.net.|A|202.12.27.33' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|AAAA|2001:503:ba3e::2:30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|AAAA|2001:500:84::b' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: determining status after receiving this packet Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'f.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'd.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'g.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'c.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'b.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'e.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'l.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'k.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'm.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'h.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'i.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'j.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'a.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: status=got results, this level of recursion done Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: Refreshed . records Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Got 28 answers from d.root-servers.net. (128.63.2.53), rcode=0 (No Error), aa=1, in 218ms Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|a.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|b.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|c.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|d.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|e.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|f.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|g.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|h.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|i.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|j.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|k.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|l.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|m.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|A|198.41.0.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|A|192.228.79.201' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'c.root-servers.net.|A|192.33.4.12' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'd.root-servers.net.|A|199.7.91.13' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'e.root-servers.net.|A|192.203.230.10' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'f.root-servers.net.|A|192.5.5.241' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'g.root-servers.net.|A|192.112.36.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'h.root-servers.net.|A|128.63.2.53' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'i.root-servers.net.|A|192.36.148.17' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'j.root-servers.net.|A|192.58.128.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'k.root-servers.net.|A|193.0.14.129' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'l.root-servers.net.|A|199.7.83.42' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'm.root-servers.net.|A|202.12.27.33' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|AAAA|2001:503:ba3e::2:30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|AAAA|2001:500:84::b' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: determining status after receiving this packet Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'a.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'b.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'c.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'd.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'e.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'f.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'g.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'h.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'i.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'j.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'k.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'l.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'm.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: status=got results, this level of recursion done Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: Refreshed . records Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Got 28 answers from h.root-servers.net. (128.63.2.53), rcode=0 (No Error), aa=1, in 232ms Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|a.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|b.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|c.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|d.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|e.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|f.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|g.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|h.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|i.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|j.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|k.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|l.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|m.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|A|198.41.0.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|A|192.228.79.201' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'c.root-servers.net.|A|192.33.4.12' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'd.root-servers.net.|A|199.7.91.13' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'e.root-servers.net.|A|192.203.230.10' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'f.root-servers.net.|A|192.5.5.241' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'g.root-servers.net.|A|192.112.36.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'h.root-servers.net.|A|128.63.2.53' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'i.root-servers.net.|A|192.36.148.17' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'j.root-servers.net.|A|192.58.128.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'k.root-servers.net.|A|193.0.14.129' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'l.root-servers.net.|A|199.7.83.42' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'm.root-servers.net.|A|202.12.27.33' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|AAAA|2001:503:ba3e::2:30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|AAAA|2001:500:84::b' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: determining status after receiving this packet Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'a.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'b.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'c.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'd.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'e.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'f.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'g.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'h.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'i.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'j.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'k.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'l.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'm.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: status=got results, this level of recursion done Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: Refreshed . records Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Looking for CNAME cache hit of 'recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.|CNAME' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: No CNAME cache hit of 'recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.|CNAME' found Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: No cache hit for 'recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.|TXT', trying to find an appropriate NS record Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Checking if we have NS in cache for 'recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: no valid/useful NS in cache for 'recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Checking if we have NS in cache for '6.2-1.el6.fedora.security-status.secpoll.powerdns.com.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: no valid/useful NS in cache for '6.2-1.el6.fedora.security-status.secpoll.powerdns.com.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Checking if we have NS in cache for '2-1.el6.fedora.security-status.secpoll.powerdns.com.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: no valid/useful NS in cache for '2-1.el6.fedora.security-status.secpoll.powerdns.com.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Checking if we have NS in cache for 'el6.fedora.security-status.secpoll.powerdns.com.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: no valid/useful NS in cache for 'el6.fedora.security-status.secpoll.powerdns.com.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Checking if we have NS in cache for 'fedora.security-status.secpoll.powerdns.com.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: no valid/useful NS in cache for 'fedora.security-status.secpoll.powerdns.com.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Checking if we have NS in cache for 'security-status.secpoll.powerdns.com.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: no valid/useful NS in cache for 'security-status.secpoll.powerdns.com.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Checking if we have NS in cache for 'secpoll.powerdns.com.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: no valid/useful NS in cache for 'secpoll.powerdns.com.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Checking if we have NS in cache for 'powerdns.com.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: no valid/useful NS in cache for 'powerdns.com.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Checking if we have NS in cache for 'com.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: no valid/useful NS in cache for 'com.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Checking if we have NS in cache for '.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: NS (with ip, or non-glue) in cache for '.' -> 'a.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: NS (with ip, or non-glue) in cache for '.' -> 'b.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: NS (with ip, or non-glue) in cache for '.' -> 'c.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: NS (with ip, or non-glue) in cache for '.' -> 'd.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: NS (with ip, or non-glue) in cache for '.' -> 'e.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: NS (with ip, or non-glue) in cache for '.' -> 'f.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: NS (with ip, or non-glue) in cache for '.' -> 'g.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: NS (with ip, or non-glue) in cache for '.' -> 'h.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: NS (with ip, or non-glue) in cache for '.' -> 'i.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: NS (with ip, or non-glue) in cache for '.' -> 'j.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: NS (with ip, or non-glue) in cache for '.' -> 'k.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: NS (with ip, or non-glue) in cache for '.' -> 'l.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: NS (with ip, or non-glue) in cache for '.' -> 'm.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: We have NS in cache for '.' (flawedNSSet=0) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Cache consultations done, have 13 NS to contact Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Nameservers: f.root-servers.net.(0.00ms), i.root-servers.net.(0.00ms), a.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: e.root-servers.net.(0.00ms), d.root-servers.net.(0.00ms), k.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: m.root-servers.net.(0.00ms), l.root-servers.net.(0.00ms), c.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: j.root-servers.net.(0.00ms), b.root-servers.net.(0.00ms), g.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: h.root-servers.net.(232.60ms) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Trying to resolve NS 'f.root-servers.net.' (1/13) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: f.root-servers.net.: Looking for CNAME cache hit of 'f.root-servers.net.|CNAME' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: f.root-servers.net.: No CNAME cache hit of 'f.root-servers.net.|CNAME' found Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: f.root-servers.net.: Found cache hit for A: 192.5.5.241[ttl=86400] Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Resolved '.' NS f.root-servers.net. to: 192.5.5.241 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Trying IP 192.5.5.241:53, asking 'recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.|TXT' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Got 28 answers from a.root-servers.net. (198.41.0.4), rcode=0 (No Error), aa=1, in 252ms Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|a.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|b.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|c.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|d.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|e.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|f.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|g.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|h.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|i.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|j.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|k.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|l.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|m.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|A|198.41.0.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|A|192.228.79.201' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'c.root-servers.net.|A|192.33.4.12' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'd.root-servers.net.|A|199.7.91.13' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'e.root-servers.net.|A|192.203.230.10' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'f.root-servers.net.|A|192.5.5.241' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'g.root-servers.net.|A|192.112.36.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'h.root-servers.net.|A|128.63.2.53' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'i.root-servers.net.|A|192.36.148.17' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'j.root-servers.net.|A|192.58.128.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'k.root-servers.net.|A|193.0.14.129' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'l.root-servers.net.|A|199.7.83.42' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'm.root-servers.net.|A|202.12.27.33' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|AAAA|2001:503:ba3e::2:30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|AAAA|2001:500:84::b' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: determining status after receiving this packet Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'a.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'b.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'c.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'd.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'e.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'f.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'g.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'h.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'i.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'j.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'k.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'l.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'm.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: status=got results, this level of recursion done Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: Refreshed . records Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Got 28 answers from e.root-servers.net. (202.12.27.33), rcode=0 (No Error), aa=1, in 265ms Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|e.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|d.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|b.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|k.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|i.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|f.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|h.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|g.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|m.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|j.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|a.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|c.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|l.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|A|198.41.0.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|A|192.228.79.201' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'c.root-servers.net.|A|192.33.4.12' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'd.root-servers.net.|A|199.7.91.13' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'e.root-servers.net.|A|192.203.230.10' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'f.root-servers.net.|A|192.5.5.241' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'g.root-servers.net.|A|192.112.36.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'h.root-servers.net.|A|128.63.2.53' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'i.root-servers.net.|A|192.36.148.17' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'j.root-servers.net.|A|192.58.128.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'k.root-servers.net.|A|193.0.14.129' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'l.root-servers.net.|A|199.7.83.42' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'm.root-servers.net.|A|202.12.27.33' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|AAAA|2001:503:ba3e::2:30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|AAAA|2001:500:84::b' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: determining status after receiving this packet Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'e.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'd.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'b.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'k.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'i.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'f.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'h.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'g.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'm.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'j.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'a.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'c.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'l.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: status=got results, this level of recursion done Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: Refreshed . records Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Got 28 answers from m.root-servers.net. (202.12.27.33), rcode=0 (No Error), aa=1, in 266ms Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|h.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|m.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|f.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|k.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|j.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|i.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|e.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|b.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|c.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|g.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|d.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|l.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|a.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|A|198.41.0.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|A|192.228.79.201' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'c.root-servers.net.|A|192.33.4.12' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'd.root-servers.net.|A|199.7.91.13' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'e.root-servers.net.|A|192.203.230.10' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'f.root-servers.net.|A|192.5.5.241' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'g.root-servers.net.|A|192.112.36.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'h.root-servers.net.|A|128.63.2.53' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'i.root-servers.net.|A|192.36.148.17' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'j.root-servers.net.|A|192.58.128.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'k.root-servers.net.|A|193.0.14.129' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'l.root-servers.net.|A|199.7.83.42' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'm.root-servers.net.|A|202.12.27.33' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|AAAA|2001:503:ba3e::2:30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|AAAA|2001:500:84::b' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: determining status after receiving this packet Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'h.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'm.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'f.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'k.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'j.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'i.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'e.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'b.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'c.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'g.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'd.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'l.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'a.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: status=got results, this level of recursion done Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: Refreshed . records Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Got 28 answers from d.root-servers.net. (202.12.27.33), rcode=0 (No Error), aa=1, in 270ms Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|k.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|l.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|b.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|m.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|d.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|e.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|g.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|c.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|j.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: Got 28 answers from m.root-servers.net. (202.12.27.33), rcode=0 (No Error), aa=1, in 270ms Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|e.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|f.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|i.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|m.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|a.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|h.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|d.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|l.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|b.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|f.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|A|198.41.0.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|A|192.228.79.201' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|j.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|c.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'c.root-servers.net.|A|192.33.4.12' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'd.root-servers.net.|A|199.7.91.13' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'e.root-servers.net.|A|192.203.230.10' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'f.root-servers.net.|A|192.5.5.241' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'g.root-servers.net.|A|192.112.36.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'h.root-servers.net.|A|128.63.2.53' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'i.root-servers.net.|A|192.36.148.17' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'j.root-servers.net.|A|192.58.128.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'k.root-servers.net.|A|193.0.14.129' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|g.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|h.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'l.root-servers.net.|A|199.7.83.42' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'm.root-servers.net.|A|202.12.27.33' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|AAAA|2001:503:ba3e::2:30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|i.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|AAAA|2001:500:84::b' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|k.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer '.|NS|a.root-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|A|198.41.0.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|A|192.228.79.201' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'c.root-servers.net.|A|192.33.4.12' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'd.root-servers.net.|A|199.7.91.13' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'e.root-servers.net.|A|192.203.230.10' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'f.root-servers.net.|A|192.5.5.241' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: determining status after receiving this packet Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'k.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'l.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'b.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'm.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'd.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'e.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'g.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'c.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'j.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'i.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'a.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'h.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'f.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: status=got results, this level of recursion done Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'g.root-servers.net.|A|192.112.36.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: Refreshed . records Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'h.root-servers.net.|A|128.63.2.53' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'i.root-servers.net.|A|192.36.148.17' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'j.root-servers.net.|A|192.58.128.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'k.root-servers.net.|A|193.0.14.129' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'l.root-servers.net.|A|199.7.83.42' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'm.root-servers.net.|A|202.12.27.33' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'a.root-servers.net.|AAAA|2001:503:ba3e::2:30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: accept answer 'b.root-servers.net.|AAAA|2001:500:84::b' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: determining status after receiving this packet Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'e.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'f.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'm.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'd.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'l.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'b.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'j.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'c.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'g.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'h.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'i.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'k.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: answer is in: resolved to 'a.root-servers.net.|NS' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: .: status=got results, this level of recursion done Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: Refreshed . records Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Got 25 answers from f.root-servers.net. (192.5.5.241), rcode=0 (No Error), aa=0, in 188ms Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'com.|NS|b.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'com.|NS|k.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'com.|NS|j.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'com.|NS|c.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'com.|NS|d.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'com.|NS|f.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'com.|NS|l.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'com.|NS|h.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'com.|NS|a.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'com.|NS|i.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'com.|NS|e.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'com.|NS|g.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'com.|NS|m.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'a.gtld-servers.net.|A|192.5.6.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'b.gtld-servers.net.|A|192.33.14.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'c.gtld-servers.net.|A|192.26.92.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'd.gtld-servers.net.|A|192.31.80.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'e.gtld-servers.net.|A|192.12.94.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'f.gtld-servers.net.|A|192.35.51.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'g.gtld-servers.net.|A|192.42.93.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'h.gtld-servers.net.|A|192.54.112.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'i.gtld-servers.net.|A|192.43.172.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'j.gtld-servers.net.|A|192.48.79.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'k.gtld-servers.net.|A|192.52.178.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'l.gtld-servers.net.|A|192.41.162.30' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: determining status after receiving this packet Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: got NS record 'com.' -> 'b.gtld-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: got NS record 'com.' -> 'k.gtld-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: got NS record 'com.' -> 'j.gtld-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: got NS record 'com.' -> 'c.gtld-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: got NS record 'com.' -> 'd.gtld-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: got NS record 'com.' -> 'f.gtld-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: got NS record 'com.' -> 'l.gtld-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: got NS record 'com.' -> 'h.gtld-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: got NS record 'com.' -> 'a.gtld-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: got NS record 'com.' -> 'i.gtld-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: got NS record 'com.' -> 'e.gtld-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: got NS record 'com.' -> 'g.gtld-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: got NS record 'com.' -> 'm.gtld-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: status=did not resolve, got 13 NS, looping to them Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Nameservers: e.gtld-servers.net.(0.00ms), g.gtld-servers.net.(0.00ms), a.gtld-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: j.gtld-servers.net.(0.00ms), d.gtld-servers.net.(0.00ms), i.gtld-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: l.gtld-servers.net.(0.00ms), b.gtld-servers.net.(0.00ms), m.gtld-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: f.gtld-servers.net.(0.00ms), k.gtld-servers.net.(0.00ms), c.gtld-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: h.gtld-servers.net.(0.00ms) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Trying to resolve NS 'e.gtld-servers.net.' (1/13) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: e.gtld-servers.net.: Looking for CNAME cache hit of 'e.gtld-servers.net.|CNAME' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: e.gtld-servers.net.: No CNAME cache hit of 'e.gtld-servers.net.|CNAME' found Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: e.gtld-servers.net.: Found cache hit for A: 192.12.94.30[ttl=86400] Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Resolved 'com.' NS e.gtld-servers.net. to: 192.12.94.30 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Trying IP 192.12.94.30:53, asking 'recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.|TXT' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Got 2 answers from e.gtld-servers.net. (192.12.94.30), rcode=0 (No Error), aa=0, in 282ms Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'powerdns.com.|NS|powerdnssec1.ds9a.nl.' from 'com.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'powerdns.com.|NS|powerdnssec2.ds9a.nl.' from 'com.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: determining status after receiving this packet Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: got NS record 'powerdns.com.' -> 'powerdnssec1.ds9a.nl.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: got NS record 'powerdns.com.' -> 'powerdnssec2.ds9a.nl.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: status=did not resolve, got 2 NS, looping to them Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Nameservers: powerdnssec1.ds9a.nl.(0.00ms), powerdnssec2.ds9a.nl.(0.00ms) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Trying to resolve NS 'powerdnssec1.ds9a.nl.' (1/2) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: Looking for CNAME cache hit of 'powerdnssec1.ds9a.nl.|CNAME' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: No CNAME cache hit of 'powerdnssec1.ds9a.nl.|CNAME' found Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: No cache hit for 'powerdnssec1.ds9a.nl.|A', trying to find an appropriate NS record Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: Checking if we have NS in cache for 'powerdnssec1.ds9a.nl.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: no valid/useful NS in cache for 'powerdnssec1.ds9a.nl.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: Checking if we have NS in cache for 'ds9a.nl.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: no valid/useful NS in cache for 'ds9a.nl.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: Checking if we have NS in cache for 'nl.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: no valid/useful NS in cache for 'nl.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: Checking if we have NS in cache for '.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: NS (with ip, or non-glue) in cache for '.' -> 'a.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: NS (with ip, or non-glue) in cache for '.' -> 'b.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: NS (with ip, or non-glue) in cache for '.' -> 'c.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: NS (with ip, or non-glue) in cache for '.' -> 'd.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: NS (with ip, or non-glue) in cache for '.' -> 'e.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: NS (with ip, or non-glue) in cache for '.' -> 'f.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: NS (with ip, or non-glue) in cache for '.' -> 'g.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: NS (with ip, or non-glue) in cache for '.' -> 'h.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: NS (with ip, or non-glue) in cache for '.' -> 'i.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: NS (with ip, or non-glue) in cache for '.' -> 'j.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: NS (with ip, or non-glue) in cache for '.' -> 'k.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: NS (with ip, or non-glue) in cache for '.' -> 'l.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: NS (with ip, or non-glue) in cache for '.' -> 'm.root-servers.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: We have NS in cache for '.' (flawedNSSet=0) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: Cache consultations done, have 13 NS to contact Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: Nameservers: a.root-servers.net.(0.00ms), l.root-servers.net.(0.00ms), m.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: g.root-servers.net.(0.00ms), d.root-servers.net.(0.00ms), k.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: c.root-servers.net.(0.00ms), e.root-servers.net.(0.00ms), i.root-servers.net.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: b.root-servers.net.(0.00ms), j.root-servers.net.(0.00ms), f.root-servers.net.(187.93ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: h.root-servers.net.(230.78ms) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: Trying to resolve NS 'a.root-servers.net.' (1/13) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: a.root-servers.net.: Looking for CNAME cache hit of 'a.root-servers.net.|CNAME' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: a.root-servers.net.: No CNAME cache hit of 'a.root-servers.net.|CNAME' found Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: a.root-servers.net.: Found cache hit for A: 198.41.0.4[ttl=86400] Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: Resolved '.' NS a.root-servers.net. to: 198.41.0.4 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: Trying IP 198.41.0.4:53, asking 'powerdnssec1.ds9a.nl.|A' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: Got 22 answers from a.root-servers.net. (198.41.0.4), rcode=0 (No Error), aa=0, in 230ms Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'nl.|NS|nl1.dnsnode.net.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'nl.|NS|ns1.dns.nl.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'nl.|NS|ns2.dns.nl.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'nl.|NS|ns3.dns.nl.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'nl.|NS|ns4.dns.nl.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'nl.|NS|ns5.dns.nl.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'nl.|NS|ns-nl.nic.fr.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'nl.|NS|sns-pb.isc.org.' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'nl1.dnsnode.net.|A|194.146.106.42' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'ns1.dns.nl.|A|193.176.144.5' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'ns2.dns.nl.|A|213.154.241.85' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'ns3.dns.nl.|A|194.171.17.10' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'ns4.dns.nl.|A|95.142.99.212' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'ns5.dns.nl.|A|194.0.28.53' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'ns-nl.nic.fr.|A|192.93.0.4' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'sns-pb.isc.org.|A|192.5.4.1' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'nl1.dnsnode.net.|AAAA|2001:67c:1010:10::53' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'ns1.dns.nl.|AAAA|2a00:d78:0:102:193:176:144:5' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'ns2.dns.nl.|AAAA|2001:7b8:606::85' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'ns3.dns.nl.|AAAA|2001:610:0:800d::10' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'ns4.dns.nl.|AAAA|2a00:1188:5::212' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'ns5.dns.nl.|AAAA|2001:678:2c:0:194:0:28:53' from '.' nameservers? YES! Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: determining status after receiving this packet Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: got NS record 'nl.' -> 'nl1.dnsnode.net.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: got NS record 'nl.' -> 'ns1.dns.nl.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: got NS record 'nl.' -> 'ns2.dns.nl.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: got NS record 'nl.' -> 'ns3.dns.nl.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: got NS record 'nl.' -> 'ns4.dns.nl.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: got NS record 'nl.' -> 'ns5.dns.nl.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: got NS record 'nl.' -> 'ns-nl.nic.fr.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: got NS record 'nl.' -> 'sns-pb.isc.org.' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: status=did not resolve, got 8 NS, looping to them Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: Nameservers: nl1.dnsnode.net.(0.00ms), ns-nl.nic.fr.(0.00ms), ns1.dns.nl.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: ns5.dns.nl.(0.00ms), ns4.dns.nl.(0.00ms), sns-pb.isc.org.(0.00ms), Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: ns2.dns.nl.(0.00ms), ns3.dns.nl.(0.00ms) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: Trying to resolve NS 'nl1.dnsnode.net.' (1/8) Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: nl1.dnsnode.net.: Looking for CNAME cache hit of 'nl1.dnsnode.net.|CNAME' Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: nl1.dnsnode.net.: No CNAME cache hit of 'nl1.dnsnode.net.|CNAME' found Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: nl1.dnsnode.net.: Found cache hit for A: 194.146.106.42[ttl=86400] Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: Resolved 'nl.' NS nl1.dnsnode.net. to: 194.146.106.42 Jan 20 22:12:23 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: Trying IP 194.146.106.42:53, asking 'powerdnssec1.ds9a.nl.|A' Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: Got 4 answers from nl1.dnsnode.net. (194.146.106.42), rcode=0 (No Error), aa=0, in 274ms Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'ds9a.nl.|NS|ns2.pine.nl.' from 'nl.' nameservers? YES! Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'ds9a.nl.|NS|ns1.pine.nl.' from 'nl.' nameservers? YES! Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'ns1.pine.nl.|A|213.156.2.1' from 'nl.' nameservers? YES! Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'ns2.pine.nl.|A|217.114.101.235' from 'nl.' nameservers? YES! Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: determining status after receiving this packet Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: got NS record 'ds9a.nl.' -> 'ns2.pine.nl.' Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: got NS record 'ds9a.nl.' -> 'ns1.pine.nl.' Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: status=did not resolve, got 2 NS, looping to them Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: Nameservers: ns2.pine.nl.(0.00ms), ns1.pine.nl.(0.00ms) Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: Trying to resolve NS 'ns2.pine.nl.' (1/2) Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: ns2.pine.nl.: Looking for CNAME cache hit of 'ns2.pine.nl.|CNAME' Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: ns2.pine.nl.: No CNAME cache hit of 'ns2.pine.nl.|CNAME' found Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: ns2.pine.nl.: Found cache hit for A: 217.114.101.235[ttl=7200] Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: Resolved 'ds9a.nl.' NS ns2.pine.nl. to: 217.114.101.235 Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: Trying IP 217.114.101.235:53, asking 'powerdnssec1.ds9a.nl.|A' Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: Got 5 answers from ns2.pine.nl. (217.114.101.235), rcode=0 (No Error), aa=1, in 261ms Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'powerdnssec1.ds9a.nl.|A|82.94.213.34' from 'ds9a.nl.' nameservers? YES! Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'ds9a.nl.|NS|ns2.pine.nl.' from 'ds9a.nl.' nameservers? YES! Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'ds9a.nl.|NS|ns1.pine.nl.' from 'ds9a.nl.' nameservers? YES! Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'ns1.pine.nl.|A|213.156.2.1' from 'ds9a.nl.' nameservers? NO! Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: accept answer 'ns2.pine.nl.|A|217.114.101.235' from 'ds9a.nl.' nameservers? NO! Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: determining status after receiving this packet Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: answer is in: resolved to '82.94.213.34|A' Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: got upwards/level NS record 'ds9a.nl.' -> 'ns2.pine.nl.', had 'ds9a.nl.' Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: got upwards/level NS record 'ds9a.nl.' -> 'ns1.pine.nl.', had 'ds9a.nl.' Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: powerdnssec1.ds9a.nl.: status=got results, this level of recursion done Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Resolved 'powerdns.com.' NS powerdnssec1.ds9a.nl. to: 82.94.213.34 Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Trying IP 82.94.213.34:53, asking 'recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.|TXT' Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: Got 1 answers from powerdnssec1.ds9a.nl. (82.94.213.34), rcode=0 (No Error), aa=1, in 266ms Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: accept answer 'recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.|TXT|"1 OK"' from 'powerdns.com.' nameservers? YES! Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: determining status after receiving this packet Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: answer is in: resolved to '"1 OK"|TXT' Jan 20 22:12:24 rdns4m01 pdns_recursor[10816]: recursor-3.6.2-1.el6.fedora.security-status.secpoll.powerdns.com.: status=got results, this level of recursion done Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: 7 [1] question for '2.centos.pool.ntp.org.|A' from 200.85.32.67 Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Looking for CNAME cache hit of '2.centos.pool.ntp.org.|CNAME' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: No CNAME cache hit of '2.centos.pool.ntp.org.|CNAME' found Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: No cache hit for '2.centos.pool.ntp.org.|A', trying to find an appropriate NS record Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Checking if we have NS in cache for '2.centos.pool.ntp.org.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: no valid/useful NS in cache for '2.centos.pool.ntp.org.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Checking if we have NS in cache for 'centos.pool.ntp.org.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: no valid/useful NS in cache for 'centos.pool.ntp.org.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Checking if we have NS in cache for 'pool.ntp.org.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: no valid/useful NS in cache for 'pool.ntp.org.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Checking if we have NS in cache for 'ntp.org.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: no valid/useful NS in cache for 'ntp.org.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Checking if we have NS in cache for 'org.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: no valid/useful NS in cache for 'org.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Checking if we have NS in cache for '.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: NS (with ip, or non-glue) in cache for '.' -> 'a.root-servers.net.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: within bailiwick: 1, in cache, ttl=86387 Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: NS (with ip, or non-glue) in cache for '.' -> 'b.root-servers.net.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: within bailiwick: 1, in cache, ttl=86387 Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: NS (with ip, or non-glue) in cache for '.' -> 'c.root-servers.net.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: within bailiwick: 1, in cache, ttl=86387 Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: NS (with ip, or non-glue) in cache for '.' -> 'd.root-servers.net.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: within bailiwick: 1, in cache, ttl=86387 Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: NS (with ip, or non-glue) in cache for '.' -> 'e.root-servers.net.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: within bailiwick: 1, in cache, ttl=86387 Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: NS (with ip, or non-glue) in cache for '.' -> 'f.root-servers.net.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: within bailiwick: 1, in cache, ttl=86387 Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: NS (with ip, or non-glue) in cache for '.' -> 'g.root-servers.net.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: within bailiwick: 1, in cache, ttl=86387 Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: NS (with ip, or non-glue) in cache for '.' -> 'h.root-servers.net.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: within bailiwick: 1, in cache, ttl=86387 Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: NS (with ip, or non-glue) in cache for '.' -> 'i.root-servers.net.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: within bailiwick: 1, in cache, ttl=86387 Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: NS (with ip, or non-glue) in cache for '.' -> 'j.root-servers.net.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: within bailiwick: 1, in cache, ttl=86387 Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: NS (with ip, or non-glue) in cache for '.' -> 'k.root-servers.net.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: within bailiwick: 1, in cache, ttl=86387 Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: NS (with ip, or non-glue) in cache for '.' -> 'l.root-servers.net.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: within bailiwick: 1, in cache, ttl=86387 Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: NS (with ip, or non-glue) in cache for '.' -> 'm.root-servers.net.' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: within bailiwick: 1, in cache, ttl=86387 Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: We have NS in cache for '.' (flawedNSSet=0) Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Cache consultations done, have 13 NS to contact Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Nameservers: j.root-servers.net.(0.00ms), e.root-servers.net.(0.00ms), c.root-servers.net.(0.00ms), Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: f.root-servers.net.(0.00ms), m.root-servers.net.(0.00ms), h.root-servers.net.(0.00ms), Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: i.root-servers.net.(0.00ms), d.root-servers.net.(0.00ms), b.root-servers.net.(0.00ms), Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: a.root-servers.net.(0.00ms), g.root-servers.net.(0.00ms), k.root-servers.net.(0.00ms), Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: l.root-servers.net.(170.02ms) Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Trying to resolve NS 'j.root-servers.net.' (1/13) Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] j.root-servers.net.: Looking for CNAME cache hit of 'j.root-servers.net.|CNAME' Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] j.root-servers.net.: No CNAME cache hit of 'j.root-servers.net.|CNAME' found Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] j.root-servers.net.: Found cache hit for A: 192.58.128.30[ttl=86387] Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Resolved '.' NS j.root-servers.net. to: 192.58.128.30 Jan 20 22:12:36 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Trying IP 192.58.128.30:53, asking '2.centos.pool.ntp.org.|A' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Got 18 answers from j.root-servers.net. (192.58.128.30), rcode=0 (No Error), aa=0, in 226ms Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'org.|NS|b0.org.afilias-nst.org.' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'org.|NS|d0.org.afilias-nst.org.' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'org.|NS|a2.org.afilias-nst.info.' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'org.|NS|b2.org.afilias-nst.org.' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'org.|NS|c0.org.afilias-nst.info.' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'org.|NS|a0.org.afilias-nst.info.' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'a0.org.afilias-nst.info.|A|199.19.56.1' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'a0.org.afilias-nst.info.|AAAA|2001:500:e::1' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'a2.org.afilias-nst.info.|A|199.249.112.1' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'a2.org.afilias-nst.info.|AAAA|2001:500:40::1' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'b0.org.afilias-nst.org.|A|199.19.54.1' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'b0.org.afilias-nst.org.|AAAA|2001:500:c::1' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'b2.org.afilias-nst.org.|A|199.249.120.1' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'b2.org.afilias-nst.org.|AAAA|2001:500:48::1' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'c0.org.afilias-nst.info.|A|199.19.53.1' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'c0.org.afilias-nst.info.|AAAA|2001:500:b::1' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'd0.org.afilias-nst.org.|A|199.19.57.1' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'd0.org.afilias-nst.org.|AAAA|2001:500:f::1' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: determining status after receiving this packet Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: got NS record 'org.' -> 'b0.org.afilias-nst.org.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: got NS record 'org.' -> 'd0.org.afilias-nst.org.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: got NS record 'org.' -> 'a2.org.afilias-nst.info.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: got NS record 'org.' -> 'b2.org.afilias-nst.org.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: got NS record 'org.' -> 'c0.org.afilias-nst.info.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: got NS record 'org.' -> 'a0.org.afilias-nst.info.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: status=did not resolve, got 6 NS, looping to them Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Nameservers: b2.org.afilias-nst.org.(0.00ms), a2.org.afilias-nst.info.(0.00ms), a0.org.afilias-nst.info.(0.00ms), Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: c0.org.afilias-nst.info.(0.00ms), b0.org.afilias-nst.org.(0.00ms), d0.org.afilias-nst.org.(0.00ms) Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Trying to resolve NS 'b2.org.afilias-nst.org.' (1/6) Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] b2.org.afilias-nst.org.: Looking for CNAME cache hit of 'b2.org.afilias-nst.org.|CNAME' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] b2.org.afilias-nst.org.: No CNAME cache hit of 'b2.org.afilias-nst.org.|CNAME' found Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] b2.org.afilias-nst.org.: Found cache hit for A: 199.249.120.1[ttl=86400] Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Resolved 'org.' NS b2.org.afilias-nst.org. to: 199.249.120.1 Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Trying IP 199.249.120.1:53, asking '2.centos.pool.ntp.org.|A' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Got 6 answers from b2.org.afilias-nst.org. (199.249.120.1), rcode=0 (No Error), aa=0, in 184ms Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'ntp.org.|NS|ns1.ntp.org.' from 'org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'ntp.org.|NS|ns2.ntp.org.' from 'org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'ntp.org.|NS|dns1.udel.edu.' from 'org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'ntp.org.|NS|dns2.udel.edu.' from 'org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'ns1.ntp.org.|A|149.20.68.3' from 'org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'ns2.ntp.org.|A|149.20.68.4' from 'org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: determining status after receiving this packet Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: got NS record 'ntp.org.' -> 'ns1.ntp.org.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: got NS record 'ntp.org.' -> 'ns2.ntp.org.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: got NS record 'ntp.org.' -> 'dns1.udel.edu.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: got NS record 'ntp.org.' -> 'dns2.udel.edu.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: status=did not resolve, got 4 NS, looping to them Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Nameservers: ns1.ntp.org.(0.00ms), dns2.udel.edu.(0.00ms), ns2.ntp.org.(0.00ms), Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: dns1.udel.edu.(0.00ms) Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Trying to resolve NS 'ns1.ntp.org.' (1/4) Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns1.ntp.org.: Looking for CNAME cache hit of 'ns1.ntp.org.|CNAME' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns1.ntp.org.: No CNAME cache hit of 'ns1.ntp.org.|CNAME' found Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns1.ntp.org.: Found cache hit for A: 149.20.68.3[ttl=86400] Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Resolved 'ntp.org.' NS ns1.ntp.org. to: 149.20.68.3 Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Trying IP 149.20.68.3:53, asking '2.centos.pool.ntp.org.|A' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Got 9 answers from ns1.ntp.org. (149.20.68.3), rcode=0 (No Error), aa=0, in 226ms Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'pool.ntp.org.|NS|b.ntpns.org.' from 'ntp.org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'pool.ntp.org.|NS|h.ntpns.org.' from 'ntp.org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'pool.ntp.org.|NS|g.ntpns.org.' from 'ntp.org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'pool.ntp.org.|NS|i.ntpns.org.' from 'ntp.org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'pool.ntp.org.|NS|a.ntpns.org.' from 'ntp.org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'pool.ntp.org.|NS|f.ntpns.org.' from 'ntp.org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'pool.ntp.org.|NS|e.ntpns.org.' from 'ntp.org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'pool.ntp.org.|NS|c.ntpns.org.' from 'ntp.org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer 'pool.ntp.org.|NS|d.ntpns.org.' from 'ntp.org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: determining status after receiving this packet Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: got NS record 'pool.ntp.org.' -> 'b.ntpns.org.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: got NS record 'pool.ntp.org.' -> 'h.ntpns.org.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: got NS record 'pool.ntp.org.' -> 'g.ntpns.org.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: got NS record 'pool.ntp.org.' -> 'i.ntpns.org.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: got NS record 'pool.ntp.org.' -> 'a.ntpns.org.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: got NS record 'pool.ntp.org.' -> 'f.ntpns.org.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: got NS record 'pool.ntp.org.' -> 'e.ntpns.org.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: got NS record 'pool.ntp.org.' -> 'c.ntpns.org.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: got NS record 'pool.ntp.org.' -> 'd.ntpns.org.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: status=did not resolve, got 9 NS, looping to them Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Nameservers: a.ntpns.org.(0.00ms), d.ntpns.org.(0.00ms), e.ntpns.org.(0.00ms), Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: f.ntpns.org.(0.00ms), b.ntpns.org.(0.00ms), h.ntpns.org.(0.00ms), Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: i.ntpns.org.(0.00ms), c.ntpns.org.(0.00ms), g.ntpns.org.(0.00ms) Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Trying to resolve NS 'a.ntpns.org.' (1/9) Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: Looking for CNAME cache hit of 'a.ntpns.org.|CNAME' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: No CNAME cache hit of 'a.ntpns.org.|CNAME' found Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: No cache hit for 'a.ntpns.org.|A', trying to find an appropriate NS record Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: Checking if we have NS in cache for 'a.ntpns.org.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: no valid/useful NS in cache for 'a.ntpns.org.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: Checking if we have NS in cache for 'ntpns.org.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: no valid/useful NS in cache for 'ntpns.org.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: Checking if we have NS in cache for 'org.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: NS (with ip, or non-glue) in cache for 'org.' -> 'a0.org.afilias-nst.info.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: within bailiwick: 0, not in cache / did not look at cache Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: NS (with ip, or non-glue) in cache for 'org.' -> 'a2.org.afilias-nst.info.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: within bailiwick: 0, not in cache / did not look at cache Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: NS (with ip, or non-glue) in cache for 'org.' -> 'b0.org.afilias-nst.org.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: NS (with ip, or non-glue) in cache for 'org.' -> 'b2.org.afilias-nst.org.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: NS (with ip, or non-glue) in cache for 'org.' -> 'c0.org.afilias-nst.info.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: within bailiwick: 0, not in cache / did not look at cache Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: NS (with ip, or non-glue) in cache for 'org.' -> 'd0.org.afilias-nst.org.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: within bailiwick: 1, in cache, ttl=86400 Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: We have NS in cache for 'org.' (flawedNSSet=0) Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: Cache consultations done, have 6 NS to contact Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: Nameservers: b0.org.afilias-nst.org.(0.00ms), d0.org.afilias-nst.org.(0.00ms), a0.org.afilias-nst.info.(0.00ms), Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: a2.org.afilias-nst.info.(0.00ms), c0.org.afilias-nst.info.(0.00ms), b2.org.afilias-nst.org.(183.84ms) Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: Trying to resolve NS 'b0.org.afilias-nst.org.' (1/6) Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] b0.org.afilias-nst.org.: Looking for CNAME cache hit of 'b0.org.afilias-nst.org.|CNAME' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] b0.org.afilias-nst.org.: No CNAME cache hit of 'b0.org.afilias-nst.org.|CNAME' found Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] b0.org.afilias-nst.org.: Found cache hit for A: 199.19.54.1[ttl=86400] Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: Resolved 'org.' NS b0.org.afilias-nst.org. to: 199.19.54.1 Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: Trying IP 199.19.54.1:53, asking 'a.ntpns.org.|A' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: Got 8 answers from b0.org.afilias-nst.org. (199.19.54.1), rcode=0 (No Error), aa=0, in 233ms Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ntpns.org.|NS|ns1.eu.bitnames.com.' from 'org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ntpns.org.|NS|ns-g2.bitnames.com.' from 'org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ntpns.org.|NS|ns3.p20.dynect.net.' from 'org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ntpns.org.|NS|ns-g1.bitnames.com.' from 'org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ntpns.org.|NS|ns2.us.bitnames.com.' from 'org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ntpns.org.|NS|ns2.p20.dynect.net.' from 'org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ntpns.org.|NS|ns4.p20.dynect.net.' from 'org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ntpns.org.|NS|ns1.us.bitnames.com.' from 'org.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: determining status after receiving this packet Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: got NS record 'ntpns.org.' -> 'ns1.eu.bitnames.com.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: got NS record 'ntpns.org.' -> 'ns-g2.bitnames.com.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: got NS record 'ntpns.org.' -> 'ns3.p20.dynect.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: got NS record 'ntpns.org.' -> 'ns-g1.bitnames.com.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: got NS record 'ntpns.org.' -> 'ns2.us.bitnames.com.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: got NS record 'ntpns.org.' -> 'ns2.p20.dynect.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: got NS record 'ntpns.org.' -> 'ns4.p20.dynect.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: got NS record 'ntpns.org.' -> 'ns1.us.bitnames.com.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: status=did not resolve, got 8 NS, looping to them Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: Nameservers: ns-g2.bitnames.com.(0.00ms), ns2.p20.dynect.net.(0.00ms), ns1.us.bitnames.com.(0.00ms), Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: ns3.p20.dynect.net.(0.00ms), ns-g1.bitnames.com.(0.00ms), ns2.us.bitnames.com.(0.00ms), Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: ns4.p20.dynect.net.(0.00ms), ns1.eu.bitnames.com.(0.00ms) Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: Trying to resolve NS 'ns-g2.bitnames.com.' (1/8) Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: Looking for CNAME cache hit of 'ns-g2.bitnames.com.|CNAME' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: No CNAME cache hit of 'ns-g2.bitnames.com.|CNAME' found Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: No cache hit for 'ns-g2.bitnames.com.|A', trying to find an appropriate NS record Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: Checking if we have NS in cache for 'ns-g2.bitnames.com.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: no valid/useful NS in cache for 'ns-g2.bitnames.com.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: Checking if we have NS in cache for 'bitnames.com.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: no valid/useful NS in cache for 'bitnames.com.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: Checking if we have NS in cache for 'com.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: no valid/useful NS in cache for 'com.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: Checking if we have NS in cache for '.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: NS (with ip, or non-glue) in cache for '.' -> 'a.root-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: within bailiwick: 1, in cache, ttl=86386 Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: NS (with ip, or non-glue) in cache for '.' -> 'b.root-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: within bailiwick: 1, in cache, ttl=86386 Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: NS (with ip, or non-glue) in cache for '.' -> 'c.root-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: within bailiwick: 1, in cache, ttl=86386 Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: NS (with ip, or non-glue) in cache for '.' -> 'd.root-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: within bailiwick: 1, in cache, ttl=86386 Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: NS (with ip, or non-glue) in cache for '.' -> 'e.root-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: within bailiwick: 1, in cache, ttl=86386 Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: NS (with ip, or non-glue) in cache for '.' -> 'f.root-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: within bailiwick: 1, in cache, ttl=86386 Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: NS (with ip, or non-glue) in cache for '.' -> 'g.root-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: within bailiwick: 1, in cache, ttl=86386 Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: NS (with ip, or non-glue) in cache for '.' -> 'h.root-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: within bailiwick: 1, in cache, ttl=86386 Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: NS (with ip, or non-glue) in cache for '.' -> 'i.root-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: within bailiwick: 1, in cache, ttl=86386 Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: NS (with ip, or non-glue) in cache for '.' -> 'j.root-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: within bailiwick: 1, in cache, ttl=86386 Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: NS (with ip, or non-glue) in cache for '.' -> 'k.root-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: within bailiwick: 1, in cache, ttl=86386 Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: NS (with ip, or non-glue) in cache for '.' -> 'l.root-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: within bailiwick: 1, in cache, ttl=86386 Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: NS (with ip, or non-glue) in cache for '.' -> 'm.root-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: within bailiwick: 1, in cache, ttl=86386 Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: We have NS in cache for '.' (flawedNSSet=0) Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: Cache consultations done, have 13 NS to contact Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: Nameservers: i.root-servers.net.(0.00ms), b.root-servers.net.(0.00ms), k.root-servers.net.(0.00ms), Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: d.root-servers.net.(0.00ms), f.root-servers.net.(0.00ms), c.root-servers.net.(0.00ms), Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: g.root-servers.net.(0.00ms), h.root-servers.net.(0.00ms), m.root-servers.net.(0.00ms), Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: a.root-servers.net.(0.00ms), e.root-servers.net.(0.00ms), l.root-servers.net.(167.57ms), Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: j.root-servers.net.(223.78ms) Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: Trying to resolve NS 'i.root-servers.net.' (1/13) Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] i.root-servers.net.: Looking for CNAME cache hit of 'i.root-servers.net.|CNAME' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] i.root-servers.net.: No CNAME cache hit of 'i.root-servers.net.|CNAME' found Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] i.root-servers.net.: Found cache hit for A: 192.36.148.17[ttl=86386] Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: Resolved '.' NS i.root-servers.net. to: 192.36.148.17 Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: Trying IP 192.36.148.17:53, asking 'ns-g2.bitnames.com.|A' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: Got 27 answers from i.root-servers.net. (192.36.148.17), rcode=0 (No Error), aa=0, in 267ms Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'com.|NS|b.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'com.|NS|i.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'com.|NS|h.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'com.|NS|d.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'com.|NS|g.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'com.|NS|c.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'com.|NS|k.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'com.|NS|l.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'com.|NS|f.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'com.|NS|m.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'com.|NS|j.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'com.|NS|e.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'com.|NS|a.gtld-servers.net.' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'a.gtld-servers.net.|A|192.5.6.30' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'a.gtld-servers.net.|AAAA|2001:503:a83e::2:30' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'b.gtld-servers.net.|A|192.33.14.30' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'b.gtld-servers.net.|AAAA|2001:503:231d::2:30' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'c.gtld-servers.net.|A|192.26.92.30' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'd.gtld-servers.net.|A|192.31.80.30' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'e.gtld-servers.net.|A|192.12.94.30' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'f.gtld-servers.net.|A|192.35.51.30' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'g.gtld-servers.net.|A|192.42.93.30' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'h.gtld-servers.net.|A|192.54.112.30' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'i.gtld-servers.net.|A|192.43.172.30' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'j.gtld-servers.net.|A|192.48.79.30' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'k.gtld-servers.net.|A|192.52.178.30' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'l.gtld-servers.net.|A|192.41.162.30' from '.' nameservers? YES! Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: determining status after receiving this packet Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got NS record 'com.' -> 'b.gtld-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got NS record 'com.' -> 'i.gtld-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got NS record 'com.' -> 'h.gtld-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got NS record 'com.' -> 'd.gtld-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got NS record 'com.' -> 'g.gtld-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got NS record 'com.' -> 'c.gtld-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got NS record 'com.' -> 'k.gtld-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got NS record 'com.' -> 'l.gtld-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got NS record 'com.' -> 'f.gtld-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got NS record 'com.' -> 'm.gtld-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got NS record 'com.' -> 'j.gtld-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got NS record 'com.' -> 'e.gtld-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got NS record 'com.' -> 'a.gtld-servers.net.' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: status=did not resolve, got 13 NS, looping to them Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: Nameservers: b.gtld-servers.net.(0.00ms), i.gtld-servers.net.(0.00ms), f.gtld-servers.net.(0.00ms), Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: e.gtld-servers.net.(0.00ms), a.gtld-servers.net.(0.00ms), k.gtld-servers.net.(0.00ms), Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: m.gtld-servers.net.(0.00ms), h.gtld-servers.net.(0.00ms), j.gtld-servers.net.(0.00ms), Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: c.gtld-servers.net.(0.00ms), l.gtld-servers.net.(0.00ms), d.gtld-servers.net.(0.00ms), Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: g.gtld-servers.net.(0.00ms) Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: Trying to resolve NS 'b.gtld-servers.net.' (1/13) Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] b.gtld-servers.net.: Looking for CNAME cache hit of 'b.gtld-servers.net.|CNAME' Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] b.gtld-servers.net.: No CNAME cache hit of 'b.gtld-servers.net.|CNAME' found Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] b.gtld-servers.net.: Found cache hit for A: 192.33.14.30[ttl=86400] Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: Resolved 'com.' NS b.gtld-servers.net. to: 192.33.14.30 Jan 20 22:12:37 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: Trying IP 192.33.14.30:53, asking 'ns-g2.bitnames.com.|A' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: Got 21 answers from b.gtld-servers.net. (192.33.14.30), rcode=0 (No Error), aa=0, in 223ms Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'bitnames.com.|NS|ns1.eu.bitnames.com.' from 'com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'bitnames.com.|NS|ns1.us.bitnames.com.' from 'com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'bitnames.com.|NS|ns2.us.bitnames.com.' from 'com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'bitnames.com.|NS|ns3.us.bitnames.com.' from 'com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'bitnames.com.|NS|ns2.eu.bitnames.com.' from 'com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'bitnames.com.|NS|ns-g2.bitnames.com.' from 'com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'bitnames.com.|NS|ns-g1.bitnames.com.' from 'com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'bitnames.com.|NS|ns-g3.bitnames.com.' from 'com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns1.eu.bitnames.com.|AAAA|2a01:608:ffff:a011::200' from 'com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns1.eu.bitnames.com.|A|94.242.223.200' from 'com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns1.us.bitnames.com.|A|207.171.3.21' from 'com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns1.us.bitnames.com.|AAAA|2607:f238:2::53:21' from 'com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns2.us.bitnames.com.|A|107.170.182.174' from 'com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns3.us.bitnames.com.|A|70.85.157.110' from 'com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns2.eu.bitnames.com.|AAAA|2001:4b98:dc0:41:216:3eff:fe3f:42c5' from 'com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns2.eu.bitnames.com.|A|92.243.1.21' from 'com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns-g2.bitnames.com.|A|192.5.4.1' from 'com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns-g2.bitnames.com.|AAAA|2001:500:2e::1' from 'com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns-g1.bitnames.com.|AAAA|2001:500:90:1::20' from 'com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns-g1.bitnames.com.|A|208.78.70.20' from 'com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns-g3.bitnames.com.|A|204.13.250.20' from 'com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: determining status after receiving this packet Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got NS record 'bitnames.com.' -> 'ns1.eu.bitnames.com.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got NS record 'bitnames.com.' -> 'ns1.us.bitnames.com.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got NS record 'bitnames.com.' -> 'ns2.us.bitnames.com.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got NS record 'bitnames.com.' -> 'ns3.us.bitnames.com.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got NS record 'bitnames.com.' -> 'ns2.eu.bitnames.com.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got NS record 'bitnames.com.' -> 'ns-g2.bitnames.com.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got NS record 'bitnames.com.' -> 'ns-g1.bitnames.com.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got NS record 'bitnames.com.' -> 'ns-g3.bitnames.com.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: status=did not resolve, got 8 NS, looping to them Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: Nameservers: ns3.us.bitnames.com.(0.00ms), ns-g2.bitnames.com.(0.00ms), ns1.eu.bitnames.com.(0.00ms), Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: ns1.us.bitnames.com.(0.00ms), ns2.us.bitnames.com.(0.00ms), ns-g1.bitnames.com.(0.00ms), Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: ns-g3.bitnames.com.(0.00ms), ns2.eu.bitnames.com.(0.00ms) Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: Trying to resolve NS 'ns3.us.bitnames.com.' (1/8) Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns3.us.bitnames.com.: Looking for CNAME cache hit of 'ns3.us.bitnames.com.|CNAME' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns3.us.bitnames.com.: No CNAME cache hit of 'ns3.us.bitnames.com.|CNAME' found Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns3.us.bitnames.com.: Found cache hit for A: 70.85.157.110[ttl=86400] Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: Resolved 'bitnames.com.' NS ns3.us.bitnames.com. to: 70.85.157.110 Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: Trying IP 70.85.157.110:53, asking 'ns-g2.bitnames.com.|A' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: Got 21 answers from ns3.us.bitnames.com. (70.85.157.110), rcode=0 (No Error), aa=1, in 201ms Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns-g2.bitnames.com.|A|192.5.4.1' from 'bitnames.com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'bitnames.com.|NS|ns1.eu.bitnames.com.' from 'bitnames.com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'bitnames.com.|NS|ns1.us.bitnames.com.' from 'bitnames.com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'bitnames.com.|NS|ns2.eu.bitnames.com.' from 'bitnames.com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'bitnames.com.|NS|ns2.us.bitnames.com.' from 'bitnames.com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'bitnames.com.|NS|ns3.us.bitnames.com.' from 'bitnames.com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'bitnames.com.|NS|ns-g1.bitnames.com.' from 'bitnames.com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'bitnames.com.|NS|ns-g2.bitnames.com.' from 'bitnames.com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'bitnames.com.|NS|ns-g3.bitnames.com.' from 'bitnames.com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns1.eu.bitnames.com.|A|94.242.223.200' from 'bitnames.com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns1.us.bitnames.com.|A|207.171.3.21' from 'bitnames.com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns2.eu.bitnames.com.|A|92.243.1.21' from 'bitnames.com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns2.us.bitnames.com.|A|107.170.182.174' from 'bitnames.com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns3.us.bitnames.com.|A|70.85.157.110' from 'bitnames.com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns-g1.bitnames.com.|A|208.78.70.20' from 'bitnames.com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns-g3.bitnames.com.|A|204.13.250.20' from 'bitnames.com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns1.eu.bitnames.com.|AAAA|2a01:608:ffff:a011::200' from 'bitnames.com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns1.us.bitnames.com.|AAAA|2607:f238:2::53:21' from 'bitnames.com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns2.eu.bitnames.com.|AAAA|2001:4b98:dc0:41:216:3eff:fe3f:42c5' from 'bitnames.com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns-g1.bitnames.com.|AAAA|2001:500:90:1::20' from 'bitnames.com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: accept answer 'ns-g2.bitnames.com.|AAAA|2001:500:2e::1' from 'bitnames.com.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: determining status after receiving this packet Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: answer is in: resolved to '192.5.4.1|A' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got upwards/level NS record 'bitnames.com.' -> 'ns1.eu.bitnames.com.', had 'bitnames.com.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got upwards/level NS record 'bitnames.com.' -> 'ns1.us.bitnames.com.', had 'bitnames.com.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got upwards/level NS record 'bitnames.com.' -> 'ns2.eu.bitnames.com.', had 'bitnames.com.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got upwards/level NS record 'bitnames.com.' -> 'ns2.us.bitnames.com.', had 'bitnames.com.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got upwards/level NS record 'bitnames.com.' -> 'ns3.us.bitnames.com.', had 'bitnames.com.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got upwards/level NS record 'bitnames.com.' -> 'ns-g1.bitnames.com.', had 'bitnames.com.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got upwards/level NS record 'bitnames.com.' -> 'ns-g2.bitnames.com.', had 'bitnames.com.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: got upwards/level NS record 'bitnames.com.' -> 'ns-g3.bitnames.com.', had 'bitnames.com.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g2.bitnames.com.: status=got results, this level of recursion done Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: Resolved 'ntpns.org.' NS ns-g2.bitnames.com. to: 192.5.4.1 Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: Trying IP 192.5.4.1:53, asking 'a.ntpns.org.|A' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: Got 20 answers from ns-g2.bitnames.com. (192.5.4.1), rcode=0 (No Error), aa=1, in 224ms Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'a.ntpns.org.|A|207.171.17.42' from 'ntpns.org.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ntpns.org.|NS|ns-g2.bitnames.com.' from 'ntpns.org.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ntpns.org.|NS|ns4.p20.dynect.net.' from 'ntpns.org.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ntpns.org.|NS|ns-g1.bitnames.com.' from 'ntpns.org.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ntpns.org.|NS|ns3.us.bitnames.com.' from 'ntpns.org.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ntpns.org.|NS|ns1.eu.bitnames.com.' from 'ntpns.org.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ntpns.org.|NS|ns2.us.bitnames.com.' from 'ntpns.org.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ntpns.org.|NS|ns3.p20.dynect.net.' from 'ntpns.org.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ntpns.org.|NS|ns2.p20.dynect.net.' from 'ntpns.org.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ntpns.org.|NS|ns1.us.bitnames.com.' from 'ntpns.org.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ns1.eu.bitnames.com.|A|94.242.223.200' from 'ntpns.org.' nameservers? NO! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ns1.eu.bitnames.com.|AAAA|2a01:608:ffff:a011::200' from 'ntpns.org.' nameservers? NO! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ns1.us.bitnames.com.|A|207.171.3.21' from 'ntpns.org.' nameservers? NO! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ns1.us.bitnames.com.|AAAA|2607:f238:2::53:21' from 'ntpns.org.' nameservers? NO! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ns2.us.bitnames.com.|A|107.170.182.174' from 'ntpns.org.' nameservers? NO! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ns3.us.bitnames.com.|A|70.85.157.110' from 'ntpns.org.' nameservers? NO! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ns-g1.bitnames.com.|A|208.78.70.20' from 'ntpns.org.' nameservers? NO! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ns-g1.bitnames.com.|AAAA|2001:500:90:1::20' from 'ntpns.org.' nameservers? NO! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ns-g2.bitnames.com.|A|192.5.4.1' from 'ntpns.org.' nameservers? NO! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: accept answer 'ns-g2.bitnames.com.|AAAA|2001:500:2e::1' from 'ntpns.org.' nameservers? NO! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: determining status after receiving this packet Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: answer is in: resolved to '207.171.17.42|A' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: got upwards/level NS record 'ntpns.org.' -> 'ns-g2.bitnames.com.', had 'ntpns.org.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: got upwards/level NS record 'ntpns.org.' -> 'ns4.p20.dynect.net.', had 'ntpns.org.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: got upwards/level NS record 'ntpns.org.' -> 'ns-g1.bitnames.com.', had 'ntpns.org.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: got upwards/level NS record 'ntpns.org.' -> 'ns3.us.bitnames.com.', had 'ntpns.org.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: got upwards/level NS record 'ntpns.org.' -> 'ns1.eu.bitnames.com.', had 'ntpns.org.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: got upwards/level NS record 'ntpns.org.' -> 'ns2.us.bitnames.com.', had 'ntpns.org.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: got upwards/level NS record 'ntpns.org.' -> 'ns3.p20.dynect.net.', had 'ntpns.org.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: got upwards/level NS record 'ntpns.org.' -> 'ns2.p20.dynect.net.', had 'ntpns.org.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: got upwards/level NS record 'ntpns.org.' -> 'ns1.us.bitnames.com.', had 'ntpns.org.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] a.ntpns.org.: status=got results, this level of recursion done Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Resolved 'pool.ntp.org.' NS a.ntpns.org. to: 207.171.17.42 Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Trying IP 207.171.17.42:53, asking '2.centos.pool.ntp.org.|A' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: a.ntpns.org. returned a ServFail, trying sibling IP or NS Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Trying to resolve NS 'd.ntpns.org.' (2/9) Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: Looking for CNAME cache hit of 'd.ntpns.org.|CNAME' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: No CNAME cache hit of 'd.ntpns.org.|CNAME' found Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: No cache hit for 'd.ntpns.org.|A', trying to find an appropriate NS record Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: Checking if we have NS in cache for 'd.ntpns.org.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: no valid/useful NS in cache for 'd.ntpns.org.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: Checking if we have NS in cache for 'ntpns.org.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: NS (with ip, or non-glue) in cache for 'ntpns.org.' -> 'ns-g1.bitnames.com.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: within bailiwick: 0, not in cache / did not look at cache Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: NS (with ip, or non-glue) in cache for 'ntpns.org.' -> 'ns-g2.bitnames.com.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: within bailiwick: 0, not in cache / did not look at cache Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: NS (with ip, or non-glue) in cache for 'ntpns.org.' -> 'ns1.eu.bitnames.com.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: within bailiwick: 0, not in cache / did not look at cache Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: NS (with ip, or non-glue) in cache for 'ntpns.org.' -> 'ns1.us.bitnames.com.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: within bailiwick: 0, not in cache / did not look at cache Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: NS (with ip, or non-glue) in cache for 'ntpns.org.' -> 'ns2.p20.dynect.net.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: within bailiwick: 0, not in cache / did not look at cache Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: NS (with ip, or non-glue) in cache for 'ntpns.org.' -> 'ns2.us.bitnames.com.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: within bailiwick: 0, not in cache / did not look at cache Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: NS (with ip, or non-glue) in cache for 'ntpns.org.' -> 'ns3.p20.dynect.net.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: within bailiwick: 0, not in cache / did not look at cache Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: NS (with ip, or non-glue) in cache for 'ntpns.org.' -> 'ns3.us.bitnames.com.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: within bailiwick: 0, not in cache / did not look at cache Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: NS (with ip, or non-glue) in cache for 'ntpns.org.' -> 'ns4.p20.dynect.net.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: within bailiwick: 0, not in cache / did not look at cache Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: We have NS in cache for 'ntpns.org.' (flawedNSSet=0) Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: Cache consultations done, have 9 NS to contact Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: Nameservers: ns-g1.bitnames.com.(0.00ms), ns2.p20.dynect.net.(0.00ms), ns1.us.bitnames.com.(0.00ms), Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: ns3.p20.dynect.net.(0.00ms), ns1.eu.bitnames.com.(0.00ms), ns4.p20.dynect.net.(0.00ms), Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: ns2.us.bitnames.com.(0.00ms), ns3.us.bitnames.com.(199.76ms), ns-g2.bitnames.com.(223.51ms) Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: Trying to resolve NS 'ns-g1.bitnames.com.' (1/9) Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g1.bitnames.com.: Looking for CNAME cache hit of 'ns-g1.bitnames.com.|CNAME' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g1.bitnames.com.: No CNAME cache hit of 'ns-g1.bitnames.com.|CNAME' found Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] ns-g1.bitnames.com.: Found cache hit for A: 208.78.70.20[ttl=86400] Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: Resolved 'ntpns.org.' NS ns-g1.bitnames.com. to: 208.78.70.20 Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: Trying IP 208.78.70.20:53, asking 'd.ntpns.org.|A' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: Got 11 answers from ns-g1.bitnames.com. (208.78.70.20), rcode=0 (No Error), aa=1, in 51ms Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: accept answer 'd.ntpns.org.|A|198.105.223.32' from 'ntpns.org.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: accept answer 'd.ntpns.org.|A|199.188.48.59' from 'ntpns.org.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: accept answer 'ntpns.org.|NS|ns3.p20.dynect.net.' from 'ntpns.org.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: accept answer 'ntpns.org.|NS|ns-g2.bitnames.com.' from 'ntpns.org.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: accept answer 'ntpns.org.|NS|ns1.us.bitnames.com.' from 'ntpns.org.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: accept answer 'ntpns.org.|NS|ns2.us.bitnames.com.' from 'ntpns.org.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: accept answer 'ntpns.org.|NS|ns3.us.bitnames.com.' from 'ntpns.org.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: accept answer 'ntpns.org.|NS|ns4.p20.dynect.net.' from 'ntpns.org.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: accept answer 'ntpns.org.|NS|ns-g1.bitnames.com.' from 'ntpns.org.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: accept answer 'ntpns.org.|NS|ns1.eu.bitnames.com.' from 'ntpns.org.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: accept answer 'ntpns.org.|NS|ns2.p20.dynect.net.' from 'ntpns.org.' nameservers? YES! Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: determining status after receiving this packet Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: answer is in: resolved to '198.105.223.32|A' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: answer is in: resolved to '199.188.48.59|A' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: got upwards/level NS record 'ntpns.org.' -> 'ns3.p20.dynect.net.', had 'ntpns.org.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: got upwards/level NS record 'ntpns.org.' -> 'ns-g2.bitnames.com.', had 'ntpns.org.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: got upwards/level NS record 'ntpns.org.' -> 'ns1.us.bitnames.com.', had 'ntpns.org.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: got upwards/level NS record 'ntpns.org.' -> 'ns2.us.bitnames.com.', had 'ntpns.org.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: got upwards/level NS record 'ntpns.org.' -> 'ns3.us.bitnames.com.', had 'ntpns.org.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: got upwards/level NS record 'ntpns.org.' -> 'ns4.p20.dynect.net.', had 'ntpns.org.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: got upwards/level NS record 'ntpns.org.' -> 'ns-g1.bitnames.com.', had 'ntpns.org.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: got upwards/level NS record 'ntpns.org.' -> 'ns1.eu.bitnames.com.', had 'ntpns.org.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: got upwards/level NS record 'ntpns.org.' -> 'ns2.p20.dynect.net.', had 'ntpns.org.' Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] d.ntpns.org.: status=got results, this level of recursion done Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Resolved 'pool.ntp.org.' NS d.ntpns.org. to: 198.105.223.32, 199.188.48.59 Jan 20 22:12:38 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Trying IP 198.105.223.32:53, asking '2.centos.pool.ntp.org.|A' Jan 20 22:12:39 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: Got 4 answers from d.ntpns.org. (198.105.223.32), rcode=0 (No Error), aa=1, in 199ms Jan 20 22:12:39 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer '2.centos.pool.ntp.org.|A|200.192.112.8' from 'pool.ntp.org.' nameservers? YES! Jan 20 22:12:39 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer '2.centos.pool.ntp.org.|A|200.89.75.198' from 'pool.ntp.org.' nameservers? YES! Jan 20 22:12:39 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer '2.centos.pool.ntp.org.|A|200.144.121.33' from 'pool.ntp.org.' nameservers? YES! Jan 20 22:12:39 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: accept answer '2.centos.pool.ntp.org.|A|190.245.82.207' from 'pool.ntp.org.' nameservers? YES! Jan 20 22:12:39 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: determining status after receiving this packet Jan 20 22:12:39 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: answer is in: resolved to '200.192.112.8|A' Jan 20 22:12:39 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: answer is in: resolved to '200.89.75.198|A' Jan 20 22:12:39 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: answer is in: resolved to '200.144.121.33|A' Jan 20 22:12:39 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: answer is in: resolved to '190.245.82.207|A' Jan 20 22:12:39 rdns4m01 pdns_recursor[10816]: [1] 2.centos.pool.ntp.org.: status=got results, this level of recursion done Jan 20 22:12:39 rdns4m01 pdns_recursor[10816]: 7 [1] answer to question '2.centos.pool.ntp.org.|A': 4 answers, 0 additional, took 11 packets, 0 throttled, 0 timeouts, 0 tcp connections, rcode=0