Dust- Traceroute Timeout To Phatmass.com

[arfink]

[code]
traceroute to 207.7.87.129 (207.7.87.129), 30 hops max, 40 byte packets
1 gigagate1 (128.112.128.114) 0.542 ms 0.714 ms 0.395 ms
2 vgate1 (128.112.12.22) 0.477 ms 0.370 ms 0.361 ms
3 te-1-4-3998-pe01.philadelphia.pa.ibone.comcast.net (24.104.128.89) 13.819 ms 48.913 ms 48.004 ms
4 te-0-1-0-12-cr01.ashburn.va.ibone.comcast.net (68.86.84.177) 17.589 ms 23.546 ms 23.976 ms
5 xe-10-2-0.edge2.Washington12.Level3.net (4.26.6.9) 10.425 ms 10.392 ms 13.110 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 ae-3-80.edge3.Dallas1.Level3.net (4.69.145.136) 55.025 ms 46.191 ms ae-2-70.edge3.Dallas1.Level3.net (4.69.145.72) 126.226 ms
12 COLO4-DALLA.edge3.Dallas1.Level3.net (8.9.232.74) 61.913 ms 42.742 ms 42.461 ms
13 206.123.64.42 (206.123.64.42) 55.076 ms 53.459 ms 48.504 ms
14 72.249.129.125 (72.249.129.125) 42.197 ms 43.667 ms 44.388 ms
15 vz84-tx.privatesystems.net (72.249.97.84) 45.152 ms 46.243 ms 44.991 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

Done.
[/code]

Your registrar, ENOM, seems to be falling down on the job. Their route through tx.privatesystems.net (also owned by ENOM) is failing repeatedly, causing frequent timeouts. Anything you can do to fix this?

Edited September 29, 2012 by arfink

[Nihil Obstat]

[img]http://www.idolol.com/pictures/fec3392b0dc073244d38eba1feb8e6b7.jpg[/img]

[TheresaThoma]

Ummm fink I have absolutely no clue what that means. I hope that dUST does or you can translate.

[dUSt]

I've never heard of ENOM. What can I do, change registrars?

[Winchester]

Call the cyber police and have them backtrace it. ENOM dun guf'd.

[Lil Red]

[img]http://cdn2.mamapop.com/wp-content/uploads/2011/11/nom-nom.jpg[/img]

[arfink]

[quote name='dUSt' timestamp='1348906104' post='2487944']
I've never heard of ENOM. What can I do, change registrars?
[/quote]

Don't tell me you've never done a traceroute or whois on your own domain.

EDIT:
NVM, I found new info.

Edited September 29, 2012 by arfink

[arfink]

I should inform you that ENOM is a problematic registrar. You have purchased services from ENOM through one of their resellers, I don't know which though. The WHOIS database lists ENOM as the registrar, not the reseller. ENOM has a history of customer complaints and is the #1 spam-hosting registrar as of Feb 2012.

https://en.wikipedia.org/wiki/ENom

I don't know if it would be possible or financially feasible for you to use a different parent registrar or how one would go about doing that. I'm not that much of an expert. But I can say you'll likely continue to have these problems if you continue to use ENOM as your registrar.

[dUSt]

I use NameCheap.com. It looks like they use to be an ENOM reseller, and apparently are still using their ENOM reseller account instead of their own.

[BigJon16]

And that is the story of how Arfink saved Phatmass.

[arfink]

[quote name='BigJon16' timestamp='1348947522' post='2488119']
And that is the story of how Arfink saved Phatmass.
[/quote]

[img]http://www.fatwallet.com/static/attachments/94486_wat_heidi.jpg[/img]