Accommodating a domain that doesn't exist

[GoWilkes]

One of my domains is a .CO extension, because the .COM is not available. It hasn't been used since 1999, and the owner of it hasn't replied to any of my emails or letters :-( So I gave up and bought the .NET and the .CO.

Here's the question, though.

For clients that are hosting on my server, sometimes they mistakenly email me using the .COM extension even though I don't own it. On my old VPS, I "fixed" this by creating an account for the .COM and forwarded any emails sent to it to my .NET. Which worked just fine; it obviously doesn't work for everyone else, but at least I don't miss emails from hosting clients.

I'm setting up a new VPS right now, and before I copy that over... is there a better way? Can I add something to the .NET's DNS records to accommodate for emails sent to the .COM... and potentially other domain misspellings?

 

[cPRex]

Hey there! Nope, it sounds like you're doing this the best way possible. Creating that account in WHM and ensuring the email is set to local delivery will let other sites on that one server deliver the messages locally. Since you don't own the domain or manage the DNS, you won't be able to do anything on the DNS side to get that traffic adjusted.

 

[keat63]

When I used the transfer tool to move some domains to a new server, I neglected to remove the originals.
And even though the DNS had propagated, I couldn't for the life of me figure out why I wasn't receiving email from the old server to the new one.
Until it dawned on me, as far as the old server was concerned, the transferred domain was still within it's own remit, and didn't need to look outside.

I'm not sure if this is the correct way of doing what you want, but it's known to work.