We switched ISP's. The new one is in a different country although the
domain name has remained the same. Normally, they say it can take up to
3 days for the new DNS Primary domain to update throughout the Internt.
It's been about a week now and for the most part, this update has taken
place.

Here is the order of events that took place (the real domain names have
been replaced):

1. We used 1 ISP for 2 domains: domain1.com and domain2.com. Both are
located in Israel. Both domains used the same mail server.

2. We move domain1.com to the USA and have it hosted by an ISP there.

3. The DNS update on the Internet happens quite fast but we wait about
a week for the new DNS Primary address to propagate throughout the
Internet.

4. People can send and receive e-mail on both domains to and from
anyone with one exception: if an e-mail is sent from the mail server on
domain2.com to domain1.com, it never arrives and no message is sent
from any mail server indicating any problem. Some people in Israel can
send an e-mail to domain1.com or domain2.com and it arrives. If someone
in Israel is using a different ISP, then their DNS is probably correct.
If they are using the same ISP, it is possible that there are multiple
DNS servers and the one they are using happens to be updated.

It would then logically appear that the mail server on domain2.com is
forwarding the e-mail not to the new ISP but has an old cached DNS on
its system somewhere.

Does this make sense? Is it possible from my computer to run a program
of some sort to determine where the e-mail is ending up at when sent
through the mail server on domain2.com? In other words, is it possible
to find out somehow (from my own computer) if the old DNS Primary name
is still being used by the domain2.com mail server?

Thanks for your insight

Hi
Assuming that you're using exchange you can trace the mails sent and
received through message traking center under tools (in exchange manager).

First thing to do is check if your exchange is resolving correctly the MX
records.
- Nslookup <press enter>
- Server ipserver <press enter>
- Set Type=MX <press enter>
- domain.tld <press enter>

if everything ok, start the SMTP test is some tools tha you can use
Email/SMTP Test Utility
http://www.zoneedit.com/smtp.html
How To Test SMTP Services Manually in Windows Server 2003
http://support.microsoft.com/kb/323350/
*if you're using ISA with mail relay check this link :Configuring an Inbound
and Outbound SMTP Relay to Complement ISA 2004 Firewall Protection for
Exchange Servers
http://www.isaserver.org/articles/sm...doutbound.html
--
I hope that the information above s you
Good Luck

Jorge Silva
MCSA
Systems Administrator

"Polaris431" <polaris431@gmail.com> wrote in message
news:1162390113.137338.217110@m7g2000cwm.googlegro ups.com...
> We switched ISP's. The new one is in a different country although the
> domain name has remained the same. Normally, they say it can take up to
> 3 days for the new DNS Primary domain to update throughout the Internt.
> It's been about a week now and for the most part, this update has taken
> place.
>
> Here is the order of events that took place (the real domain names have
> been replaced):
>
> 1. We used 1 ISP for 2 domains: domain1.com and domain2.com. Both are
> located in Israel. Both domains used the same mail server.
>
> 2. We move domain1.com to the USA and have it hosted by an ISP there.
>
> 3. The DNS update on the Internet happens quite fast but we wait about
> a week for the new DNS Primary address to propagate throughout the
> Internet.
>
> 4. People can send and receive e-mail on both domains to and from
> anyone with one exception: if an e-mail is sent from the mail server on
> domain2.com to domain1.com, it never arrives and no message is sent
> from any mail server indicating any problem. Some people in Israel can
> send an e-mail to domain1.com or domain2.com and it arrives. If someone
> in Israel is using a different ISP, then their DNS is probably correct.
> If they are using the same ISP, it is possible that there are multiple
> DNS servers and the one they are using happens to be updated.
>
> It would then logically appear that the mail server on domain2.com is
> forwarding the e-mail not to the new ISP but has an old cached DNS on
> its system somewhere.
>
> Does this make sense? Is it possible from my computer to run a program
> of some sort to determine where the e-mail is ending up at when sent
> through the mail server on domain2.com? In other words, is it possible
> to find out somehow (from my own computer) if the old DNS Primary name
> is still being used by the domain2.com mail server?
>
> Thanks for your insight
>

