- Joined
- Mar 29, 2003
- Messages
- 894
- Reaction score
- 0
Enom now acknowledges that sites using their nameservers and redirecting to folders elsewhere are not reachable from any ISP that depends on AT&T's backbone. This includes Cox and Comcast. It also includes lots of .gov sites. Here's the word that I got from Amin Taheri in tech support
"The problem is that anyone who is going through the att network (such as cox, comcast, @home, attbi, etc.) are not able to get to sites that use the redirector. This is becuase ATT is blocking access to the sites due to a few phishing sites that were up on the redirector servers. We are working with them to get this resolved but we are at their mercy as to a time line."
Later he said "unfortunately we have to wait for internap and att to get this resolved between themselves"
I suggested:
"It seems like one thing enom could do is to add some new i.p. addresses that are not contiguous with the ones that are blocked, and map the servers to these addresses. That way the internet would route around the block. You'd want to be sure that all of the phishing sites were taken down first, of course."
He replied:
"Thanks, but we already have 16 servers in non contiguous IP spaces, as well in different parts of the country and using different ISPs. Believe me, this will get taken care of, but either way enom can not make this go any faster, this is now an issue between att and internap."
The bottom line is that if you have any high income domains that depend on enom's nameservers you should move them somewhere else for now.
"The problem is that anyone who is going through the att network (such as cox, comcast, @home, attbi, etc.) are not able to get to sites that use the redirector. This is becuase ATT is blocking access to the sites due to a few phishing sites that were up on the redirector servers. We are working with them to get this resolved but we are at their mercy as to a time line."
Later he said "unfortunately we have to wait for internap and att to get this resolved between themselves"
I suggested:
"It seems like one thing enom could do is to add some new i.p. addresses that are not contiguous with the ones that are blocked, and map the servers to these addresses. That way the internet would route around the block. You'd want to be sure that all of the phishing sites were taken down first, of course."
He replied:
"Thanks, but we already have 16 servers in non contiguous IP spaces, as well in different parts of the country and using different ISPs. Believe me, this will get taken care of, but either way enom can not make this go any faster, this is now an issue between att and internap."
The bottom line is that if you have any high income domains that depend on enom's nameservers you should move them somewhere else for now.
