Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Thursday, May 22, 2014 10:04 PM
Hello,
I have SharePoint sites with fully qualified domain name (FQDN). I have DNS and SharePoint configured to access sites with the FQDN links. I work in an organization with users who have logins in different domains, SharePoint servers are in different domains, and users who connect to the SharePoint externally. So, the FQDN links used for SharePoint sites works great in getting users connected. However, some users enter sites with no FQDN, i.e http://sharepointsite v.s. http://sharepointsite.domain.com, and some of the SharePoint features do not work or they may not be able to connect to sites.
The problem is that users have short-cuts or favorites or hyper-links with links that are non-FQDN.
In my alternative access mappings, I have both settings for non-FQDN and FQDN, like http://server and http://server.domain.com, but this does not help. The public URL zone is the FQDN and the site collection is the FQDN URL.
Is there a way for DNS to add the domain.com automatically to web links, if they don't have them? Anything I can do differently in SharePoint?
Paul
Friday, May 23, 2014 6:39 PM ✅Answered
If you book mark the complete URL and trying to browse it then sharePoint is unable to redirect it to FQDN...
Yes, it is normal and you write your own custom solution for this or IIS level redirection etc.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog
Friday, May 23, 2014 3:38 AM
check my reply here.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog
Friday, May 23, 2014 5:11 PM
I actually posted that question on that site.
In the alternative access mappings, I tried adding a http://site as in Internal URLs in the default zone and SharePoint would not take it. I tried adding the URL in the intranet zone and SharePoint said it was already added.
So, this did not work.
DNS settings are:
Alias (CNAME) = sharepointsite
Fully Qualified Domain Name (FQDN) = sharepointsite.domain.com
Fully Qualified Domain Name (FQDN) for target host = server.domain.com
When I type in sharepiontsite in IE address bar, it will revert to http://sharepointsite.domain.com. So, that is working, but the URL is not converted to a FQDN with a full address, like http://sharepointsite/project/default.aspx
I am still stuck. Any other suggestions?
Paul
Friday, May 23, 2014 5:55 PM
this typical behavior when you use AAM for redirection. You need to use rewrite url method.
http://johnliu.net/blog/2010/7/23/sharepoint-2010-with-iis-url-rewrite-20.html
http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=48
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog
Friday, May 23, 2014 6:33 PM
So, what I am seeing is normal behavior with SharePoint? So, I need a third-party product or customization for non-FQDN to be converted to FQDN?
Paul
Friday, March 25, 2016 2:45 PM
_________________________________________
This worked in my 2013 environment.
Create two Alternate Access Mappings. One for http://sharepointname.domain.com as the Intranet Zone and the other http://sharepointname as the Custom Zone.
Now users get the same content from either http://sharepointname/subiste/page or http://sharepointname.domain.com/subiste/page
__________________________________________