Strange DNS Problem

I had a domain located on a shared server that was giving us problems.
We moved it to a new company, that is great. The problem is, even though
I changed the DNS to the new company several months ago and disabled the
account on the old server, about 1 in 20 emails is still going to the
old server. How can that happen? What are some DNS servers not updated?
Do I have to delete rather than disable the account on the old server?

mcp6453 <mcp6453@earthlink.net> writes:
> I had a domain located on a shared server that was giving us
> problems. We moved it to a new company, that is great. The problem is,
> even though I changed the DNS to the new company several months ago
> and disabled the account on the old server, about 1 in 20 emails is
> still going to the old server. How can that happen? What are some DNS
> servers not updated? Do I have to delete rather than disable the
> account on the old server?


Are, by chance the emails that are getting misdirected coming from
folks that are also customers of the old hosting company?


I noted this effect when I switched hosts. The reason it happens is
that from the same server/provider, the mail server thinks the DNS
records at the old company are authoritative because the mail server
doesn't go out to the internet to check otherwise.

The only fix is to have the domain purged from the old company's DNS
records. That way, when the old company mail server goes to deliver
@yourdomain.com the resolver will have to go to the root servers and
they'll point it to the right DNS records, correct new IP and send
your mail to the right place.

Best Regards,
--
Todd H.
http://www.toddh.net/

Todd H. wrote:
> mcp6453 <mcp6453@earthlink.net> writes:
>
>>I had a domain located on a shared server that was giving us
>>problems. We moved it to a new company, that is great. The problem is,
>>even though I changed the DNS to the new company several months ago
>>and disabled the account on the old server, about 1 in 20 emails is
>>still going to the old server. How can that happen? What are some DNS
>>servers not updated? Do I have to delete rather than disable the
>>account on the old server?
>
>
>
> Are, by chance the emails that are getting misdirected coming from
> folks that are also customers of the old hosting company?
>
>
> I noted this effect when I switched hosts. The reason it happens is
> that from the same server/provider, the mail server thinks the DNS
> records at the old company are authoritative because the mail server
> doesn't go out to the internet to check otherwise.
>
> The only fix is to have the domain purged from the old company's DNS
> records. That way, when the old company mail server goes to deliver
> @yourdomain.com the resolver will have to go to the root servers and
> they'll point it to the right DNS records, correct new IP and send
> your mail to the right place.
>
> Best Regards,


Actually, some of the problems are caused by this reason, I just
discovered. There are several more that I am trying to uncover, but
you're right on the money.

Thanks for all for the advice!

mcp6453 <mcp6453@earthlink.net> writes:

> Todd H. wrote:
> > mcp6453 <mcp6453@earthlink.net> writes:
> >
> >>I had a domain located on a shared server that was giving us
> >>problems. We moved it to a new company, that is great. The problem is,
> >>even though I changed the DNS to the new company several months ago
> >>and disabled the account on the old server, about 1 in 20 emails is
> >>still going to the old server. How can that happen? What are some DNS
> >>servers not updated? Do I have to delete rather than disable the
> >>account on the old server?
> > Are, by chance the emails that are getting misdirected coming from
> > folks that are also customers of the old hosting company? I noted
> > this effect when I switched hosts. The reason it happens is
> > that from the same server/provider, the mail server thinks the DNS
> > records at the old company are authoritative because the mail server
> > doesn't go out to the internet to check otherwise.
> > The only fix is to have the domain purged from the old company's DNS
> > records. That way, when the old company mail server goes to deliver
> > @yourdomain.com the resolver will have to go to the root servers and
> > they'll point it to the right DNS records, correct new IP and send
> > your mail to the right place. Best Regards,
>
>
> Actually, some of the problems are caused by this reason, I just
> discovered. There are several more that I am trying to uncover, but
> you're right on the money.
>
> Thanks for all for the advice!

w00t!

Best Regards,
--
Todd H.
http://www.toddh.net/

Todd H. wrote:
> mcp6453 <mcp6453@earthlink.net> writes:
>
>
>>Todd H. wrote:
>>
>>>mcp6453 <mcp6453@earthlink.net> writes:
>>>
>>>
>>>>I had a domain located on a shared server that was giving us
>>>>problems. We moved it to a new company, that is great. The problem is,
>>>>even though I changed the DNS to the new company several months ago
>>>>and disabled the account on the old server, about 1 in 20 emails is
>>>>still going to the old server. How can that happen? What are some DNS
>>>>servers not updated? Do I have to delete rather than disable the
>>>>account on the old server?
>>>
>>>Are, by chance the emails that are getting misdirected coming from
>>>folks that are also customers of the old hosting company? I noted
>>>this effect when I switched hosts. The reason it happens is
>>>that from the same server/provider, the mail server thinks the DNS
>>>records at the old company are authoritative because the mail server
>>>doesn't go out to the internet to check otherwise.
>>>The only fix is to have the domain purged from the old company's DNS
>>>records. That way, when the old company mail server goes to deliver
>>>@yourdomain.com the resolver will have to go to the root servers and
>>>they'll point it to the right DNS records, correct new IP and send
>>>your mail to the right place. Best Regards,
>>
>>
>>Actually, some of the problems are caused by this reason, I just
>>discovered. There are several more that I am trying to uncover, but
>>you're right on the money.
>>
>>Thanks for all for the advice!
>
>
> w00t!
>
> Best Regards,

Actually, ALL of the problems were caused by this reason. I had no idea
that the problem sender was on the same shared server! Now it all makes
sense. Now, if someone could tell me why suspending an account in cPanel
does not suspend the account...