asked on

I need recommendation should I configure my new domain using dot local or dot com?

I am going to install a new domain controller Windows 2012 R2 (VM) & Exchange 2013 with all the roles on another Windows 2012 R2 (VM) (I use pop3 connector to fetch emails)

I want to use RWW installed at DC & exchange through OWA externally.

Previously I used to configure myserver.mydomain.local & later change the external & internal URL at exchange to mydomain.com

I need recommendation should I configure my new domain using dot local or dot com?

SOLUTION

Manikandan Narayanswamy

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Chris H

I've always been told best practice is have different local domain than external domain for DNS sanity. You want your local doman/SRV records to share no similarities with the outside word.

SOLUTION

M A

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Akash Bansal

ASKER

I guess, best practice is updated; certificate authority no longer includes .local.

SOLUTION

Manikandan Narayanswamy

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Akash Bansal

ASKER

SOLUTION

Philip Elder

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Akash Bansal

ASKER

yes essentials & integrating exchange 2013
would buy certificate for both

I am also from SBS background.

ASKER CERTIFIED SOLUTION

Philip Elder

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Akash Bansal

ASKER

Thank you all. You all were right.

As I already have a public domain that is dedicated for this setup.
I am eliminating .local completely; I don't think it would create any issue.
As we have to buy certificates for each server, its better to use public domain only. (certificate authority won't support .local in future)
Both the servers have to be access from outside the LAN.