Sal Sorice
asked on
Using an internal domain name that you do not own
Sigh. Recently setup a new 2012RS Standard Server for a client. The Server is used for basic services (file sharing, remote access, etc). Email is handled by Office365. It's a small company (5 employees - 2 local and 3 always remote).
Following recommended practices I set the internal domain to 'internal.companydomain.co m'
In one respect, my client got lucky. A BIG company paid them mucho dollars to buy the domain.
My gut instinct is to do a re-install using the new name they register. They want to know if we can just leave it as is and adjust as needed for the new domain (remote access. etc.).
Makes me a bit uneasy to keep the old domain - afraid there might be DNS issues down the road.
Any potential pitfalls, like the external clients having DNS issues, etc.? Should I follow my instincts and insist that we do a reinstall?
Following recommended practices I set the internal domain to 'internal.companydomain.co
In one respect, my client got lucky. A BIG company paid them mucho dollars to buy the domain.
My gut instinct is to do a re-install using the new name they register. They want to know if we can just leave it as is and adjust as needed for the new domain (remote access. etc.).
Makes me a bit uneasy to keep the old domain - afraid there might be DNS issues down the road.
Any potential pitfalls, like the external clients having DNS issues, etc.? Should I follow my instincts and insist that we do a reinstall?
OK.
If you want to use domain name that someone else own on External DNS but you're absolutely sure that your users will use this domain only INSIDE, you can do it.
But You need to create Forward Lookup Zone in your local DNS and point all requests like www, FTP, etc. to local IP address.
Also you need to put all that information in server localhost file.
Any requests for external name from inside is going to be rerouted to your internal server.
All this settings will work only from inside. For outside requests you're going to be rerouted to owner of the name registered in External DNS
If you want to use domain name that someone else own on External DNS but you're absolutely sure that your users will use this domain only INSIDE, you can do it.
But You need to create Forward Lookup Zone in your local DNS and point all requests like www, FTP, etc. to local IP address.
Also you need to put all that information in server localhost file.
Any requests for external name from inside is going to be rerouted to your internal server.
All this settings will work only from inside. For outside requests you're going to be rerouted to owner of the name registered in External DNS
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks all for the comments so far. I'm leaning towards re-install but will wait a bit longer to see if any other comments are posted.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks all for the comments. My client decided that, even though they probably could leave it as is, always (locally) logging into a domain they don't was not in their long term best interests. Going to have to do a reinstall.
But if you want to make it fresh, this is always a wise idea to have domain name suffix with .local or .int. If you have so much patience and you want to have everything with new domain, go for fresh forest.