rbmacct
asked on
DNS MX record cached
We are having an issue with DNS. We moved our MX records about 2 months ago from one spam filter (hosted) to another (hosted). Still after 2 months we are seeing e-mail traffic still going through our old one. (About 1-2% - 10-15 domains). Network Solutions hosts our DNS. I have called them twice to verify they aren't caching any old MX records and they insist that they are NOT.
Luckily our old spam filter host still accepts and delivers mail. However I'm now stuck as to why mail is still going to an 2 month old MX record that doesn't exist anywhere anymore.
I highly doubt these e-mail servers from the senders are caching old DNS records. Considering after we made the MX change mail almost immediately started going through the new host.
I'm lost, much help would be appreciated.
Luckily our old spam filter host still accepts and delivers mail. However I'm now stuck as to why mail is still going to an 2 month old MX record that doesn't exist anywhere anymore.
I highly doubt these e-mail servers from the senders are caching old DNS records. Considering after we made the MX change mail almost immediately started going through the new host.
I'm lost, much help would be appreciated.
Kent W
This sounds like your OLD DNS sever still has the zone/domain record loaded, and even though you have moved hosts, and DNS servers, anyone still using the OLD DNS servers will of course get the OLD answer. Make sure that at the OLD DNS server, your zone has been completely deleted. I doubt it's cache, nothing would live that long.
ASKER
We didn't move the DNS hosts. We just updated the MX records that is and was hosted with Network Solutions.
The cache will be there and valid until they manually clear the cache. I think this is applicable to clients, servers etc.
ASKER
I guess I shouldn't of used the word 'moved'. We just updated our MX records at the current DNS host (Network Solutions). Sorry for the confusion.
Can you identify the source to the mail that is misdirected? Look at the headers for some of these 1-2% of the messages you should see a common mail server or servers. These would be the places to continue your investigation.
Check you mail server settings.
specifically Send connector settings if it is an exchange server .
specifically Send connector settings if it is an exchange server .
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
How would clients/servers get their DNS information from someplace that isn't my DNS host? They would have to go to the name servers first to get back to the old spam filter (old MX records) which they shouldn't because the MX records point elsewhere. I just don't understand how the old spam filter would cache/server DNS requests when they aren't even my DNS host nor do my MX records point there.
-Ask your DNS host to change MX Time to live ( TTL ) to something short ( e.g. 30 min)
-Make sure they didn't "ADD" your new spam filter hosts to your records ; they should also remove existing ones.
-Make sure they didn't "ADD" your new spam filter hosts to your records ; they should also remove existing ones.
ASKER
We already changed the TTL to 3600. I'm calling them again to see if I can get higher up the chain. I feel this is definitely a Network Solutions problem. It just doesn't make sense why mail is still going to a 2 month old MX record. I'll update after I speak with them again.
I don't think you understood. People using your old spam filter, if this is a popular service, could be picking up the old MX from the actual spam filter you were using, if their mail is routed through that service. A lot of these services will cache MX, or just save DNS resolutions, within the service itself, independent of DNS MX. The fact that they are still accepting mail for your domain is one clue that could be the issue. Regular DNS MX caching and related issues seem to be getting you nowhere.
> I have called them twice to verify they aren't caching any old MX records and they insist that they are NOT.
If they host it they will not be caching anything, they will be providing authoritative answers.
My DNS server might cache a response to a query via network solutions (for example), but that won't be their fault, it'll be mine.
> However I'm now stuck as to why mail is still going to an 2 month old MX record that doesn't exist anywhere anymore.
You know, I've seen a problem like this before. I don't suppose the people delivering via the "old MX" are also customers of the same anti-spam provider are they?
If they are you may find that mail is being routed internally through the anti-spam system, not delivery via the MX.
Chris
If they host it they will not be caching anything, they will be providing authoritative answers.
My DNS server might cache a response to a query via network solutions (for example), but that won't be their fault, it'll be mine.
> However I'm now stuck as to why mail is still going to an 2 month old MX record that doesn't exist anywhere anymore.
You know, I've seen a problem like this before. I don't suppose the people delivering via the "old MX" are also customers of the same anti-spam provider are they?
If they are you may find that mail is being routed internally through the anti-spam system, not delivery via the MX.
Chris
Actually, ignore that, it's exactly what mugojava said. Apologies for the repetition, need to pay more attention.
Chris
ASKER
I did lookup's on the MX's for the domains that were going through our same old spam filter and they aren't pointed to the same filter, so that would tell me they aren't using the same spam filter as we were. I'm going to call ForeFront (old spam filter) and see what they have to say.
Ignore the MX, if it's routing internally through their system it will have nothing to do with the MX.
I used to have a problem like this with MessageLabs, shifted away from them but the account wasn't quite cancelled, stuff from their other customers was still delivered by the path they defined (not the path the MX defined).
That's what mugojava is getting at.
Chris
I used to have a problem like this with MessageLabs, shifted away from them but the account wasn't quite cancelled, stuff from their other customers was still delivered by the path they defined (not the path the MX defined).
That's what mugojava is getting at.
Chris
Dont take any DNS hosting company's word for it on what they say your MX records are, check it for yourself. Here is an easy way:
Go to this site and input your domain name:
http://www.mxtoolbox.com
It will report back what the internet is seeing as your MX records. What you may also want to do is verify that your name servers are where you think they are:
http://www.networksolutions.com/whois/index.jsp
At the bottom, you will find your name servers in listed order. Make sure these are the Network Solutions name servers.
Please report back what you find. Make sure to change the domain names to something fictitious, if you do post the results. That may be helpful.
Go to this site and input your domain name:
http://www.mxtoolbox.com
It will report back what the internet is seeing as your MX records. What you may also want to do is verify that your name servers are where you think they are:
http://www.networksolutions.com/whois/index.jsp
At the bottom, you will find your name servers in listed order. Make sure these are the Network Solutions name servers.
Please report back what you find. Make sure to change the domain names to something fictitious, if you do post the results. That may be helpful.
ASKER
It appears that was the problem. The cloud for Microsoft was caching the MX records for other domains that were hosted in the same cloud. As soon as I removed our domains from MS ForeFront they removed their cached DNS and went off the public records.
Good enough :)
Chris
Sweet. Glad that helped :)