|
tix.sixxs.net down?
![[de]](/s/countries/de.gif) Shadow Hawkins on Saturday, 30 January 2010 18:51:47
Hi @ all,
I'm not able to connect to tic.sixxs.net. Is it down?
Thanks for your help!
HaM1
tix.sixxs.net down?
I'm not able to connect to tic.sixxs.net. Is it down?
Connect exactly how to tic.sixxs.net?
Also, you might want to provide a traceroute and also check that you are not trying to connect to it too often as the it will very impolitely ratelimit you.
tix.sixxs.net down?
Carmen Sandiego on Saturday, 30 January 2010 21:18:26
I have the same problem. It looks like tic.sixxs.net cannot be resolved:
# host tic.sixxs.net
Host tic.sixxs.net not found: 2(SERVFAIL)
#
tix.sixxs.net down?
'host' is a really really bad tool, as it does not tell you anything, please use a 'dig +trace tic.sixxs.net' to get more details.
tix.sixxs.net down?
![[us]](/s/countries/us.gif) Shadow Hawkins on Sunday, 31 January 2010 02:19:41
ns1 and ns2.sixxs.net are returning an A record of
tic.sixxs.net. 3600 IN A 193.109.122.244
tic.sixxs.net. 3600 IN A 213.204.193.2
But ns3.sixxs.net is returning a CNAME record that goes nowhere.
Lyle Giese
LCR Computer Services, Inc.
ncc1701b:~ # dig @ns3.sixxs.net tic.sixxs.net
; <<>> DiG 9.4.2-P1 <<>> @ns3.sixxs.net tic.sixxs.net
; (2 servers found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33983
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 6
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;tic.sixxs.net. IN A
;; ANSWER SECTION:
tic.sixxs.net. 86400 IN CNAME tic.m.sixxs.net.
;; AUTHORITY SECTION:
m.sixxs.net. 86400 IN NS ns1.sixxs.net.
m.sixxs.net. 86400 IN NS ns3.sixxs.net.
m.sixxs.net. 86400 IN NS ns2.sixxs.net.
;; ADDITIONAL SECTION:
ns1.sixxs.net. 86400 IN A 213.197.29.32
ns1.sixxs.net. 86400 IN AAAA 2001:838:1:1:210:dcff:fe20:7c7c
ns2.sixxs.net. 86400 IN A 193.109.122.62
ns2.sixxs.net. 86400 IN AAAA 2001:7b8:3:1e:290:27ff:fe0c:5c5e
ns3.sixxs.net. 86400 IN A 193.1.31.74
ns3.sixxs.net. 86400 IN AAAA 2001:770:18:8::4
;; Query time: 241 msec
;; SERVER: 2001:770:18:8::4#53(2001:770:18:8::4)
;; WHEN: Sat Jan 30 19:16:35 2010
;; MSG SIZE rcvd: 237
tix.sixxs.net down?
ns1 and ns2.sixxs.net are returning an A record of tic.sixxs.net. 3600 IN A 193.109.122.244 tic.sixxs.net. 3600 IN A 213.204.193.2 But ns3.sixxs.net is returning a CNAME record that goes nowhere.
But why are you quering those DNS servers? The zones live on a completely different set of hosts.
As I mentioned above, use 'dig' for figuring out DNS issues, not 'host' and especially not 'nslookup' (which comes with yet another set of problems)
$ dig +trace tic.sixxs.net
[...]
sixxs.net. 172800 IN NS ns.paphosting.eu.
sixxs.net. 172800 IN NS ns.paphosting.net.
sixxs.net. 172800 IN NS ns.paphosting.nl.
;; Received 135 bytes from 2001:503:231d::2:30#53(B.GTLD-SERVERS.net) in 109 ms
tic.sixxs.net. 3600 IN A 213.204.193.2
tic.sixxs.net. 3600 IN A 193.109.122.244
sixxs.net. 3600 IN NS ns.paphosting.net.
sixxs.net. 3600 IN NS ns.paphosting.nl.
sixxs.net. 3600 IN NS ns.paphosting.eu.
;; Received 164 bytes from 2a02:898:28::3#53(ns.paphosting.nl) in 3 ms
tix.sixxs.net down?
![[be]](/s/countries/be.gif) Shadow Hawkins on Sunday, 31 January 2010 12:43:47
same problem, couldn't resolve tic.sixxs.net
tix.sixxs.net down?
Shadow Hawkins on Sunday, 31 January 2010 18:58:20
It's resolving now.
tix.sixxs.net down?
Shadow Hawkins on Monday, 01 February 2010 03:44:44
I did not keep the entire thread of queries, but it seems that the root servers are returning different information than they were earlier. Or something happened and my recursive servers had the wrong info.
I know how to use dig and would have started at the root servers and worked down the dns tree just like a recursive query would have. I would have gotten those name server names from the root servers earlier today.
Oh well, it looks correct now.
Lyle Giese
LCR Computer Services, Inc.
|
![[ch]](/s/countries/ch.gif)
on Saturday, 30 January 2010 19:03:53
Posting is only allowed when you are