SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #6202986
Ticket Status: Resolved

PoP: czprg01 - Ignum, s.r.o. (Prague)

DNS timed out
[cz] Shadow Hawkins on Wednesday, 04 January 2012 08:09:14
Hi SixXS admins, maybe problem with one of DNS servers in Europe? nslookup
server 2001:7b8:3:4f:202:b3ff:fe46:bec
Default server: 2001:7b8:3:4f:202:b3ff:fe46:bec Address: 2001:7b8:3:4f:202:b3ff:fe46:bec#53
www.bbs.cz
;; connection timed out; no servers could be reached ping6 2001:7b8:3:4f:202:b3ff:fe46:bec PING 2001:7b8:3:4f:202:b3ff:fe46:bec(2001:7b8:3:4f:202:b3ff:fe46:bec) 56 data bytes 64 bytes from 2001:7b8:3:4f:202:b3ff:fe46:bec: icmp_seq=1 ttl=58 time=29.4 ms 2 packets transmitted, 2 received, 0% packet loss, time 1000ms Yours sincerely, Stanislav Ulman
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Wednesday, 04 January 2012 11:35:48
Message is Locked
The state of this ticket has been changed to resolved
DNS timed out
[cz] Shadow Hawkins on Wednesday, 18 January 2012 10:08:48
I have the same problem again. timeouting DNS servers: 2001:7b8:3:4f:202:b3ff:fe46:bec 2001:1418:10:2::2 nslookup
server 2001:7b8:3:4f:202:b3ff:fe46:bec
Default server: 2001:7b8:3:4f:202:b3ff:fe46:bec Address: 2001:7b8:3:4f:202:b3ff:fe46:bec#53
www.seznam.cz
;; connection timed out; no servers could be reached
server 2001:1418:10:2::2
Default server: 2001:1418:10:2::2 Address: 2001:1418:10:2::2#53
www.seznam.cz
;; connection timed out; no servers could be reached ping6 is on both OK. Yours sincerely, Stanislav Ulman
DNS timed out
[ch] Jeroen Massar SixXS Staff on Wednesday, 18 January 2012 12:48:36
nslookup
Please do not use nslookup, please peruse 'dig' as shown below. Also note that our DNScaches only answer when the request is sourced from SixXS address space. As such, what the source address of these queries?
$ dig @2001:7b8:3:4f:202:b3ff:fe46:bec ipv6.google.com aaaa ; <<>> DiG 9.7.3-P3 <<>> @2001:7b8:3:4f:202:b3ff:fe46:bec ipv6.google.com aaaa ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56843 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;ipv6.google.com.INAAAA ;; ANSWER SECTION: ipv6.google.com.83178INCNAMEipv6.l.google.com. ipv6.l.google.com.300INAAAA2a00:1450:4001:c01::68 ;; Query time: 62 msec ;; SERVER: 2001:7b8:3:4f:202:b3ff:fe46:bec#53(2001:7b8:3:4f:202:b3ff:fe46:bec) ;; WHEN: Wed Jan 18 12:46:47 2012 ;; MSG SIZE rcvd: 82
$ dig @2001:1418:10:2::2 ipv6.google.com aaaa ; <<>> DiG 9.7.3-P3 <<>> @2001:1418:10:2::2 ipv6.google.com aaaa ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57723 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;ipv6.google.com.INAAAA ;; ANSWER SECTION: ipv6.google.com.604800INCNAMEipv6.l.google.com. ipv6.l.google.com.300INAAAA2a00:1450:4001:c01::63 ;; Query time: 96 msec ;; SERVER: 2001:1418:10:2::2#53(2001:1418:10:2::2) ;; WHEN: Wed Jan 18 12:47:41 2012 ;; MSG SIZE rcvd: 82
DNS timed out
[cz] Shadow Hawkins on Thursday, 19 January 2012 08:44:56
...Also note that our DNScaches only answer when the request is sourced from SixXS address space. You are right, I didn't know it. When I added routes to my routing table, both DNS ansvers correctly. ip -6 route add 2001:7b8:3:4f:202:b3ff:fe46:bec via 2a01:8c00:ff00:13b::1 dev sixxs ip -6 route add 2001:1418:10:2::2 via 2a01:8c00:ff00:13b::1 dev sixxs Thank You very much for the important note! Stanislav Ulman

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker