Legacy.domain.com DNS record for Exchange

If I understand Legacy.domain.com should exist in the Internal and public DNS servers.
So, how does Exchange CAS server know where to redirect the user request (to legacy.domain.com IP in public or internal DNS) ?

Thanks
jskfanAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Simon Butler (Sembee)Connect With a Mentor ConsultantCommented:
That is correct. You would have two legacy DNS records becaues you need it to work both internally and externally.

Exchange literally says the mailbox isn't here, go here instead.

Simon.
0
 
Simon Butler (Sembee)Connect With a Mentor ConsultantCommented:
As I wrote in your other question, Exchange doesn't do the DNS lookup at all. It is the client that does it. All Exchange does it tell the client that the mailbox can be located at legacy.example.com instead and then it is up to the client browser to find that location.

Simon.
0
 
jskfanAuthor Commented:
<<All Exchange does it tell the client that the mailbox can be located at legacy.example.com >>

how does Exchange respond to the client ? how does Exchange tell the client "your mailbox can be located at legacy.domain.com".
The reason I am asking is there are 2 legacy.domain.com records, one in internal DNS and one in External DNS.
0
 
jskfanAuthor Commented:
Thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.