Email servers are notorious for holding on to what was once a valid IP, in
their own DNS cache, long after the TTL has expired and the server's OS has
discarded the values from its DNS cache. Of course this isn't RFC compliant,
but it could definitely save time on a very busy email server. So event
though it usually takes [much] less than three days for DNS changes to
propagate, not all email will check for these changes.

My experience is that this is more common in older email servers, but
there's no hard statistics on it. So, when ever I encounter a problem
receiving email after an IP address change, I first check the logs on my
email server to verify that the sender's server isn't connecting and failing
to deliver for some other reason. Then I contact the IT staff of the sender
email server and ask them to manually populate the server's DNS cache (the
management console of many email servers allow you to perform manual DNS
queries). And if that doesn't work, I ask them to restart their email
server. If they have a user complaining about not be able to send out an
important email, there's usually no arguments.


"Polaris431" <polaris431@gmail.com> wrote in message
news:1162390113.137338.217110@m7g2000cwm.googlegro ups.com...
> We switched ISP's. The new one is in a different country although the
> domain name has remained the same. Normally, they say it can take up to
> 3 days for the new DNS Primary domain to update throughout the Internt.
> It's been about a week now and for the most part, this update has taken
> place.
>
> Here is the order of events that took place (the real domain names have
> been replaced):
>
> 1. We used 1 ISP for 2 domains: domain1.com and domain2.com. Both are
> located in Israel. Both domains used the same mail server.
>
> 2. We move domain1.com to the USA and have it hosted by an ISP there.
>
> 3. The DNS update on the Internet happens quite fast but we wait about
> a week for the new DNS Primary address to propagate throughout the
> Internet.
>
> 4. People can send and receive e-mail on both domains to and from
> anyone with one exception: if an e-mail is sent from the mail server on
> domain2.com to domain1.com, it never arrives and no message is sent
> from any mail server indicating any problem. Some people in Israel can
> send an e-mail to domain1.com or domain2.com and it arrives. If someone
> in Israel is using a different ISP, then their DNS is probably correct.
> If they are using the same ISP, it is possible that there are multiple
> DNS servers and the one they are using happens to be updated.
>
> It would then logically appear that the mail server on domain2.com is
> forwarding the e-mail not to the new ISP but has an old cached DNS on
> its system somewhere.
>
> Does this make sense? Is it possible from my computer to run a program
> of some sort to determine where the e-mail is ending up at when sent
> through the mail server on domain2.com? In other words, is it possible
> to find out somehow (from my own computer) if the old DNS Primary name
> is still being used by the domain2.com mail server?
>
> Thanks for your insight
>

Check to make sure the ISP in Israel removed domain1.com from their
nameservers.

I would venture a guess that people in domain2.com are using the Israel
ISP's nameservers to resolve domain1.com. If this domain still exists on
the ISP's nameservers with old information, then I think you'll find that
the people in domain1.com will be able to read all the lost emails by
logging in to their old email server.

You can test this by running a query against the Israel ISP's name servers,
checking the A record associated with the mail server for domain1.com. If
it provides the old IP address, then this is the problem.
--
Greg Lindsay [MSFT]

Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

