Question about using .LOCAL and .COM

[Kyle Burns]

I originally posted this inquiry on the Exchange connectivity newsgroup, but
in retrospect this is probably a much more appropriate forum so I apologize
in advance to those who subscribe to both for the cross post (post to
microsoft.public.exchange2000.connectivity follows):


I came here looking for the answer to basically the same question and, after
reading the linked article, still do not have a complete picture of what I
need to do. I've decided to try my hand at hosting my own mail services at
home and am not sure if I'm completely on the right track. To date, I've
done the following:

1) Installed Windows 2000 Server and configured it as an Active Directory DC
for "mydomain.local"
2) Installed Exchange 2000
3) Placed my order for DSL service with 5 static IP addresses

I've been told by SBC that I will be managing my own DNS. I'm familiar with
creating records in DNS, but am not 100% sure of what I have to initially do
as the source of the records. I _think_ that what I have left to do is:

1) Add a Primary Forward Zone in DNS manager using "mydomain.com"
2) Add host records pointing to public IP addresses that I choose to use for
mail.mydomain.com and www.mydomain.com
3) Add an MX record pointing to mail.mydomain.com
4) Change my default recipient policy to reflect the "mydomain.com" address
for SMTP

Am I on the right track here? I have a couple of weeks before my DSL is in
place, so I can go so far as to start over from scratch if necessary. I
just want to make sure I get it right. If I need to step back and start
over, I will have the following items at my disposal:

- (1) Cayman 3546 DSL Modem/Router (I plan on using NAT)
- (1) HP NetServer LC II Server (I can use multiple NICs if necessary)
- (1) D-Link DI-614+ Wireless Router (what I'm currently using for my cable
modem)
- (1) MSDN Universal Subscription

If I'm not already on the right path, can someone provide some guidance?

Thanks in advance



"Lanwench [MVP - Exchange]"

 

[Herb Martin]

1) Installed Windows 2000 Server and configured it as an Active Directory
DC

for "mydomain.local"
2) Installed Exchange 2000
3) Placed my order for DSL service with 5 static IP addresses

I've been told by SBC that I will be managing my own DNS. I'm familiar with
creating records in DNS, but am not 100% sure of what I have to initially do
as the source of the records. I _think_ that what I have left to do is:

It's a poor policy to manage your own EXTERNAL DNS unless you have
a rather large company and a significant reason. Let the REGISTRAR do it.
Register with someone like Register.com (or move to them) and let their
24/7 fault tolerant servers do the job.

You still get to enter the (usually very small number of) external records
so
you retain complete control of the actual zone data.

1) Add a Primary Forward Zone in DNS manager using "mydomain.com"
2) Add host records pointing to public IP addresses that I choose to use for
mail.mydomain.com and www.mydomain.com
3) Add an MX record pointing to mail.mydomain.com

Maybe not. SBC will have the REVERSE and you need to find out
what (or ask them to set the) name they will use for you IP addresses in
the reverse zone.

What REVERSE will you Email servers IP use? That's where the MX for
mydomain.com needs to point --> might be mail.mydomain.com or it might
be something like SBC17824.mydomain.com or it might even be:
dsl-200.10.5.1.sbc.com (or some other combo.)

4) Change my default recipient policy to reflect the "mydomain.com" address
for SMTP

Yes, but you are back to exchange stuff again. (Not pure DNS.)

Am I on the right track here? I have a couple of weeks before my DSL is in
place, so I can go so far as to start over from scratch if necessary. I
just want to make sure I get it right. If I need to step back and start
over, I will have the following items at my disposal:

Figure out the IP they will give you. Get the OWNER of the IP (SBC) to
create the reverse record using EITHER their "standard pattern" or your
desired name -- which is largely irrelevant, but you must KNOW that
name.

This is the name you TELL you SMTP server to "act as". When it contacts
another SMTP server for SENDING email it will report this name, while the
IP address part of the send/receive headers in the packet. The recipient
email server will (typically) try to confirm you are who you say you are by
doing a "reverse on the IP" to determine it is WHO you claimed to be.

