Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > Issues with netfirms DNS servers
Issues with netfirms DNS servers
Posted by Cyborg--, 04-13-2010, 09:27 PM |
I have been having intermittent issues with DNS resolving on netfirms.com registrred domain.
ns1.netfirms.com seems to be responding, but ns2 falls in a endless loop :
Tracing route to ns2.netfirms.com [70.35.17.1]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms unknown [192.168.2.1]
2 19 ms 19 ms 18 ms 206.248.154.102
3 19 ms 19 ms 19 ms 69.196.136.66
4 27 ms 24 ms 24 ms tge6-1.fr3.yyz.llnw.net [208.111.182.137]
5 23 ms 19 ms 19 ms xe-1-1-0-350.tor10.ip4.tinet.net [77.67.69.69]
6 45 ms 45 ms 45 ms xe-11-3-0.nyc30.ip4.tinet.net [89.149.184.109]
7 38 ms 37 ms 37 ms te3-4.ccr01.jfk07.atlas.cogentco.com [154.54.10.
89]
8 37 ms 37 ms 37 ms te0-3-0-1.mpd21.jfk02.atlas.cogentco.com [154.54
.1.133]
9 38 ms 37 ms 37 ms te7-2.mpd01.yyz02.atlas.cogentco.com [154.54.27.
162]
10 38 ms 38 ms 38 ms netfirms.demarc.cogentco.com [38.99.210.114]
11 37 ms 37 ms 37 ms 70.35.17.28
12 38 ms 39 ms 38 ms 10.200.25.1
13 38 ms 133 ms 37 ms 70.35.17.28
14 39 ms 39 ms 38 ms 10.200.25.1
15 37 ms 38 ms 38 ms 70.35.17.28
16 38 ms 38 ms 38 ms 10.200.25.1
17 37 ms 49 ms 38 ms
Their websites have been unreachable intermittently also.
C:\Users\Guillaume>ping www.netfirms.com
Pinging www.netfirms.com [67.23.128.26] with 32 bytes of data:
Reply from 172.16.1.1: TTL expired in transit.
Reply from 172.16.1.1: TTL expired in transit.
Reply from 172.16.1.1: TTL expired in transit.
Reply from 172.16.1.1: TTL expired in transit.
This brings down a few of my domains... Not good !
Anybody else having issues ?
- Cyb |
Posted by Canadaka, 04-14-2010, 05:13 AM |
wow glad too see i'm not the only one! I have had people telling me for over a month that they sometimes couldn't access my gaming clans website clan.canadaka.ca I could never reproduce the problem at home, so i thought it was there problem.
Well today I was at a clients using his internet and I couldn't access the site, i could press refresh several times and it would sometimes eventualy load. So I thought i would try some other domains i have registered at netfirms like politwitter.ca and wastedtalent.ca the same problem existed!!!! All my domains that are not on netfirms work fine.
I sent a message to the netfirms support yesterday, still no reply. This is a pretty serious issue if this has been happening for motnhs. But the last few days I think its gotten worse, since I have numerous reports. |
Posted by plumsauce, 04-14-2010, 06:16 AM |
from intodns.com:
Code:
Nameserver records returned by the parent servers are:
ns1.netfirms.com. ['70.42.30.1'] (NO GLUE) [TTL=86400]
ns2.netfirms.com. [] (NO GLUE) [TTL=86400]
a.ca-servers.ca was kind enough to give us that information.
from another source:
Code:
Results
7.7% of queries will end in failure at 192.112.36.4 (g.root-servers.net) - query timed out
23.1% of queries will end in failure at 70.42.30.1 (ns1.netfirms.com) - failed to resolve ns2.netfirms.com due to 70.42.30.1 - query timed out
46.2% of queries will end in failure at 70.42.30.1 (ns1.netfirms.com) - query timed out
23.1% of queries will end in failure at 70.35.17.1 (ns2.netfirms.com) - query timed out
Have you considered whether their name servers are under heavy load? All it takes is for them to be hosting a domain that is under DDOS. |
Add to Favourites Print this Article
Also Read