"Polaris431" <polaris431@gmail.com> wrote in message
news:1162390113.137338.217110@m7g2000cwm.googlegro ups.com...
> We switched ISP's. The new one is in a different country although the
> domain name has remained the same. Normally, they say it can take up to
> 3 days for the new DNS Primary domain to update throughout the Internt.
> It's been about a week now and for the most part, this update has taken
> place.
>
> Here is the order of events that took place (the real domain names have
> been replaced):
>
> 1. We used 1 ISP for 2 domains: domain1.com and domain2.com. Both are
> located in Israel. Both domains used the same mail server.
>
> 2. We move domain1.com to the USA and have it hosted by an ISP there.
>
> 3. The DNS update on the Internet happens quite fast but we wait about
> a week for the new DNS Primary address to propagate throughout the
> Internet.
>
> 4. People can send and receive e-mail on both domains to and from
> anyone with one exception: if an e-mail is sent from the mail server on
> domain2.com to domain1.com, it never arrives and no message is sent
> from any mail server indicating any problem. Some people in Israel can
> send an e-mail to domain1.com or domain2.com and it arrives. If someone
> in Israel is using a different ISP, then their DNS is probably correct.
> If they are using the same ISP, it is possible that there are multiple
> DNS servers and the one they are using happens to be updated.
>
> It would then logically appear that the mail server on domain2.com is
> forwarding the e-mail not to the new ISP but has an old cached DNS on
> its system somewhere.
>
> Does this make sense? Is it possible from my computer to run a program
> of some sort to determine where the e-mail is ending up at when sent
> through the mail server on domain2.com? In other words, is it possible
> to find out somehow (from my own computer) if the old DNS Primary name
> is still being used by the domain2.com mail server?
>
> Thanks for your insight
>

Sorry, I forgot to include how to check the A record. Find out the IP
address of the authoritative DNS server for domain2.com (the Israel ISP's
DNS server). Pretend for now that this is 10.10.10.10, and that your mail
server's host name is mail.domain1.com.

nslookup <enter>
server 10.10.10.10 <enter>
mail.domain1.com <enter>

Try the same thing using the new ISP's name server IP address. If you don't
get the same result, then the Israel ISP needs to remove domain1.com from
their DNS server.

--
Greg Lindsay [MSFT]

Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

"Greg Lindsay [MSFT]" <greglin@microsoft.com> wrote in message
news:OKSjK8f$GHA.4348@TK2MSFTNGP04.phx.gbl...
> Check to make sure the ISP in Israel removed domain1.com from their
> nameservers.
>
> I would venture a guess that people in domain2.com are using the Israel
> ISP's nameservers to resolve domain1.com. If this domain still exists on
> the ISP's nameservers with old information, then I think you'll find that
> the people in domain1.com will be able to read all the lost emails by
> logging in to their old email server.
>
> You can test this by running a query against the Israel ISP's name
> servers, checking the A record associated with the mail server for
> domain1.com. If it provides the old IP address, then this is the problem.
> --
> Greg Lindsay [MSFT]
>
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
>
> "Polaris431" <polaris431@gmail.com> wrote in message
> news:1162390113.137338.217110@m7g2000cwm.googlegro ups.com...
>> We switched ISP's. The new one is in a different country although the
>> domain name has remained the same. Normally, they say it can take up to
>> 3 days for the new DNS Primary domain to update throughout the Internt.
>> It's been about a week now and for the most part, this update has taken
>> place.
>>
>> Here is the order of events that took place (the real domain names have
>> been replaced):
>>
>> 1. We used 1 ISP for 2 domains: domain1.com and domain2.com. Both are
>> located in Israel. Both domains used the same mail server.
>>
>> 2. We move domain1.com to the USA and have it hosted by an ISP there.
>>
>> 3. The DNS update on the Internet happens quite fast but we wait about
>> a week for the new DNS Primary address to propagate throughout the
>> Internet.
>>
>> 4. People can send and receive e-mail on both domains to and from
>> anyone with one exception: if an e-mail is sent from the mail server on
>> domain2.com to domain1.com, it never arrives and no message is sent
>> from any mail server indicating any problem. Some people in Israel can
>> send an e-mail to domain1.com or domain2.com and it arrives. If someone
>> in Israel is using a different ISP, then their DNS is probably correct.
>> If they are using the same ISP, it is possible that there are multiple
>> DNS servers and the one they are using happens to be updated.
>>
>> It would then logically appear that the mail server on domain2.com is
>> forwarding the e-mail not to the new ISP but has an old cached DNS on
>> its system somewhere.
>>
>> Does this make sense? Is it possible from my computer to run a program
>> of some sort to determine where the e-mail is ending up at when sent
>> through the mail server on domain2.com? In other words, is it possible
>> to find out somehow (from my own computer) if the old DNS Primary name
>> is still being used by the domain2.com mail server?
>>
>> Thanks for your insight
>>
>
>