Replicate MX record

  • Thread starter Thread starter Daniel Tan
  • Start date Start date
D

Daniel Tan

Is it possible that when i change to a new MX record, it may replicate
to other dns servers when they are trying to resolve my mx address ?
Thanks.

Regards,
Daniel
 
You mean your domain's public MX record? That info should get propagated
throughout the Internet on its own.
 
Yes. My domain MX record should be on other DNS server caches or in
their zone once they resolved my MX record ?

Regards,
Daniel
 
In
posted their thoughts said:
Yes. My domain MX record should be on other DNS server caches or in
their zone once they resolved my MX record ?

Regards,
Daniel

"Lanwench [MVP - Exchange]"
You mean your domain's public MX record? That info should get
propagated
throughout the Internet on its own.

You mean your own internal DNS servers? Internally, they won't need your MX
records, since MX records are for other mail servers out on the Internet to
find your mail server for your domain. Internally, your clients, MAPI, IMAP,
HTTP or POP3 clients won't need that record. They just connect directly to
the mail service and retrieve mail based on their protocols.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Ace No i mean external DNS server

Ace Fekay said:
In
posted their thoughts said:
Yes. My domain MX record should be on other DNS server caches or in
their zone once they resolved my MX record ?

Regards,
Daniel

"Lanwench [MVP - Exchange]"
You mean your domain's public MX record? That info should get
propagated
throughout the Internet on its own.

Daniel Tan wrote:
Is it possible that when i change to a new MX record, it may
replicate
to other dns servers when they are trying to resolve my mx address
?
Thanks.

Regards,
Daniel

You mean your own internal DNS servers? Internally, they won't need your MX
records, since MX records are for other mail servers out on the Internet to
find your mail server for your domain. Internally, your clients, MAPI, IMAP,
HTTP or POP3 clients won't need that record. They just connect directly to
the mail service and retrieve mail based on their protocols.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Hi, Daniel - I'd pick up a basic DNS book if you want to understand how it
works. It isn't anything to do with your MX record specifically, it's more
about propagation of your domain's DNS info to other servers...
 
In
posted their thoughts said:
Ace No i mean external DNS server

"Ace Fekay [MVP]"
In Daniel Tan <[email protected]>, posted their thoughts, then I
offered my
thoughts down below:
Yes. My domain MX record should be on other DNS server caches or in
their zone once they resolved my MX record ?

Regards,
Daniel

"Lanwench [MVP - Exchange]"
message You mean your domain's public MX record? That info should get
propagated
throughout the Internet on its own.

Daniel Tan wrote:
Is it possible that when i change to a new MX record, it may
replicate
to other dns servers when they are trying to resolve my mx address
?
Thanks.

Regards,
Daniel

You mean your own internal DNS servers? Internally, they won't need
your MX
records, since MX records are for other mail servers out on the
Internet to
find your mail server for your domain. Internally, your clients,
MAPI, IMAP,
HTTP or POP3 clients won't need that record. They just connect
directly to
the mail service and retrieve mail based on their protocols.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

If you're DNS is hosting your external name, and you have an MX record, then
I don't see why it would cache that, since the server itself will never ask
for it and won't cache it's own records (what it's authorative for), since
they exist in the zone. When other DNS servers query it, then it will be
cached in THEIR cache since they had to perform an iterative query to find
it.

Is this what you mean?
Make sense?


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In Lanwench [MVP - Exchange]
posted their said:
Hi, Daniel - I'd pick up a basic DNS book if you want to understand
how it works. It isn't anything to do with your MX record
specifically, it's more about propagation of your domain's DNS info
to other servers...

That's right. I agree with you and Jonathan. There is no "replication"
happening at all. As other servers query for any records, they will cache
them once they get an answer. That's pretty much the propogation. And when
someone changes a hostname server record at the registrar, the old record,
having been cached on some servers already queryied the older record, would
have to expire the TTL before it will re-query for the new one, so that can
take anywhere between 24 to 72 hours (shorter or longer, depending).

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Ace, recently i often get the NDR email undeliverable message with
.....20 delivery attempt. Could it because the mx record being changed
or expired ? I send email with outlook but i can log on to the
website. any ideas ?

Regards,
Daniel

Ace Fekay said:
In Lanwench [MVP - Exchange]
posted their said:
Hi, Daniel - I'd pick up a basic DNS book if you want to understand
how it works. It isn't anything to do with your MX record
specifically, it's more about propagation of your domain's DNS info
to other servers...

That's right. I agree with you and Jonathan. There is no "replication"
happening at all. As other servers query for any records, they will cache
them once they get an answer. That's pretty much the propogation. And when
someone changes a hostname server record at the registrar, the old record,
having been cached on some servers already queryied the older record, would
have to expire the TTL before it will re-query for the new one, so that can
take anywhere between 24 to 72 hours (shorter or longer, depending).

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In
Daniel Tan said:
Ace, recently i often get the NDR email undeliverable message with
....20 delivery attempt. Could it because the mx record being changed
or expired ? I send email with outlook but i can log on to the
website. any ideas ?

Regards,
Daniel

The MX record is only important for Other mail servers on the Internet to
find YOUR mail server for your domain. It would have nothing to do with a
client sending mail. The NDRs just say that your mail server could not find
the mail server for the domain of that the mail's recipeint address.

Sending mail and to find the mail server for that domain, YOUR mail server
will just do a simple MX query for that mail server of that domain. Once
found, then it resolves the IP thru another DNS lookup, then it connects
with the other mail server, then it checks the recipient, then if the
recipient is found, it will send it. Pretty simple, eh? That's pretty much
all it does in the background.

What email recipient are you trying to send mail to?

If your MX record is messed up, then no one in your domain will receive
mail. Is that what's going on? What's the actual NDR message say? Does it
say can't find the mail server or that the recipient doesn't exist? Is this
to another domain or to your own email address in your domain?


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Ace, the NDR message i get is Subject " Undeliverable message " ,
content is email domain cannot be found after 20 delivery attempts.
Then it bounds back to my email. If i use another ISP to send to this
email server then it is ok.


Regards,
Daniel
 
Back
Top