none
Host-named site collection and My Site Host site collection is not accessible

    Question

  • Hi, to All!

    I had created application pool and one web application that is hosted in this application pool with URL http://serv.tnn-nv.com:80

    serv.tnn-nv.com is FQDN for my server.

    I had created root site collection with the same URL http://serv.tnn-nv.com This site is accessible.

    Then I created host-named site collection as described in this article "Host-named site collection architecture and deployment (SharePoint 2013)" with URL http://portal.tnn-nv.com and it's not accessible. I have "Page can not be displayed" error. Though I see it in CA SharePoint.

    And then I had created new application pool and web application for My Site host site collection, and created site collection with URL http://my.tnn-nv.com It's not accessible too.

    I think that I need something doing with DNS. But what exactly? Why my sites with URL not like FQDN is not accessible?

    Thanks a lot for all.
    Sunday, November 10, 2013 12:10 PM

Answers

  • You'll still need to create DNS records for each Site Collection when using HNSC.  Also, why are you creating >1 Web Application?  There is no need for this in HNSC (with specific exceptions), especially just for MySites.

    Did you properly create the Web Application and Site Collections with HNSC in mind?  I take it that there are no bindings on the IIS Site hosting the HNSC Web Application, correct?


    Trevor Seward, MCC

    Follow or contact me at...
      

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    • Proposed as answer by romeo doncaMVP Sunday, November 10, 2013 6:19 PM
    • Marked as answer by GrassGrasping Monday, November 11, 2013 5:23 AM
    Sunday, November 10, 2013 6:00 PM
  • Yep, not all guidance from TechNet is good guidance.  You should limit your Web Applications to as few as possible, and combining the MySite host into the Web App used for other purposes is ideal.

    As for DNS (regardless of the route you choose), you need to create an A record in DNS for the site pointing to the IP of the IIS site the Web Application is bound to.  In Active Directory, you would do this within Microsoft DNS.  Your DNS provider may be different.


    Trevor Seward, MCC

    Follow or contact me at...
      

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    • Marked as answer by GrassGrasping Monday, November 11, 2013 5:23 AM
    Monday, November 11, 2013 4:02 AM

All replies

  • You'll still need to create DNS records for each Site Collection when using HNSC.  Also, why are you creating >1 Web Application?  There is no need for this in HNSC (with specific exceptions), especially just for MySites.

    Did you properly create the Web Application and Site Collections with HNSC in mind?  I take it that there are no bindings on the IIS Site hosting the HNSC Web Application, correct?


    Trevor Seward, MCC

    Follow or contact me at...
      

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    • Proposed as answer by romeo doncaMVP Sunday, November 10, 2013 6:19 PM
    • Marked as answer by GrassGrasping Monday, November 11, 2013 5:23 AM
    Sunday, November 10, 2013 6:00 PM
  • Thanks for your answer, Romeo.

    I created Web Application for MySites because this guide "Configure My Sites in SharePoint Server 2013"   says:

    "If a My Site host site collection was created during initial deployment and configuration, we recommend that you do not use it because it was created in the default web application. Delete this site collection, and create a new web application that is dedicated to hosting My Sites. Then create a new My Site host site collection in the dedicated web application."

    I will delete Web Application for MySites. But please tell me, where exactly I must create DNS record for Site Collection? I'm not domain administrator, and I'll need to explained him what to do.

    Web Aplication and Site Collection i have created with PowerShell as in this article "Host-named site collection architecture and deployment (SharePoint 2013)".Bindings on the IIS I had created after the creation of Web Application and Site Collection.

    • Edited by GrassGrasping Monday, November 11, 2013 3:37 AM
    • Marked as answer by GrassGrasping Monday, November 11, 2013 5:23 AM
    • Unmarked as answer by GrassGrasping Monday, November 11, 2013 5:23 AM
    Monday, November 11, 2013 3:11 AM
  • Yep, not all guidance from TechNet is good guidance.  You should limit your Web Applications to as few as possible, and combining the MySite host into the Web App used for other purposes is ideal.

    As for DNS (regardless of the route you choose), you need to create an A record in DNS for the site pointing to the IP of the IIS site the Web Application is bound to.  In Active Directory, you would do this within Microsoft DNS.  Your DNS provider may be different.


    Trevor Seward, MCC

    Follow or contact me at...
      

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    • Marked as answer by GrassGrasping Monday, November 11, 2013 5:23 AM
    Monday, November 11, 2013 4:02 AM
  • Many thanks, Trevor.

    A record in DNS was created in the beginning.  And now we have created CNAME in DNS and sites became available.

    Monday, November 11, 2013 5:23 AM