[Pdns-users] Problems with pdns-recursor
Andy Rabagliati
andyr at wizzy.com
Wed Jan 31 12:09:24 UTC 2007
On Wed, 31 Jan 2007, bert hubert wrote:
> If that doesn't help, please run the recursor on the foreground, like this:
>
> pdns_recursor --daemon=no --trace
>
> And show us the output while querying for the domain that has the problem.
> Please include all logging from the start, and all 'dig' output.
I verified I have no old copies of pdns_recursor lying around.
Dig output follows - trace attached. Thanks again for your help.
The machine musselcracker is our firewall. My desktop (quail) routes through it.
From my desktop (also ubuntu dapper), I see this :-
andyr at quail:~$ dig visolve.com @76.212.18.42
; <<>> DiG 9.3.2 <<>> visolve.com @76.212.18.42
; (1 server found)
;; global options: printcmd
;; connection timed out; no servers could be reached
andyr at quail:~$ dig visolve.com @76.212.18.41
...
;; QUESTION SECTION:
;visolve.com. IN A
;; ANSWER SECTION:
visolve.com. 600 IN A 76.212.18.41
;; AUTHORITY SECTION:
visolve.com. 600 IN NS ns2.visolve.com.
visolve.com. 600 IN NS visolve.com.
visolve.com. 600 IN NS ns1.visolve.com.
;; ADDITIONAL SECTION:
ns1.visolve.com. 600 IN A 76.212.18.41
ns2.visolve.com. 600 IN A 76.212.18.42
;; Query time: 1572 msec
;; SERVER: 76.212.18.41#53(76.212.18.41)
;; WHEN: Wed Jan 31 13:57:49 2007
;; MSG SIZE rcvd: 127
andyr at quail:~$ telnet 76.212.18.41 53
Trying 76.212.18.41...
telnet: Unable to connect to remote host: Connection refused
[ Does that mean it only answers UDP queries ??]
From the firewall :-
andyr at musselcracker:~$ dig visolve.com @76.212.18.41
; <<>> DiG 9.3.2 <<>> visolve.com @76.212.18.41
; (1 server found)
;; global options: printcmd
;; connection timed out; no servers could be reached
Cheers, Andy!
========= dig output corresponding to trace attached ======
dig visolve.com @127.0.0.2
; <<>> DiG 9.3.2 <<>> visolve.com @127.0.0.2
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 64670
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;visolve.com. IN A
;; Query time: 4904 msec
;; SERVER: 127.0.0.2#53(127.0.0.2)
;; WHEN: Wed Jan 31 13:46:58 2007
;; MSG SIZE rcvd: 29
-------------- next part --------------
Jan 31 13:46:48 PowerDNS recursor 3.1.4 (C) 2001-2006 PowerDNS.COM BV (Nov 12 2006, 17:57:29, gcc 4.0.3 (Ubuntu 4.0.3-1ubuntu5)) starting up
Jan 31 13:46:48 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 31 13:46:48 Operating in 32 bits mode
Jan 31 13:46:48 Only allowing queries from: 127.0.0.0/8, 10.0.0.0/8, 192.168.0.0/16, 172.16.0.0/12, ::1/128, fe80::/10
Jan 31 13:46:48 Inserting rfc 1918 private space zones
Jan 31 13:46:48 Listening for UDP queries on 127.0.0.2:53
Jan 31 13:46:48 Listening for TCP queries on 127.0.0.2:53
Jan 31 13:46:48 Done priming cache with root hints
Jan 31 13:46:48 Enabled 'epoll' multiplexer
Jan 31 13:46:48 .: No cache hit for '.|NS', trying to find an appropriate NS record
Jan 31 13:46:48 .: Checking if we have NS in cache for '.'
Jan 31 13:46:48 .: NS (with ip, or non-glue) in cache for '.' -> 'a.root-servers.net.'
Jan 31 13:46:48 .: within bailiwick: 1, in cache, ttl=3600000
Jan 31 13:46:48 .: NS (with ip, or non-glue) in cache for '.' -> 'b.root-servers.net.'
Jan 31 13:46:48 .: within bailiwick: 1, in cache, ttl=3600000
Jan 31 13:46:48 .: NS (with ip, or non-glue) in cache for '.' -> 'c.root-servers.net.'
Jan 31 13:46:48 .: within bailiwick: 1, in cache, ttl=3600000
Jan 31 13:46:48 .: NS (with ip, or non-glue) in cache for '.' -> 'd.root-servers.net.'
Jan 31 13:46:48 .: within bailiwick: 1, in cache, ttl=3600000
Jan 31 13:46:48 .: NS (with ip, or non-glue) in cache for '.' -> 'e.root-servers.net.'
Jan 31 13:46:48 .: within bailiwick: 1, in cache, ttl=3600000
Jan 31 13:46:48 .: NS (with ip, or non-glue) in cache for '.' -> 'f.root-servers.net.'
Jan 31 13:46:48 .: within bailiwick: 1, in cache, ttl=3600000
Jan 31 13:46:48 .: NS (with ip, or non-glue) in cache for '.' -> 'g.root-servers.net.'
Jan 31 13:46:48 .: within bailiwick: 1, in cache, ttl=3600000
Jan 31 13:46:48 .: NS (with ip, or non-glue) in cache for '.' -> 'h.root-servers.net.'
Jan 31 13:46:48 .: within bailiwick: 1, in cache, ttl=3600000
Jan 31 13:46:48 .: NS (with ip, or non-glue) in cache for '.' -> 'i.root-servers.net.'
Jan 31 13:46:48 .: within bailiwick: 1, in cache, ttl=3600000
Jan 31 13:46:48 .: NS (with ip, or non-glue) in cache for '.' -> 'j.root-servers.net.'
Jan 31 13:46:48 .: within bailiwick: 1, in cache, ttl=3600000
Jan 31 13:46:48 .: NS (with ip, or non-glue) in cache for '.' -> 'k.root-servers.net.'
Jan 31 13:46:48 .: within bailiwick: 1, in cache, ttl=3600000
Jan 31 13:46:48 .: NS (with ip, or non-glue) in cache for '.' -> 'l.root-servers.net.'
Jan 31 13:46:48 .: within bailiwick: 1, in cache, ttl=3600000
Jan 31 13:46:48 .: NS (with ip, or non-glue) in cache for '.' -> 'm.root-servers.net.'
Jan 31 13:46:48 .: within bailiwick: 1, in cache, ttl=3600000
Jan 31 13:46:48 .: We have NS in cache for '.' (flawedNSSet=0)
Jan 31 13:46:48 .: Cache consultations done, have 13 NS to contact
Jan 31 13:46:48 .: Nameservers: g.root-servers.net.(0ms), d.root-servers.net.(0ms), c.root-servers.net.(0ms),
Jan 31 13:46:48 .: b.root-servers.net.(0ms), i.root-servers.net.(0ms), k.root-servers.net.(0ms),
Jan 31 13:46:48 .: a.root-servers.net.(0ms), l.root-servers.net.(0ms), m.root-servers.net.(0ms),
Jan 31 13:46:48 .: f.root-servers.net.(0ms), j.root-servers.net.(0ms), h.root-servers.net.(0ms),
Jan 31 13:46:48 .: e.root-servers.net.(0ms)
Jan 31 13:46:48 .: Trying to resolve NS 'g.root-servers.net.' (1/13)
Jan 31 13:46:48 g.root-servers.net.: Looking for CNAME cache hit of 'g.root-servers.net.|CNAME'
Jan 31 13:46:48 g.root-servers.net.: No CNAME cache hit of 'g.root-servers.net.|CNAME' found
Jan 31 13:46:48 g.root-servers.net.: Found cache hit for A: 192.112.36.4[ttl=3600000]
Jan 31 13:46:48 .: Resolved '.' NS g.root-servers.net. to: 192.112.36.4
Jan 31 13:46:48 .: Trying IP 192.112.36.4, asking '.|NS'
Jan 31 13:46:49 .: Got 26 answers from g.root-servers.net. (192.112.36.4), rcode=0, in 1194ms
Jan 31 13:46:49 .: accept answer '.|NS|L.ROOT-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer '.|NS|M.ROOT-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer '.|NS|A.ROOT-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer '.|NS|B.ROOT-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer '.|NS|C.ROOT-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer '.|NS|D.ROOT-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer '.|NS|E.ROOT-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer '.|NS|F.ROOT-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer '.|NS|G.ROOT-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer '.|NS|H.ROOT-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer '.|NS|I.ROOT-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer '.|NS|J.ROOT-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer '.|NS|K.ROOT-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer 'A.ROOT-SERVERS.NET.|A|198.41.0.4' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer 'B.ROOT-SERVERS.NET.|A|192.228.79.201' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer 'C.ROOT-SERVERS.NET.|A|192.33.4.12' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer 'D.ROOT-SERVERS.NET.|A|128.8.10.90' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer 'E.ROOT-SERVERS.NET.|A|192.203.230.10' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer 'F.ROOT-SERVERS.NET.|A|192.5.5.241' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer 'G.ROOT-SERVERS.NET.|A|192.112.36.4' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer 'H.ROOT-SERVERS.NET.|A|128.63.2.53' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer 'I.ROOT-SERVERS.NET.|A|192.36.148.17' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer 'J.ROOT-SERVERS.NET.|A|192.58.128.30' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer 'K.ROOT-SERVERS.NET.|A|193.0.14.129' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer 'L.ROOT-SERVERS.NET.|A|198.32.64.12' from '.' nameservers? YES!
Jan 31 13:46:49 .: accept answer 'M.ROOT-SERVERS.NET.|A|202.12.27.33' from '.' nameservers? YES!
Jan 31 13:46:49 .: determining status after receiving this packet
Jan 31 13:46:49 .: answer is in: resolved to 'L.ROOT-SERVERS.NET.|NS'
Jan 31 13:46:49 .: answer is in: resolved to 'M.ROOT-SERVERS.NET.|NS'
Jan 31 13:46:49 .: answer is in: resolved to 'A.ROOT-SERVERS.NET.|NS'
Jan 31 13:46:49 .: answer is in: resolved to 'B.ROOT-SERVERS.NET.|NS'
Jan 31 13:46:49 .: answer is in: resolved to 'C.ROOT-SERVERS.NET.|NS'
Jan 31 13:46:49 .: answer is in: resolved to 'D.ROOT-SERVERS.NET.|NS'
Jan 31 13:46:49 .: answer is in: resolved to 'E.ROOT-SERVERS.NET.|NS'
Jan 31 13:46:49 .: answer is in: resolved to 'F.ROOT-SERVERS.NET.|NS'
Jan 31 13:46:49 .: answer is in: resolved to 'G.ROOT-SERVERS.NET.|NS'
Jan 31 13:46:49 .: answer is in: resolved to 'H.ROOT-SERVERS.NET.|NS'
Jan 31 13:46:49 .: answer is in: resolved to 'I.ROOT-SERVERS.NET.|NS'
Jan 31 13:46:49 .: answer is in: resolved to 'J.ROOT-SERVERS.NET.|NS'
Jan 31 13:46:49 .: answer is in: resolved to 'K.ROOT-SERVERS.NET.|NS'
Jan 31 13:46:49 .: status=got results, this level of recursion done
Jan 31 13:46:49 .: Starting additional processing
Jan 31 13:46:49 .: record 'L.ROOT-SERVERS.NET.|NS' needs IP for additional processing
Jan 31 13:46:49 L.ROOT-SERVERS.NET.: Looking for CNAME cache hit of 'L.ROOT-SERVERS.NET.|CNAME'
Jan 31 13:46:49 L.ROOT-SERVERS.NET.: No CNAME cache hit of 'L.ROOT-SERVERS.NET.|CNAME' found
Jan 31 13:46:49 L.ROOT-SERVERS.NET.: Found cache hit for A: 198.32.64.12[ttl=3599999]
Jan 31 13:46:49 .: record 'M.ROOT-SERVERS.NET.|NS' needs IP for additional processing
Jan 31 13:46:49 M.ROOT-SERVERS.NET.: Looking for CNAME cache hit of 'M.ROOT-SERVERS.NET.|CNAME'
Jan 31 13:46:49 M.ROOT-SERVERS.NET.: No CNAME cache hit of 'M.ROOT-SERVERS.NET.|CNAME' found
Jan 31 13:46:49 M.ROOT-SERVERS.NET.: Found cache hit for A: 202.12.27.33[ttl=3599999]
Jan 31 13:46:49 .: record 'A.ROOT-SERVERS.NET.|NS' needs IP for additional processing
Jan 31 13:46:49 A.ROOT-SERVERS.NET.: Looking for CNAME cache hit of 'A.ROOT-SERVERS.NET.|CNAME'
Jan 31 13:46:49 A.ROOT-SERVERS.NET.: No CNAME cache hit of 'A.ROOT-SERVERS.NET.|CNAME' found
Jan 31 13:46:49 A.ROOT-SERVERS.NET.: Found cache hit for A: 198.41.0.4[ttl=3599999]
Jan 31 13:46:49 .: record 'B.ROOT-SERVERS.NET.|NS' needs IP for additional processing
Jan 31 13:46:49 B.ROOT-SERVERS.NET.: Looking for CNAME cache hit of 'B.ROOT-SERVERS.NET.|CNAME'
Jan 31 13:46:49 B.ROOT-SERVERS.NET.: No CNAME cache hit of 'B.ROOT-SERVERS.NET.|CNAME' found
Jan 31 13:46:49 B.ROOT-SERVERS.NET.: Found cache hit for A: 192.228.79.201[ttl=3599999]
Jan 31 13:46:49 .: record 'C.ROOT-SERVERS.NET.|NS' needs IP for additional processing
Jan 31 13:46:49 C.ROOT-SERVERS.NET.: Looking for CNAME cache hit of 'C.ROOT-SERVERS.NET.|CNAME'
Jan 31 13:46:49 C.ROOT-SERVERS.NET.: No CNAME cache hit of 'C.ROOT-SERVERS.NET.|CNAME' found
Jan 31 13:46:49 C.ROOT-SERVERS.NET.: Found cache hit for A: 192.33.4.12[ttl=3599999]
Jan 31 13:46:49 .: record 'D.ROOT-SERVERS.NET.|NS' needs IP for additional processing
Jan 31 13:46:49 D.ROOT-SERVERS.NET.: Looking for CNAME cache hit of 'D.ROOT-SERVERS.NET.|CNAME'
Jan 31 13:46:49 D.ROOT-SERVERS.NET.: No CNAME cache hit of 'D.ROOT-SERVERS.NET.|CNAME' found
Jan 31 13:46:49 D.ROOT-SERVERS.NET.: Found cache hit for A: 128.8.10.90[ttl=3599999]
Jan 31 13:46:49 .: record 'E.ROOT-SERVERS.NET.|NS' needs IP for additional processing
Jan 31 13:46:49 E.ROOT-SERVERS.NET.: Looking for CNAME cache hit of 'E.ROOT-SERVERS.NET.|CNAME'
Jan 31 13:46:49 E.ROOT-SERVERS.NET.: No CNAME cache hit of 'E.ROOT-SERVERS.NET.|CNAME' found
Jan 31 13:46:49 E.ROOT-SERVERS.NET.: Found cache hit for A: 192.203.230.10[ttl=3599999]
Jan 31 13:46:49 .: record 'F.ROOT-SERVERS.NET.|NS' needs IP for additional processing
Jan 31 13:46:49 F.ROOT-SERVERS.NET.: Looking for CNAME cache hit of 'F.ROOT-SERVERS.NET.|CNAME'
Jan 31 13:46:49 F.ROOT-SERVERS.NET.: No CNAME cache hit of 'F.ROOT-SERVERS.NET.|CNAME' found
Jan 31 13:46:49 F.ROOT-SERVERS.NET.: Found cache hit for A: 192.5.5.241[ttl=3599999]
Jan 31 13:46:49 .: record 'G.ROOT-SERVERS.NET.|NS' needs IP for additional processing
Jan 31 13:46:49 G.ROOT-SERVERS.NET.: Looking for CNAME cache hit of 'G.ROOT-SERVERS.NET.|CNAME'
Jan 31 13:46:49 G.ROOT-SERVERS.NET.: No CNAME cache hit of 'G.ROOT-SERVERS.NET.|CNAME' found
Jan 31 13:46:49 G.ROOT-SERVERS.NET.: Found cache hit for A: 192.112.36.4[ttl=3599999]
Jan 31 13:46:49 .: record 'H.ROOT-SERVERS.NET.|NS' needs IP for additional processing
Jan 31 13:46:49 H.ROOT-SERVERS.NET.: Looking for CNAME cache hit of 'H.ROOT-SERVERS.NET.|CNAME'
Jan 31 13:46:49 H.ROOT-SERVERS.NET.: No CNAME cache hit of 'H.ROOT-SERVERS.NET.|CNAME' found
Jan 31 13:46:49 H.ROOT-SERVERS.NET.: Found cache hit for A: 128.63.2.53[ttl=3599999]
Jan 31 13:46:49 .: record 'I.ROOT-SERVERS.NET.|NS' needs IP for additional processing
Jan 31 13:46:49 I.ROOT-SERVERS.NET.: Looking for CNAME cache hit of 'I.ROOT-SERVERS.NET.|CNAME'
Jan 31 13:46:49 I.ROOT-SERVERS.NET.: No CNAME cache hit of 'I.ROOT-SERVERS.NET.|CNAME' found
Jan 31 13:46:49 I.ROOT-SERVERS.NET.: Found cache hit for A: 192.36.148.17[ttl=3599999]
Jan 31 13:46:49 .: record 'J.ROOT-SERVERS.NET.|NS' needs IP for additional processing
Jan 31 13:46:49 J.ROOT-SERVERS.NET.: Looking for CNAME cache hit of 'J.ROOT-SERVERS.NET.|CNAME'
Jan 31 13:46:49 J.ROOT-SERVERS.NET.: No CNAME cache hit of 'J.ROOT-SERVERS.NET.|CNAME' found
Jan 31 13:46:49 J.ROOT-SERVERS.NET.: Found cache hit for A: 192.58.128.30[ttl=3599999]
Jan 31 13:46:49 .: record 'K.ROOT-SERVERS.NET.|NS' needs IP for additional processing
Jan 31 13:46:49 K.ROOT-SERVERS.NET.: Looking for CNAME cache hit of 'K.ROOT-SERVERS.NET.|CNAME'
Jan 31 13:46:49 K.ROOT-SERVERS.NET.: No CNAME cache hit of 'K.ROOT-SERVERS.NET.|CNAME' found
Jan 31 13:46:49 K.ROOT-SERVERS.NET.: Found cache hit for A: 193.0.14.129[ttl=3599999]
Jan 31 13:46:49 .: Done with additional processing
Jan 31 13:46:49 Refreshed . records
Jan 31 13:46:53 [1] question for 'visolve.com.|A' from 127.0.0.2
Jan 31 13:46:53 [1] visolve.com.: Looking for CNAME cache hit of 'visolve.com.|CNAME'
Jan 31 13:46:53 [1] visolve.com.: No CNAME cache hit of 'visolve.com.|CNAME' found
Jan 31 13:46:53 [1] visolve.com.: No cache hit for 'visolve.com.|A', trying to find an appropriate NS record
Jan 31 13:46:53 [1] visolve.com.: Checking if we have NS in cache for 'visolve.com.'
Jan 31 13:46:53 [1] visolve.com.: no valid/useful NS in cache for 'visolve.com.'
Jan 31 13:46:53 [1] visolve.com.: Checking if we have NS in cache for 'com.'
Jan 31 13:46:53 [1] visolve.com.: no valid/useful NS in cache for 'com.'
Jan 31 13:46:53 [1] visolve.com.: Checking if we have NS in cache for '.'
Jan 31 13:46:53 [1] visolve.com.: NS (with ip, or non-glue) in cache for '.' -> 'a.root-servers.net.'
Jan 31 13:46:53 [1] visolve.com.: within bailiwick: 1, in cache, ttl=3599995
Jan 31 13:46:53 [1] visolve.com.: NS (with ip, or non-glue) in cache for '.' -> 'b.root-servers.net.'
Jan 31 13:46:53 [1] visolve.com.: within bailiwick: 1, in cache, ttl=3599995
Jan 31 13:46:53 [1] visolve.com.: NS (with ip, or non-glue) in cache for '.' -> 'c.root-servers.net.'
Jan 31 13:46:53 [1] visolve.com.: within bailiwick: 1, in cache, ttl=3599995
Jan 31 13:46:53 [1] visolve.com.: NS (with ip, or non-glue) in cache for '.' -> 'd.root-servers.net.'
Jan 31 13:46:53 [1] visolve.com.: within bailiwick: 1, in cache, ttl=3599995
Jan 31 13:46:53 [1] visolve.com.: NS (with ip, or non-glue) in cache for '.' -> 'e.root-servers.net.'
Jan 31 13:46:53 [1] visolve.com.: within bailiwick: 1, in cache, ttl=3599995
Jan 31 13:46:53 [1] visolve.com.: NS (with ip, or non-glue) in cache for '.' -> 'f.root-servers.net.'
Jan 31 13:46:53 [1] visolve.com.: within bailiwick: 1, in cache, ttl=3599995
Jan 31 13:46:53 [1] visolve.com.: NS (with ip, or non-glue) in cache for '.' -> 'g.root-servers.net.'
Jan 31 13:46:53 [1] visolve.com.: within bailiwick: 1, in cache, ttl=3599995
Jan 31 13:46:53 [1] visolve.com.: NS (with ip, or non-glue) in cache for '.' -> 'h.root-servers.net.'
Jan 31 13:46:53 [1] visolve.com.: within bailiwick: 1, in cache, ttl=3599995
Jan 31 13:46:53 [1] visolve.com.: NS (with ip, or non-glue) in cache for '.' -> 'i.root-servers.net.'
Jan 31 13:46:53 [1] visolve.com.: within bailiwick: 1, in cache, ttl=3599995
Jan 31 13:46:53 [1] visolve.com.: NS (with ip, or non-glue) in cache for '.' -> 'j.root-servers.net.'
Jan 31 13:46:53 [1] visolve.com.: within bailiwick: 1, in cache, ttl=3599995
Jan 31 13:46:53 [1] visolve.com.: NS (with ip, or non-glue) in cache for '.' -> 'k.root-servers.net.'
Jan 31 13:46:53 [1] visolve.com.: within bailiwick: 1, in cache, ttl=3599995
Jan 31 13:46:53 [1] visolve.com.: NS (with ip, or non-glue) in cache for '.' -> 'l.root-servers.net.'
Jan 31 13:46:53 [1] visolve.com.: within bailiwick: 1, in cache, ttl=3599995
Jan 31 13:46:53 [1] visolve.com.: NS (with ip, or non-glue) in cache for '.' -> 'm.root-servers.net.'
Jan 31 13:46:53 [1] visolve.com.: within bailiwick: 1, in cache, ttl=3599995
Jan 31 13:46:53 [1] visolve.com.: We have NS in cache for '.' (flawedNSSet=0)
Jan 31 13:46:53 [1] visolve.com.: Cache consultations done, have 13 NS to contact
Jan 31 13:46:53 [1] visolve.com.: Nameservers: g.root-servers.net.(0ms), e.root-servers.net.(0ms), h.root-servers.net.(0ms),
Jan 31 13:46:53 [1] visolve.com.: k.root-servers.net.(0ms), m.root-servers.net.(0ms), d.root-servers.net.(0ms),
Jan 31 13:46:53 [1] visolve.com.: b.root-servers.net.(0ms), i.root-servers.net.(0ms), l.root-servers.net.(0ms),
Jan 31 13:46:53 [1] visolve.com.: j.root-servers.net.(0ms), f.root-servers.net.(0ms), c.root-servers.net.(0ms),
Jan 31 13:46:53 [1] visolve.com.: a.root-servers.net.(0ms)
Jan 31 13:46:53 [1] visolve.com.: Trying to resolve NS 'g.root-servers.net.' (1/13)
Jan 31 13:46:53 [1] g.root-servers.net.: Looking for CNAME cache hit of 'g.root-servers.net.|CNAME'
Jan 31 13:46:53 [1] g.root-servers.net.: No CNAME cache hit of 'g.root-servers.net.|CNAME' found
Jan 31 13:46:53 [1] g.root-servers.net.: Found cache hit for A: 192.112.36.4[ttl=3599995]
Jan 31 13:46:53 [1] visolve.com.: Resolved '.' NS g.root-servers.net. to: 192.112.36.4
Jan 31 13:46:53 [1] visolve.com.: Trying IP 192.112.36.4, asking 'visolve.com.|A'
Jan 31 13:46:55 [1] visolve.com.: timeout resolving
Jan 31 13:46:55 [1] visolve.com.: Trying to resolve NS 'e.root-servers.net.' (2/13)
Jan 31 13:46:55 [1] e.root-servers.net.: Looking for CNAME cache hit of 'e.root-servers.net.|CNAME'
Jan 31 13:46:55 [1] e.root-servers.net.: No CNAME cache hit of 'e.root-servers.net.|CNAME' found
Jan 31 13:46:55 [1] e.root-servers.net.: Found cache hit for A: 192.203.230.10[ttl=3599993]
Jan 31 13:46:55 [1] visolve.com.: Resolved '.' NS e.root-servers.net. to: 192.203.230.10
Jan 31 13:46:55 [1] visolve.com.: Trying IP 192.203.230.10, asking 'visolve.com.|A'
Jan 31 13:46:56 [1] visolve.com.: Got 27 answers from e.root-servers.net. (192.203.230.10), rcode=0, in 1530ms
Jan 31 13:46:56 [1] visolve.com.: accept answer 'com.|NS|K.GTLD-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'com.|NS|L.GTLD-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'com.|NS|M.GTLD-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'com.|NS|A.GTLD-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'com.|NS|B.GTLD-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'com.|NS|C.GTLD-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'com.|NS|D.GTLD-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'com.|NS|E.GTLD-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'com.|NS|F.GTLD-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'com.|NS|G.GTLD-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'com.|NS|H.GTLD-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'com.|NS|I.GTLD-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'com.|NS|J.GTLD-SERVERS.NET.' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'A.GTLD-SERVERS.NET.|A|192.5.6.30' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'A.GTLD-SERVERS.NET.|AAAA|2001:503:a83e::2:30' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'B.GTLD-SERVERS.NET.|A|192.33.14.30' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'B.GTLD-SERVERS.NET.|AAAA|2001:503:231d::2:30' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'C.GTLD-SERVERS.NET.|A|192.26.92.30' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'D.GTLD-SERVERS.NET.|A|192.31.80.30' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'E.GTLD-SERVERS.NET.|A|192.12.94.30' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'F.GTLD-SERVERS.NET.|A|192.35.51.30' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'G.GTLD-SERVERS.NET.|A|192.42.93.30' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'H.GTLD-SERVERS.NET.|A|192.54.112.30' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'I.GTLD-SERVERS.NET.|A|192.43.172.30' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'J.GTLD-SERVERS.NET.|A|192.48.79.30' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'K.GTLD-SERVERS.NET.|A|192.52.178.30' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: accept answer 'L.GTLD-SERVERS.NET.|A|192.41.162.30' from '.' nameservers? YES!
Jan 31 13:46:56 [1] visolve.com.: determining status after receiving this packet
Jan 31 13:46:56 [1] visolve.com.: got NS record 'com.' -> 'K.GTLD-SERVERS.NET.'
Jan 31 13:46:56 [1] visolve.com.: got NS record 'com.' -> 'L.GTLD-SERVERS.NET.'
Jan 31 13:46:56 [1] visolve.com.: got NS record 'com.' -> 'M.GTLD-SERVERS.NET.'
Jan 31 13:46:56 [1] visolve.com.: got NS record 'com.' -> 'A.GTLD-SERVERS.NET.'
Jan 31 13:46:56 [1] visolve.com.: got NS record 'com.' -> 'B.GTLD-SERVERS.NET.'
Jan 31 13:46:56 [1] visolve.com.: got NS record 'com.' -> 'C.GTLD-SERVERS.NET.'
Jan 31 13:46:56 [1] visolve.com.: got NS record 'com.' -> 'D.GTLD-SERVERS.NET.'
Jan 31 13:46:56 [1] visolve.com.: got NS record 'com.' -> 'E.GTLD-SERVERS.NET.'
Jan 31 13:46:56 [1] visolve.com.: got NS record 'com.' -> 'F.GTLD-SERVERS.NET.'
Jan 31 13:46:56 [1] visolve.com.: got NS record 'com.' -> 'G.GTLD-SERVERS.NET.'
Jan 31 13:46:56 [1] visolve.com.: got NS record 'com.' -> 'H.GTLD-SERVERS.NET.'
Jan 31 13:46:56 [1] visolve.com.: got NS record 'com.' -> 'I.GTLD-SERVERS.NET.'
Jan 31 13:46:56 [1] visolve.com.: got NS record 'com.' -> 'J.GTLD-SERVERS.NET.'
Jan 31 13:46:56 [1] visolve.com.: status=did not resolve, got 13 NS, looping to them
Jan 31 13:46:56 [1] visolve.com.: Nameservers: B.GTLD-SERVERS.NET.(0ms), E.GTLD-SERVERS.NET.(0ms), K.GTLD-SERVERS.NET.(0ms),
Jan 31 13:46:56 [1] visolve.com.: F.GTLD-SERVERS.NET.(0ms), M.GTLD-SERVERS.NET.(0ms), H.GTLD-SERVERS.NET.(0ms),
Jan 31 13:46:56 [1] visolve.com.: A.GTLD-SERVERS.NET.(0ms), G.GTLD-SERVERS.NET.(0ms), I.GTLD-SERVERS.NET.(0ms),
Jan 31 13:46:56 [1] visolve.com.: C.GTLD-SERVERS.NET.(0ms), L.GTLD-SERVERS.NET.(0ms), D.GTLD-SERVERS.NET.(0ms),
Jan 31 13:46:56 [1] visolve.com.: J.GTLD-SERVERS.NET.(0ms)
Jan 31 13:46:56 [1] visolve.com.: Trying to resolve NS 'B.GTLD-SERVERS.NET.' (1/13)
Jan 31 13:46:56 [1] B.GTLD-SERVERS.NET.: Looking for CNAME cache hit of 'B.GTLD-SERVERS.NET.|CNAME'
Jan 31 13:46:56 [1] B.GTLD-SERVERS.NET.: No CNAME cache hit of 'B.GTLD-SERVERS.NET.|CNAME' found
Jan 31 13:46:56 [1] B.GTLD-SERVERS.NET.: Found cache hit for A: 192.33.14.30[ttl=172800]
Jan 31 13:46:56 [1] visolve.com.: Resolved 'com.' NS B.GTLD-SERVERS.NET. to: 192.33.14.30
Jan 31 13:46:56 [1] visolve.com.: Trying IP 192.33.14.30, asking 'visolve.com.|A'
Jan 31 13:46:58 [1] visolve.com.: Got 4 answers from B.GTLD-SERVERS.NET. (192.33.14.30), rcode=0, in 1369ms
Jan 31 13:46:58 [1] visolve.com.: accept answer 'visolve.com.|NS|ns1.visolve.com.' from 'com.' nameservers? YES!
Jan 31 13:46:58 [1] visolve.com.: accept answer 'visolve.com.|NS|ns2.visolve.com.' from 'com.' nameservers? YES!
Jan 31 13:46:58 [1] visolve.com.: accept answer 'ns1.visolve.com.|A|76.212.18.41' from 'com.' nameservers? YES!
Jan 31 13:46:58 [1] visolve.com.: accept answer 'ns2.visolve.com.|A|76.212.18.42' from 'com.' nameservers? YES!
Jan 31 13:46:58 [1] visolve.com.: determining status after receiving this packet
Jan 31 13:46:58 [1] visolve.com.: got NS record 'visolve.com.' -> 'ns1.visolve.com.'
Jan 31 13:46:58 [1] visolve.com.: got NS record 'visolve.com.' -> 'ns2.visolve.com.'
Jan 31 13:46:58 [1] visolve.com.: status=did not resolve, got 2 NS, looping to them
Jan 31 13:46:58 [1] visolve.com.: Nameservers: ns1.visolve.com.(0ms), ns2.visolve.com.(0ms)
Jan 31 13:46:58 [1] visolve.com.: Trying to resolve NS 'ns1.visolve.com.' (1/2)
Jan 31 13:46:58 [1] ns1.visolve.com.: Looking for CNAME cache hit of 'ns1.visolve.com.|CNAME'
Jan 31 13:46:58 [1] ns1.visolve.com.: No CNAME cache hit of 'ns1.visolve.com.|CNAME' found
Jan 31 13:46:58 [1] ns1.visolve.com.: Found cache hit for A: 76.212.18.41[ttl=172800]
Jan 31 13:46:58 [1] visolve.com.: Resolved 'visolve.com.' NS ns1.visolve.com. to: 76.212.18.41
Jan 31 13:46:58 [1] visolve.com.: Trying IP 76.212.18.41, asking 'visolve.com.|A'
Jan 31 13:46:58 [1] visolve.com.: error resolving
Jan 31 13:46:58 [1] visolve.com.: Trying to resolve NS 'ns2.visolve.com.' (2/2)
Jan 31 13:46:58 [1] ns2.visolve.com.: Looking for CNAME cache hit of 'ns2.visolve.com.|CNAME'
Jan 31 13:46:58 [1] ns2.visolve.com.: No CNAME cache hit of 'ns2.visolve.com.|CNAME' found
Jan 31 13:46:58 [1] ns2.visolve.com.: Found cache hit for A: 76.212.18.42[ttl=172800]
Jan 31 13:46:58 [1] visolve.com.: Resolved 'visolve.com.' NS ns2.visolve.com. to: 76.212.18.42
Jan 31 13:46:58 [1] visolve.com.: Trying IP 76.212.18.42, asking 'visolve.com.|A'
Jan 31 13:46:58 [1] visolve.com.: error resolving
Jan 31 13:46:58 [1] visolve.com.: Failed to resolve via any of the 2 offered NS at level 'visolve.com.'
Jan 31 13:46:58 [1] visolve.com.: failed (res=-1)
Jan 31 13:46:58 [1] answer to question 'visolve.com.|A': 0 answers, 0 additional, took 5 packets, 0 throttled, 1 timeouts, 0 tcp connections, rcode=2
More information about the Pdns-users
mailing list