New client email failure imediately after transferring domain and creating account ?

[caminoz74]

Hi,

 

I'm sur ethis must a be a little thing but an existing client recently purchased a new hosting plan and transferred their associated domain at the same time. Correspondance with her is via this particular domains email which is her registered contact email in her WHMCS account.

 

An issue occured as soon as she paid for the new hosting account and domain transfer the automated WHMCS 'new account welcome' email bounced back with:

 

"This message was created automatically by mail delivery software.

 

A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:

 

name@herdomain.com.au

No Such User Here"

 

Note that this automated email was sent via my accounts@mydomain.com and the nameservers are ns1.mydomain.com etc.

 

I tried to send her and email from myemail@mydomain.com and it had the same response as above, no such user.

 

So I go into her new account and set up the name@herdomain.com.au email and send her an email (from myemail@mydomain.com) and it lands in her new inbox on my server.

I send her an email from my gmail email and it lands on her old server.

 

At this stage on her computer when she checks her email it is still sending and receiving from her previous host and not receiving emails that I sent her in her acount on our server.

 

All this is occurring BEFORE the domain has actually been transferred?

 

It tells me that somehting happens between WHMCS, my WHM and my ability to send emails from anything@mydomain.com that has a new realtionship with my nameservers ns1.mydomain.com as far as the records go on my server, irrelevent to that held at the clients domain delegation details.

 

I hope I have explained this enough as I woul dliek to try an avoid this happening again.

 

Thanks heaps.

C

[othellotech]

An issue occured as soon as she paid for the new hosting account and domain transfer the automated WHMCS 'new account welcome' email bounced back with:

 

Sounds like you're hosting clients on the same machine/reseller account as you have your WHMCS. So on payment the account was created, and now "exists" on the server you are trying to send the email through - and as there are no mailboxes created yet, it'll bounce.

 

Move your WHMCS to its own server.

[caminoz74]

Thanks Rob,

 

pretty clear... makes sense. It is on the same server. It is a separate account and under a subdomain but same server.

 

Cheers

Cam

[caminoz74]

Sorry, just thinking about this, what difference would it make if my clients are on another vps that is still in my names server cluster? Would it not do the same thing?

 

WHat is actually happenning for this to occur? So if I send an email to my client via me@mydomain.com, does my WHM mail routing automatically detect that it is a client on our server and bypass an registrar settings of the existing clients nameservers? I don't quite understand why putting WHMCS on its own server would change this?

 

THanks for your time.

Cam

[LDHosting]

It sounds like you are using the local dns server (127.0.0.1) for dns resolution. This means that whenever the server does a dns lookup (in this case, for the MX record of the domain), it is asking 127.0.0.1 for the records. If the zone doesn't exist locally because there is no account set up, an external lookup is done. However, if the zone does exist (which it will after the account has been created in WHM), the local dns server will return the records held on your server rather than checking externally and so the returned MX record will indicate that the email should be delivered to your server rather than their old host. It tries but as the customer hasn't yet created an inbox on your server, your server bounces it.

 

As Rob mentioned, moving WHMCS to it's own server that doesn't use your nameserver cluster for dns resolution would stop it from happening (hosting WHMCS on a shared machine is a ropey idea anyway). Another option would be to edit your resolv.conf to use external nameservers.

[caminoz74]

It sounds like you are using the local dns server (127.0.0.1) for dns resolution. This means that whenever the server does a dns lookup (in this case, for the MX record of the domain), it is asking 127.0.0.1 for the records. If the zone doesn't exist locally because there is no account set up, an external lookup is done. However, if the zone does exist (which it will after the account has been created in WHM), the local dns server will return the records held on your server rather than checking externally and so the returned MX record will indicate that the email should be delivered to your server rather than their old host. It tries but as the customer hasn't yet created an inbox on your server, your server bounces it.

 

As Rob mentioned, moving WHMCS to it's own server that doesn't use your nameserver cluster for dns resolution would stop it from happening (hosting WHMCS on a shared machine is a ropey idea anyway). Another option would be to edit your resolv.conf to use external nameservers.

 

SO just clarify this, and the fact that i'm a little new. Your suggestion is to put my whmcs (and our company website? which is not whmcs) on a separate VDS. If that is all that is on it, do I still need to have CPanel and WHM to run those two sites which i would still want to separate and run the whmcs with an SSL. The VDS might still however be on the same 'machine' and the shared client hosting VDS... do you consider this to still be overall on a 'shared machine'?

 

Would I then have to create a nameserver for our company site and WHMCS VDS and then another set of namesevers for the cluster of clients shared servers?

 

This also sounds like it would mean that I would need 2 remote DNS servers (instead of 1) for each set of nameservers?

[caminoz74]

aside from answering the above... you mentioned I couls edit the resolv.conf to use external nameservers? woul dyou mind telling me how?

[othellotech]

aside from answering the above... you mentioned I couls edit the resolv.conf to use external nameservers? woul dyou mind telling me how?

 

ssh to your server and type "man nano"