[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 395
  • Last Modified:

Local domain TLD is .com

Hi, I have recently started working for a new client on their local network.

I have since found the local domain TLD is .com

I personally use .local for local networks which is the commonly used method I know

They have been experiencing some speed issues, whilst I recognise this TLD issue may be causing some issues I know it is not the only problem they have

My question is:

Is there a simplified method for changing the TLD in the domain without the need for a major re-shuffle.

There are only 8 PC's on the network so it would not be totally out of the question to reinstall the whole network but if this can be avoided then it would be preferable as they have a few 3rd party software packages which can be a pain

If i added domain.com to DNS so it looked locally, what issues would this bring when they try to access their URL on the net. They have a website under the same domain.TLD hosted externally

0
digitechit
Asked:
digitechit
3 Solutions
 
CoccoBillCommented:
If the domain forest is in Windows 2003 Native Mode, renaming the domain is possible:
http://www.petri.co.il/windows_2003_domain_rename.htm

However, I would rather recommend just starting from scratch to avoid any possible problems.

It is of course possible to keep your current configuration, the main problem will be like you said connecting to the external web site from internal clients. The easiest way to fix this is to add the external sites as separate records for the internal clients. For example, for the external www.domain.com you could create an A host record of extweb.domain.com that points to the external address, and instruct your users to connect to extweb instead of www. If you have several external hosts you could create a separate zone for them, such as domain.ext and create all the A records inside it.

Here's some additional reading:
http://technet2.microsoft.com/WindowsServer/en/Library/7f6df44c-06c3-4b92-ba32-63d895a7924b1033.mspx
0
 
jar3817Commented:
There is nothing wrong with using a real domain name for your active directory unless you don't actually own that domain. I use a subdomain of my companies real domain name for active directory. The only possible way this could be affecting speed is if your dns structure isn't set up correctly. CoccoBill already posted about how to set that up.

0
 
brwwigginsCommented:
I agree, there is really only one issue that i've ever run into with running a .com in your active directory and that has to do with people using an intranet site of http://domain.com instead of http://www.domain.com because the domain.com resolves to the domain controllers.

Other than that, if the DNS is setup properly you should not notice a difference in speed
0
 
digitechitAuthor Commented:
Hi, and thank you for your replies. I will wrap this up very shortly.

0
 
digitechitAuthor Commented:
Thanks for your reply and apologies for not finishing this post earlier all answers received and all relevant. Info gladly received Thx

Andy
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now