Re: Outside recipients cannot reply

That is a real mixed bag kind of question....my pat answer is 3 days. Check
out your DNS settings are DNSREPORT.com Like i said, I usuall drop the
refresh intervals down to 3 hours or so, and let that bake out before I
change the MX. IT is not foolproof, however, as some MTA's cache DNS on
their own schedules.....


"Derek" <Derek@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:56BF3F4A-F1C6-4EC3-ABEB-4C4510720B97@xxxxxxxxxxxxxxxx
> The MX records are currently pointing to the ISP and they can still accept
> mail.
>
> I want to avoid disruptions in email delivery. This is why I am thinking
> of
> waiting. Do you have any idea what the max/min potential downtime is for
> email delivery?
>
> "Tom Felts" wrote:
>
>> Where are the MX records pointing currently? To the ISP? Can they still
>> accept mail?
>>
>> We usually don't flip MX records until a week-end, and we 'pre-stage' the
>> event by lowering the SOA refresh intervals. But in your case, I would
>> be
>> tempted to bite the bullet and just do it. Of course there may be
>> mitigating reasons why you don't want to do that...
>>
>>
>> "Derek" <Derek@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:018F72E6-06AA-46BC-9797-DA4955EC0239@xxxxxxxxxxxxxxxx
>> >I have just installed a new SBS2003 and we are using exchange server.
>> >We
>> >are
>> > still using an outside ISP for incoming email and I have setup the POP3
>> > external connector to recieve all email. That is working fine.
>> > I can send mail out and receive mail in just fine. However, if I send
>> > something to someone outside our organization, they get an
>> > undeliverable
>> > message when trying to reply.
>> >
>> > I know that this problem can be solved by changing my DNS/MX records to
>> > point to my new server, but I don't want to do that quite yet due to
>> > down
>> > times for propogation.
>> >
>> > Are there any short-term fixes for this problem? Should I not be
>> > worried
>> > about the propagation time and just do the DNS record changes?
>> >
>> > Thanks in advance!
>>
>>
>>


.

Relevant Pages

  • Re: SMTPSVC Event ID: 2012 and 2013
    ... I'm having exactly the same problem but I'm also having email delivery ... "By default Windows 2003 uses UDP for DNS queries. ... Two windows server 2003, one being the DC (with DNS Server) and the other ...
    (microsoft.public.exchange.admin)
  • Re: user unknown issue with "domain.com" but not "www.domain.com"
    ... I'm not even sure how to query DNS to see what record ... only  anewperspective.com has MX record in DNS with another hosts server ... declared for email delivery ... your sendmail delivers both addresses to different destinations ...
    (comp.mail.sendmail)
  • Re: Exchange 2003 taking wrong DNS record
    ... See if you have the July DNS vulnerability patches. ... (#5.7.1 smtp;550 5.7.1 Unable to relay) ... with email delivery to a couple of domains. ... is this an exchange ...
    (microsoft.public.exchange.admin)
  • Re: Exchange 2003 taking wrong DNS record
    ... Actually that patch "might" be the source of the problem. ... See if you have the July DNS vulnerability patches. ... with email delivery to a couple of domains. ... is this an exchange ...
    (microsoft.public.exchange.admin)
  • Re: Exchange - multiple relay?
    ... I want to change the way I send mail from a forward to ISP to DNS. ... Your firewall does not need to be listening for an incoming port 25 connection for outgoing mail. ... keeping your exchange box inaccessible from the ...
    (microsoft.public.windows.server.sbs)
Loading