acrocat
asked on
FQDN for local network
I am setting up a home network, that also has the ability for people to VPN into.
I am toying between having the server (running LDAP / Samba, etc.) being named:
myname.mydomain.local
or myname.mycomain.com
What are the pros and cons of using a "dot com" domain name vs a .local?
I am toying between having the server (running LDAP / Samba, etc.) being named:
myname.mydomain.local
or myname.mycomain.com
What are the pros and cons of using a "dot com" domain name vs a .local?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Darius Ghassem
This has been an ongoing debate which is better. I think both ways are fine but my preference is to install the AD in with a .com because of less configuration in a small network. Now if you are going starting a large config then running with any top extenison might be a good idea.
Hello
I just wonder why you have so many open questions? Does experts here answer's your question well? Please try to check on, if there are comments fits the way you wanted too.
Anyway.
You can setup a home network, if is local, then just use any extension you wanted too.
But if you want your network to go merge on the internet, then you must select an extension, and that can maybe .com or .net.
So you will have yourname.net and is that is available upon purchase.
However there are free domain and is called third level domain.
These third level domains eq: yourname.therewebsite.com,
An example of this is free website is: http://www.freewebspace.com/
So you can have: http://yourname.freewebspace.com
But you can buy a domain, that you would have yournameyouwant.net or .com or .org or you can select the extension that is available on the domain provider.
Hope that helps!
Great is our GOD.
:)
rionroc
I just wonder why you have so many open questions? Does experts here answer's your question well? Please try to check on, if there are comments fits the way you wanted too.
Anyway.
You can setup a home network, if is local, then just use any extension you wanted too.
But if you want your network to go merge on the internet, then you must select an extension, and that can maybe .com or .net.
So you will have yourname.net and is that is available upon purchase.
However there are free domain and is called third level domain.
These third level domains eq: yourname.therewebsite.com,
An example of this is free website is: http://www.freewebspace.com/
So you can have: http://yourname.freewebspace.com
But you can buy a domain, that you would have yournameyouwant.net or .com or .org or you can select the extension that is available on the domain provider.
Hope that helps!
Great is our GOD.
:)
rionroc
If you own a domain, use it for your local domain even if your internet presence is hosted off site. The 'confusion' people mention with having a domain out on the internet as well as locally is easily circumvented by running named and creating a dns record there for mydomain.com, www.mydomain.com, etc while you can retain server1.mydomain.com as a local address.
That is what we do at work for some of our customers. We've named their regional office domains as region1.mydomain.com, region2.mydomain.com etc, (which aren't real, but we use them as hostnames for the linux boxes at each site for remote admin and mail routing via ldap) whilst their webservers and mail is hosted off site, which we created a record for in local DNS server and push that DNS server to clients with DHCP so users can still access them.
At the end of the day, it's your choice really. Either one you choose can be a working solution, you don't have to use mydomain.com only if you are hosting it locally.
That is what we do at work for some of our customers. We've named their regional office domains as region1.mydomain.com, region2.mydomain.com etc, (which aren't real, but we use them as hostnames for the linux boxes at each site for remote admin and mail routing via ldap) whilst their webservers and mail is hosted off site, which we created a record for in local DNS server and push that DNS server to clients with DHCP so users can still access them.
At the end of the day, it's your choice really. Either one you choose can be a working solution, you don't have to use mydomain.com only if you are hosting it locally.