Note this has NOTHING (or almost nothing) to do with receiving email.
A single such email server might receive email for dozens or even hundreds
of clients domains/zones, but it can only claim to be one machine in one of
those zones -- or even in an unrelated zone.

- (1) Cayman 3546 DSL Modem/Router (I plan on using NAT)
- (1) HP NetServer LC II Server (I can use multiple NICs if necessary)
- (1) D-Link DI-614+ Wireless Router (what I'm currently using for my cable
modem)
- (1) MSDN Universal Subscription

If I'm not already on the right path, can someone provide some guidance?

You are confusing receiving email with sending it.

--
Herb Martin

I originally posted this inquiry on the Exchange connectivity newsgroup, but
in retrospect this is probably a much more appropriate forum so I apologize
in advance to those who subscribe to both for the cross post (post to
microsoft.public.exchange2000.connectivity follows):


I came here looking for the answer to basically the same question and, after
reading the linked article, still do not have a complete picture of what I
need to do. I've decided to try my hand at hosting my own mail services at
home and am not sure if I'm completely on the right track. To date, I've
done the following:

1) Installed Windows 2000 Server and configured it as an Active Directory DC
for "mydomain.local"
2) Installed Exchange 2000
3) Placed my order for DSL service with 5 static IP addresses

I've been told by SBC that I will be managing my own DNS. I'm familiar with
creating records in DNS, but am not 100% sure of what I have to initially do
as the source of the records. I _think_ that what I have left to do is:

1) Add a Primary Forward Zone in DNS manager using "mydomain.com"
2) Add host records pointing to public IP addresses that I choose to use for
mail.mydomain.com and www.mydomain.com
3) Add an MX record pointing to mail.mydomain.com
4) Change my default recipient policy to reflect the "mydomain.com" address
for SMTP

Am I on the right track here? I have a couple of weeks before my DSL is in
place, so I can go so far as to start over from scratch if necessary. I
just want to make sure I get it right. If I need to step back and start
over, I will have the following items at my disposal:

- (1) Cayman 3546 DSL Modem/Router (I plan on using NAT)
- (1) HP NetServer LC II Server (I can use multiple NICs if necessary)
- (1) D-Link DI-614+ Wireless Router (what I'm currently using for my cable
modem)
- (1) MSDN Universal Subscription

If I'm not already on the right path, can someone provide some guidance?

Thanks in advance



"Lanwench [MVP - Exchange]"

See http://www.msexchange.org/tutorials/MF002.html - you can get rid of the
.local domain in your recipient policy if you wish, and use only the true
.com domain - at the very least, you need to define the .com domain as the
primary/default reply domain.

 

[Kyle Burns]

Herb,
I'm glad I asked! I've had my domain name for three years and didn't
realize that it wasn't necessary for the company hosting my site to manage
the DNS. I checked out my options for having the registrar (network
solutions) manage the DNS and will use that service. That out of the way,
it looks like all that's really left in regards to being able to
successfully exchange mail will be to take care of the reverse issue that
you raised with SBC. Thanks for setting me straight.

1) Installed Windows 2000 Server and configured it as an Active

Directory

DC
for "mydomain.local"
2) Installed Exchange 2000
3) Placed my order for DSL service with 5 static IP addresses

I've been told by SBC that I will be managing my own DNS. I'm familiar with
creating records in DNS, but am not 100% sure of what I have to

initially

do
as the source of the records. I _think_ that what I have left to do is:

It's a poor policy to manage your own EXTERNAL DNS unless you have
a rather large company and a significant reason. Let the REGISTRAR do it.
Register with someone like Register.com (or move to them) and let their
24/7 fault tolerant servers do the job.

You still get to enter the (usually very small number of) external records
so
you retain complete control of the actual zone data.

1) Add a Primary Forward Zone in DNS manager using "mydomain.com"
2) Add host records pointing to public IP addresses that I choose to use for
mail.mydomain.com and www.mydomain.com
3) Add an MX record pointing to mail.mydomain.com

Maybe not. SBC will have the REVERSE and you need to find out
what (or ask them to set the) name they will use for you IP addresses in
the reverse zone.

