Unable to Access eNom

Possible external cause so may be regional access issue

[solokron]

Anyone else notice enom.com is down and not resolving to an IP at the moment? May be Comcast DNS servers, may not be.

[syber]

Yes, I noticed it starting last night. I cannot get to Enom.com or any of my domains listed at Enom. Tried to call Enom support, but the wait is 30 minutes. Also using Comcast for access in Denver.

[syber]

I just talked to Comcast support. They can see enom.com from their computers, but they are not using a Comcast connection. So I suspect that this is a Comcast Server issue.

[Webwork]

Interesting.

I'm not using Comcast and I'm unable to access Enom from New Jersey.

Might be a backbone issue or other routing issue.

[syber]

This also affects any domains that use Enom's DNS. Ouch!

[Webwork]

Well, if it's a backbone or external network issue it's beyond Enom's control and they're not to blame. The root of the problem could be someone with a backhoe dug a little too deep in the wrong location. Ouch!

[edited by: Webwork at 4:33 pm (utc) on Feb. 9, 2007]

[peteboyd]

I can confirm that anyone that uses enom.com's DNS service has an issue with Comcast network users.

It seems to be localized with the Comcast network, but of course this is effecting a large audience, since Comcast is a major ISP.

I have a support ticket into enom.com and have put in a higher level support ticket to Comcast. Comcast said it would be 24 to 72 hours to resolve.

Note that if you have a domain at enom.com that uses other nameservers you are fine, its just their dedicated dynamic DNS (or bulkregisters).

dns1.name-services.com
dns2.name-services.com
dns3.name-services.com
dns4.name-services.com
dns5.name-services.com

Let's see how it resolves...

[peteboyd]

FYI, for anyone else having issues. Simply just move your nameservers to a new server and your site will begin working again.

It is definitely an issue with enom.com and Comcast not playing well with each other.

We added in two entries to point to our managed server at Rackspace and our domain started working on Comcast within about 30 minutes.

[Webwork]

I'm using a major DSL provider. not Comcast, and I continue to have access issues.

[syber]

The problem must be upstream from Comcast then.

[peteboyd]

Seems to be resolved now. If anyone has a clue about the final cause, please post.

[solokron]

Accessible again here as well.