The threads about the recent problems at ***** often also mention mail problems. I don't think it has been appreciated though that ***** have changed the configuration of the mail servers in such a way that if you use fake ip's then it is now simply **no longer possible** to send mail to those domains.

All mail addressed to domains mapped to fake ip's is being refused and returned to sender.

I have one primary domain name (cowderoy.com) and four secondary domain names (palamede.com, notzai.com, enpassant.dk, mjae.com) with *****. The secondary domain names are mapped to fake ip addresses which for http access point to directories in my main domain.

This gave us http, ftp and pop3 access to our servers via either the main or the secondary domain names. So for instance it was possible to surf to http://secondaryname.com/, ftp to ftp://secondaryname.com/ and also to send mail to name@secondarydomain.com.

This is what I believed fake ips were for and there is nothing on the ***** site to contradict the idea. This set up has been working perfectly satisfactorily for two years now.

As of the beginning of this week this has simply stopped working for mail. Mail to the maindomain name is ok but all mail to any of the secondary domain names is returned to sender.

I got through finaly to a technician on the support chat who blithely informed me that this function "was not supported" and that it had been stopped.

I have several email addresses that were being used as important contact points that ***** now tells me are useless, or at least they do once i finaly manage to get through to ask them what's happened.

This was done entirely without warning. I can find no trace whatsoever on *****s site warning users that their email addresses were going to be cut off.

The package I signed up for (graduate unix) still offers fake ip's as an optional extra in such a way that it is perfectly reasonable to assume that they will be useable for all services. Nowhere is it mentioned that it does not work with mail (as it has been doing for the past two years).

I can't believe that i'm the only person having this problem given the thousands of sites hosted at ***** but I've not seen any mention on the newsgroups.

Are people still wrongly assuming, as I did at first, that this is just more fall out from the "code red" problems?
Or does nobody much use this feature and i'm on my own?

YUP, I didn't call, but figured that's what was going on.

Sure wish I had kept hard copies of the original 'features' I signed up for ... because I'm sure they mentioned SMTP & POP for Fake IPs (it was one of the reasons I used a Fake IP in one situation).

That's okay though, because like I said, as soon as I figured that out ... it was bye bye ... both for the fakeIP and the realIP that it was associated with.

Just got off of:
http://hostingsupport.com/NetStatusView.asp?ID=402

Here's what the problem report states:
------------------------------------------------
Mail is bouncing to Fake IP/Mirror domains currently. We are working to resolve the issue and expect the domains to be back working off the main domain's mail server within 12-24 hours. We apologize about any inconvenience this may cause you.***UPDATE*** 4:37am CST, all Fake IP/Mirror domains on our shared servers are fixed and working. We are still working to repair all Fake IPs/Mirrors on our dedicated machines. The ETR for dedicateds will be another 3-4 hours.
------------------------------------------------------------

NOW IF THEY HAD JUST ADMITTED THAT 2 WEEKS AGO, they may have kept me as a customer ... well, probably not after the above hassle, along with their failure during CodeRed.

Originally posted by Palamede
I got through finaly to a technician on the support chat who blithely informed me that this function "was not supported" and that it had been stopped.


This is a rare event -- getting through to a tech. You should enter the lottery; you seem to have a lot of luck ;)


I can't believe that i'm the only person having this problem given the thousands of sites hosted at ***** but I've not seen any mention on the newsgroups.


Trust me -- you're far from the only one having problems.


Are people still wrongly assuming, as I did at first, that this is just more fall out from the "code red" problems?
Or does nobody much use this feature and i'm on my own?

***** is clueless when it comes to Code Red. I have a server there and it has been hit about 50,000 times in the past few days. I also have servers with a few other providers -- ZERO Code Red scans.

I think ***** needs a lesson on network security...They're completely clueless.