yet another "lowest numbered mx record" error

[ramsc]

I have a reseller account on a host that uses cPanel (HOST1). I moved a couple of domains OFF that host onto another (HOST2 - totally different host, not just another server in same zone). After I terminated the accounts via WHM, anytime a user in a domain STILL ON that server tries to send email to one of the terminated domains, we get a message returned from HOST1 mailer-daemon stating a delay in sending the mail because: "Delay reason: lowest numbered MX record points to local host" It eventually just fails.

I also get that ("Has Lowest MX") message when I am on HOST1 WHM and use the mail troubleshooter to test an account that has been moved ot HOST2.

I have "user" SSH to the server, but the admins say the old domains do not show up in an DNS records on HOST1, so they say there is no problem, but I continue to experience these errors.

The terminated domains do NOT show up int /etc/localdomains.

Where else does EXIM look to determine that the domain is on 'localhost.'

I don't have root privs, so I'll just need to send some ideas to the sysadmin of HOST1 to try and get this corrected.

Versions are: WHM 9.4.0 Cpanel 9.5.0-C31 RedHat 7.3 i686

ANY IDEAS APPRECIATED... I am not cpanel licensed, so can't ask them for help - just a lowly user trying to do some 'reverse support'.

Thanks

 

[MediaHound]

Can you click a link in WHM that reads:
Edit a DNS Zone?

If you can, is the account there? no, prob.
Maybe first add the domain as if you wanted to host it there, then try to edit the zone file. Then simply point the mx record to your new host.

I'm no expert, I may be completely wrong, but it may help you.
The server is basically thinking that that email belongs to be delivered locally.
This would tell it to send it elsewhere.

Anyone else want to take a shot at it, or is this a correct solution? A bandaid, maybe, but a solution, maybe.

 

[ramsc]

I looked for the zone, but that domain had been deleted (at least from the WHM lookup).

I also tried adding it back, changing the MX record to point to the new location and then termimating again, but that was a no go...

The sysadmin does say he (she?) says that the domains are not in the DNS or the MX anywhere - I guess I gotta believe that.

I am convinced there is a text file somewhere on the system with a list of the local domains that was not cleaned up when the domains were teminated by the WHM script.

The server hasn't been rebooted since 7/11/04, so there also may be something cached in the system??

Any other ideas??

 

[chirpy]

Have you waited for the DNS information to be propagated? It'll often take the usually quoted figure of 72 hours before you can assume that it is now pointing to the new IP address.

 

[ramsc]

The messages to the terminated domain never get off the "sending" server. I get a return message after 24/48/72 hours that the message delivery failed - I mentioned that in my original post...

DNS has definitely populated - It's been 2 weeks since I transferred the domain, and we are sending/receiving mail from all other domains fine - except for domains still on the "old" server.

This can't be too hard a question for anybody who knows a little more than I do: In what order and where does EXIM look to try to deterimine if a destination domain is on "localhost" so it won't have to check outside for the intended recipient.

We've checked /etc/localdomains and /etc/localaliases and the old domains are not there. As I said, I've been told the local DNS doesn't have the old domains listed and "outside" web access to HTTP and POP3 work fine. There's got to be another text file or database SOMEWHERE that has the terminated accounts hanging around that WHM missed. I don't understand MX records enough to ask an intelligent quesiton about what to check there, but the domains do not show up in WHM, anyway, so I can't make any changes to whatever data is "easy" to get to



Thanks for the ideas.