What REVERSE will you Email servers IP use? That's where the MX for
mydomain.com needs to point --> might be mail.mydomain.com or it might
be something like SBC17824.mydomain.com or it might even be:
dsl-200.10.5.1.sbc.com (or some other combo.)

4) Change my default recipient policy to reflect the "mydomain.com" address
for SMTP

Yes, but you are back to exchange stuff again. (Not pure DNS.)

Am I on the right track here? I have a couple of weeks before my DSL is in
place, so I can go so far as to start over from scratch if necessary. I
just want to make sure I get it right. If I need to step back and start
over, I will have the following items at my disposal:

Figure out the IP they will give you. Get the OWNER of the IP (SBC) to
create the reverse record using EITHER their "standard pattern" or your
desired name -- which is largely irrelevant, but you must KNOW that
name.

This is the name you TELL you SMTP server to "act as". When it contacts
another SMTP server for SENDING email it will report this name, while the
IP address part of the send/receive headers in the packet. The recipient
email server will (typically) try to confirm you are who you say you are by
doing a "reverse on the IP" to determine it is WHO you claimed to be.

Note this has NOTHING (or almost nothing) to do with receiving email.
A single such email server might receive email for dozens or even hundreds
of clients domains/zones, but it can only claim to be one machine in one of
those zones -- or even in an unrelated zone.

- (1) Cayman 3546 DSL Modem/Router (I plan on using NAT)
- (1) HP NetServer LC II Server (I can use multiple NICs if necessary)
- (1) D-Link DI-614+ Wireless Router (what I'm currently using for my cable
modem)
- (1) MSDN Universal Subscription

If I'm not already on the right path, can someone provide some guidance?

You are confusing receiving email with sending it.

--
Herb Martin

I originally posted this inquiry on the Exchange connectivity newsgroup, but
in retrospect this is probably a much more appropriate forum so I apologize
in advance to those who subscribe to both for the cross post (post to
microsoft.public.exchange2000.connectivity follows):


I came here looking for the answer to basically the same question and, after
reading the linked article, still do not have a complete picture of what I
need to do. I've decided to try my hand at hosting my own mail services at
home and am not sure if I'm completely on the right track. To date, I've
done the following:

1) Installed Windows 2000 Server and configured it as an Active

Directory

DC
for "mydomain.local"
2) Installed Exchange 2000
3) Placed my order for DSL service with 5 static IP addresses

I've been told by SBC that I will be managing my own DNS. I'm familiar with
creating records in DNS, but am not 100% sure of what I have to

initially

do
as the source of the records. I _think_ that what I have left to do is:

1) Add a Primary Forward Zone in DNS manager using "mydomain.com"
2) Add host records pointing to public IP addresses that I choose to use for
mail.mydomain.com and www.mydomain.com
3) Add an MX record pointing to mail.mydomain.com
4) Change my default recipient policy to reflect the "mydomain.com" address
for SMTP

Am I on the right track here? I have a couple of weeks before my DSL is in
place, so I can go so far as to start over from scratch if necessary. I
just want to make sure I get it right. If I need to step back and start
over, I will have the following items at my disposal:

- (1) Cayman 3546 DSL Modem/Router (I plan on using NAT)
- (1) HP NetServer LC II Server (I can use multiple NICs if necessary)
- (1) D-Link DI-614+ Wireless Router (what I'm currently using for my cable
modem)
- (1) MSDN Universal Subscription

If I'm not already on the right path, can someone provide some guidance?

Thanks in advance



"Lanwench [MVP - Exchange]"

See http://www.msexchange.org/tutorials/MF002.html - you can get rid

of
the

.local domain in your recipient policy if you wish, and use only the true
.com domain - at the very least, you need to define the .com domain as the
primary/default reply domain.

Mark Jansen wrote:
Is there a way that the Exchange 2000 within a
company.local domain be able to send and receive emails
with a registered company.com domain? How could the DNS
server with the company.local domain name be configured
so it could function for Internet use, even if it is on
company.local host name?

 

[Herb Martin]

