|
-
DNS, routing, smtp??? HELP
Heres what happened. Before i came on board someone setup exchange.. that
person left the company when we moved from San Franciso and moved to Miami.
Now we're trying upgrade all of our systems to enterprise sytems with some
sort of infastructure.
So we have all of our new machines co-located. We (my colleauges and I) are
stumped on this one fact as we are not exchange admins
Our old server machine.ntdomain is -> companymail01.company
Our new Server machine.ntdomain is -> commail.company-pdc-dom
dns for the old one is -> mail.company.com
DNS for the new is -> mail.city.company.com
our website www.company.com is located at another facility and has nothing
in common with the others aside from OS platform
We planned on sending out a corporate email to change to the new email service
at a specified date. but my question is when do we shutdown the original,
how does one who emails form an outside company resolve email: in other words
how does an emailt to user@company.com form user@another-company.com get
to our server.. how does it know to now go to the server located at mail.city.company.com
and not mail.company.com. One would think that the suffix would now be mail.city.company.com,
however company.com works sending out and sending to self (in test cases).
Is this how smtp works, am i way off, should i just continue as nothing is
wrong? I already exported and recreated all the aproriate accounts. Is a
vpn needed more advanced DNS? I'm going nuts or am i
Thanks in advanced
Signed
stuck being an Exchange admin till the new guy gets hired
Joshua Goodstein
-
Re: DNS, routing, smtp??? HELP
You need to change the mx records in dns to point to the new mail server,
and make sure you have the old email addresses added to each users mailbox.
that way if someone sends email to the old address the new server will receive
it.
check out the exchange faq for more info
http://www.exchangefaq.com
"Joshua Goodstein" <awing_pilot@yahoo.com> wrote:
>
>Heres what happened. Before i came on board someone setup exchange.. that
>person left the company when we moved from San Franciso and moved to Miami.
>Now we're trying upgrade all of our systems to enterprise sytems with some
>sort of infastructure.
>So we have all of our new machines co-located. We (my colleauges and I)
are
>stumped on this one fact as we are not exchange admins
>
>
>Our old server machine.ntdomain is -> companymail01.company
>Our new Server machine.ntdomain is -> commail.company-pdc-dom
>
>dns for the old one is -> mail.company.com
>DNS for the new is -> mail.city.company.com
>
>our website www.company.com is located at another facility and has nothing
>in common with the others aside from OS platform
>
>We planned on sending out a corporate email to change to the new email service
>at a specified date. but my question is when do we shutdown the original,
>how does one who emails form an outside company resolve email: in other
words
>how does an emailt to user@company.com form user@another-company.com get
>to our server.. how does it know to now go to the server located at mail.city.company.com
>and not mail.company.com. One would think that the suffix would now be mail.city.company.com,
>however company.com works sending out and sending to self (in test cases).
>Is this how smtp works, am i way off, should i just continue as nothing
is
>wrong? I already exported and recreated all the aproriate accounts. Is a
>vpn needed more advanced DNS? I'm going nuts or am i
>
>Thanks in advanced
>Signed
>stuck being an Exchange admin till the new guy gets hired
>
>Joshua Goodstein
-
Re: DNS, routing, smtp??? HELP
Thanks I got it now !!!! Dns can be fun for everyone!!!! ;-)
"Simon Coleman" <simon.coleman@rs.com.au> wrote:
>
>You need to change the mx records in dns to point to the new mail server,
>and make sure you have the old email addresses added to each users mailbox.
>
>that way if someone sends email to the old address the new server will receive
>it.
>
>check out the exchange faq for more info
>
>http://www.exchangefaq.com
>
>
>"Joshua Goodstein" <awing_pilot@yahoo.com> wrote:
>>
>>Heres what happened. Before i came on board someone setup exchange.. that
>>person left the company when we moved from San Franciso and moved to Miami.
>>Now we're trying upgrade all of our systems to enterprise sytems with some
>>sort of infastructure.
>>So we have all of our new machines co-located. We (my colleauges and I)
>are
>>stumped on this one fact as we are not exchange admins
>>
>>
>>Our old server machine.ntdomain is -> companymail01.company
>>Our new Server machine.ntdomain is -> commail.company-pdc-dom
>>
>>dns for the old one is -> mail.company.com
>>DNS for the new is -> mail.city.company.com
>>
>>our website www.company.com is located at another facility and has nothing
>>in common with the others aside from OS platform
>>
>>We planned on sending out a corporate email to change to the new email
service
>>at a specified date. but my question is when do we shutdown the original,
>>how does one who emails form an outside company resolve email: in other
>words
>>how does an emailt to user@company.com form user@another-company.com get
>>to our server.. how does it know to now go to the server located at mail.city.company.com
>>and not mail.company.com. One would think that the suffix would now be
mail.city.company.com,
>>however company.com works sending out and sending to self (in test cases).
>>Is this how smtp works, am i way off, should i just continue as nothing
>is
>>wrong? I already exported and recreated all the aproriate accounts. Is
a
>>vpn needed more advanced DNS? I'm going nuts or am i
>>
>>Thanks in advanced
>>Signed
>>stuck being an Exchange admin till the new guy gets hired
>>
>>Joshua Goodstein
>
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
Forum Rules
|
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL
|
Bookmarks