ClubSNAP server down due to DNS problem


Status
Not open for further replies.

Jason Ho

Active Member
Jan 17, 2002
2,252
0
36
51
jasonho.clubsnap.org
Due to some DNS server (located in US) issues, ClubSNAP server was inaccessible for the last 24 hours.

We were told that the DNS server is currently being fixed and worked on and we should be expecting the DNS to be fully working again by end of today.

Apologise for the downtime and inconvenience caused during this period of time.
 

I think it's hosted by Starhub.
 

Hmmm.. there seems to be a big DNS problem in US, all hosted by NameZero and company.
 

Target Name: www.clubsnap.org
IP: 203.117.141.145
Date/Time: 10/12/2002 4:53:04 PM

1 0 ms [192.168.0.100]
2 51 ms syd-uun-ce1.iinet.net.au [203.166.38.115]
3 39 ms syd-uun-gw.iinet.net.au [203.166.38.113]
4 116 ms 325.at-3-0-0.XR2.SYD2.ALTER.NET [210.80.32.253]
5 114 ms so-6-0-0.TR1.SYD2.ALTER.NET [210.80.51.249]
6 205 ms 0.so-5-0-0.IR2.SAC2.Alter.Net [210.80.49.61]
7 188 ms pos2-0.ir2.sac1.alter.net [137.39.31.206]
8 207 ms 0.so-5-2-0.TL1.LAX9.ALTER.NET [152.63.0.146]
9 204 ms 0.so-4-0-0.TL1.SAC1.ALTER.NET [152.63.0.98]
10 195 ms POS7-0.BR6.SAC1.ALTER.NET [152.63.53.5]
11 188 ms p4-5-0-0.r00.plalca01.us.bb.verio.net [129.250.9.97]
12 243 ms p4-5-0-0.r00.plalca01.us.bb.verio.net [129.250.9.97]
13 226 ms p16-1-1-0.r21.plalca01.us.bb.verio.net [129.250.3.84]
14 237 ms p16-2-0-0.r81.sttlwa01.us.bb.verio.net [129.250.2.219]
15 386 ms p1-0-1-1.r00.sngpsi01.sg.bb.verio.net [129.250.3.70]
16 355 ms p4-0-2-0.r01.osakjp01.jp.bb.verio.net [129.250.4.75]
17 336 ms ge-1-2-0.r00.osakjp01.jp.bb.verio.net [129.250.4.114]
18 409 ms [203.118.3.132]
19 401 ms [203.118.1.12]
20 390 ms f25-r64.cyberway.com.sg [203.117.224.30]
21 402 ms [203.117.141.145]

:eek:
 

I'm first to admit, nvr understood anything about networks... nvr bother to ask too...haha
(well, 9lives taking CCNA rite? :D )

just curious, how come DNS is not using local one? meaning that even if US DNS server is down, local users shouldn't be affected... right? wrong? :dunno:
 

Originally posted by Zoomer
Wrong.

Almost all the root servers are in the US. ;p

They are used to resolve

yupz....tht's what confuses me.

How come need to go to root servers? can't it be resolve locally? or local no DNS servers at all? ;p :dunno:
 

Originally posted by Shadus
I'm first to admit, nvr understood anything about networks... nvr bother to ask too...haha
(well, 9lives taking CCNA rite? :D )

just curious, how come DNS is not using local one? meaning that even if US DNS server is down, local users shouldn't be affected... right? wrong? :dunno:

our domain name is bought from USA , so we are using their DNS server. the dns server contains the A record. this A record will point to a server ie: an ip adress. for our case, our A record www.clubsnap.org will point to 203.117.141.145. If the dns server is down. the host will not know where is www.clubsnap.org point to. That's why when u ping www.clubsnap.org when the dns server is down, it will not resolve to ip address.

ps: btw ccna never taught me that, it is a different subject
 

Originally posted by Shadus


yupz....tht's what confuses me.

How come need to go to root servers? can't it be resolve locally? or local no DNS servers at all? ;p :dunno:

If I didn't remember wrongly, it goes something like this. When you type "www.clubsnap.org" in your browser...

1. Your system will check the DNS server the ISP assigned to you when you logon and find out "who is the DNS Server for clubsnap.org"?

2. ISP DNS Server will return the DNS Server to which clubsnap.org is registered, in this case, mydomain.com

3. Now, query mydomain.com for the IP address of "www.clubsnap.org" and return it to your browser. (i.e. ask for the Address record of "www.clubsnap.org")

4. Browser now requests a web page from "203.117.141.145" using HTTP protocol.

Something like that. I might be rusty. The experts can correct me if I am wrong. ;p

So when the DNS server goes down, step 3 can never be completed.

Regards
CK
 

Originally posted by Zoomer
Wrong.

Almost all the root servers are in the US. ;p

They are used to resolve www.clubsnap.org -> 203.117.141.145

So, if you just use http://203.117.141.145

then theres no problems. :)
actually there has been quite some DoS attack on DNS servers lately ......

i wont be surprised if this was a DoS attack also ......DNS servers are quite vulnerable ...
 

IRC Servers is getting DOSsed quite heavily these days.
 

Originally posted by ckiang


If I didn't remember wrongly, it goes something like this. When you type "www.clubsnap.org" in your browser...

1. Your system will check the DNS server the ISP assigned to you when you logon and find out "who is the DNS Server for clubsnap.org"?

2. ISP DNS Server will return the DNS Server to which clubsnap.org is registered, in this case, mydomain.com

3. Now, query mydomain.com for the IP address of "www.clubsnap.org" and return it to your browser. (i.e. ask for the Address record of "www.clubsnap.org")

4. Browser now requests a web page from "203.117.141.145" using HTTP protocol.

Something like that. I might be rusty. The experts can correct me if I am wrong. ;p

So when the DNS server goes down, step 3 can never be completed.

Regards
CK

Nah. It can't query mydomain.com for the IP address cos it would need it ip for mydomain.com. ;p

How Stuff WOrks to the rescue!
http://www.howstuffworks.com/dns.htm

Lazy to type. ;p
 

Originally posted by Zoomer


Nah. It can't query mydomain.com for the IP address cos it would need it ip for mydomain.com. ;p

How Stuff WOrks to the rescue!
http://www.howstuffworks.com/dns.htm

Lazy to type. ;p

Eeks. My bad. What I was trying to say is that it will know mydomain.com (IP) is the DNS for clubsnap.org and query for clubsnap.org from there.

Yeah, howstuffworks has the full details. I think I got about 80% of it. Memory failing lar. ;p

Regards
CK
 

Status
Not open for further replies.