• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 446
  • Last Modified:

Domain Vs. Domain.Local

I use DFS on my windows 2008 R2 network. I redirect people's My Documents folder to a domain-based DFS share. The share is \\Domain.local\share

When I redirect users in group policy to \\domain\share (without the .local) it works perfectly fine with no problems. However, if I change this in group policy to \\domain.local\share which is the actual name of the share, users get a warning when trying to open My Documents that says "This page has an unspecified potential security risk. Would you like to continue?"

I've done some research and found some references saying the "domain.local" needs to be added to trusted sites. But why? It is the name of the domain. The clients are members of the domain already. Why would it need to be added? My guess is that I have something else configured incorrectly somewhere with DNS or something like that.

Any suggestions?
1 Solution
Domain is the NetBIOS name.  Domain.local is the FQDN.  The FQDN is controlled by DNS and would need to be added to the trusted sites in IE.  The NetBIOS name would be controlled by WINS (If you use it...if not, it's the Browser service/broadcast to find the name).

If you've unchecked "Automatically Detect Intranet Network" in the Internet Settings then your local domain won't be considered "Safe."  You can either check this or add the domain.local to one of the trusted sites.

Local Intranet

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

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