Herb,
I'm glad I asked! I've had my domain name for three years and didn't
realize that it wasn't necessary for the company hosting my site to manage
the DNS. I checked out my options for having the registrar (network
solutions) manage the DNS and will use that service. That out of the way,
it looks like all that's really left in regards to being able to
successfully exchange mail will be to take care of the reverse issue that
you raised with SBC. Thanks for setting me straight.

Sure man, took me years to work all this out. Not because it is hard but
because there really was no one convenient to ask then.

I am actually amazed at how well my MS DNS has worked all these years
considering how little I knew when I started. (Good defaults, good GUI,
I'm logical, AND I got lucky A LOT. <grin>)

--
Herb Martin

Directory familiar
with initially is:

It's a poor policy to manage your own EXTERNAL DNS unless you have
a rather large company and a significant reason. Let the REGISTRAR do it.
Register with someone like Register.com (or move to them) and let their
24/7 fault tolerant servers do the job.

You still get to enter the (usually very small number of) external records
so
you retain complete control of the actual zone data.
use
for

Maybe not. SBC will have the REVERSE and you need to find out
what (or ask them to set the) name they will use for you IP addresses in
the reverse zone.

What REVERSE will you Email servers IP use? That's where the MX for
mydomain.com needs to point --> might be mail.mydomain.com or it might
be something like SBC17824.mydomain.com or it might even be:
dsl-200.10.5.1.sbc.com (or some other combo.)



Yes, but you are back to exchange stuff again. (Not pure DNS.)

is
in

Figure out the IP they will give you. Get the OWNER of the IP (SBC) to
create the reverse record using EITHER their "standard pattern" or your
desired name -- which is largely irrelevant, but you must KNOW that
name.

This is the name you TELL you SMTP server to "act as". When it contacts
another SMTP server for SENDING email it will report this name, while the
IP address part of the send/receive headers in the packet. The recipient
email server will (typically) try to confirm you are who you say you are by
doing a "reverse on the IP" to determine it is WHO you claimed to be.

Note this has NOTHING (or almost nothing) to do with receiving email.
A single such email server might receive email for dozens or even hundreds
of clients domains/zones, but it can only claim to be one machine in one of
those zones -- or even in an unrelated zone.
guidance?

You are confusing receiving email with sending it.

what

I

need to do. I've decided to try my hand at hosting my own mail

services
at

home and am not sure if I'm completely on the right track. To date, I've
done the following:

1) Installed Windows 2000 Server and configured it as an Active

Directory

DC
for "mydomain.local"
2) Installed Exchange 2000
3) Placed my order for DSL service with 5 static IP addresses

I've been told by SBC that I will be managing my own DNS. I'm

familiar
with

creating records in DNS, but am not 100% sure of what I have to

initially

do
as the source of the records. I _think_ that what I have left to do is:

1) Add a Primary Forward Zone in DNS manager using "mydomain.com"
2) Add host records pointing to public IP addresses that I choose to

use
for

mail.mydomain.com and www.mydomain.com
3) Add an MX record pointing to mail.mydomain.com
4) Change my default recipient policy to reflect the "mydomain.com" address
for SMTP

Am I on the right track here? I have a couple of weeks before my DSL

is
in

place, so I can go so far as to start over from scratch if necessary. I
just want to make sure I get it right. If I need to step back and start
over, I will have the following items at my disposal:

- (1) Cayman 3546 DSL Modem/Router (I plan on using NAT)
- (1) HP NetServer LC II Server (I can use multiple NICs if necessary)
- (1) D-Link DI-614+ Wireless Router (what I'm currently using for my cable
modem)
- (1) MSDN Universal Subscription

If I'm not already on the right path, can someone provide some guidance?

Thanks in advance



"Lanwench [MVP - Exchange]"
See http://www.msexchange.org/tutorials/MF002.html - you can get rid of
the
.local domain in your recipient policy if you wish, and use only the true
.com domain - at the very least, you need to define the .com domain

as
the

primary/default reply domain.

Mark Jansen wrote:
Is there a way that the Exchange 2000 within a
company.local domain be able to send and receive emails
with a registered company.com domain? How could the DNS
server with the company.local domain name be configured
so it could function for Internet use, even if it is on
company.local host name?