none
Hostnamed Site Collection URL

    Question

  • Hi

    Using Server 2012R2, SQL 2012, SharePoint Server 2013:

    Ive created a Web Application without host header http://portal.contoso.com

    Is it possible to create hostnamed site collections for the above web application without FQDN (I want a short URL without domain name)?

    Like:
    http://intranet

    Instead of a FQDN:
    http://intranet.contoso.com
    ?

    The DNS A-record would be the same in the site collections above.
    Though even if i only specify the short URL in the new-spsite, the site will only respond to the FQDN URL.

    Brgs

    Bjørn


    Sunday, April 02, 2017 7:46 PM

Answers

  • Sorry this was my bad. I realize i put in the wrong description.

    The DNS I created was:
    intranet.cool (http://intranet.cool.contoso.com)

    And I was setting my HNSC URL to:
    http://intranet.cool

    But intranet.cool is not pingable, and so this URL will not work on a SharePoint HNSC. URL has to be pingable to work.

    So our solution was to have the DNS entry:
    intranet instead of intranet.cool 

    brgs

    Bjørn

    Wednesday, April 05, 2017 12:55 PM

All replies

  • Hi Bjørn,

    Yes, you can do like that to create the host named site collection.

    Best Regards,

    Victoria

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com


    Monday, April 03, 2017 5:51 AM
    Moderator
  • Thank you Victoria for the reply.

    What am i doing wrong ?

    In DNS A-record i plot in 

    My HNSC is http://Intranet (Created though PowerShell)

    But site only answers to http://Intranet.contoso.com

    Brgs

    Bjørn 


    Monday, April 03, 2017 6:29 AM
  • Is the workstation you are using to access the site also in the contoso.com domain?  If not, that is your problem.  Using a netbios only host name to access a site still uses the FQDN for IP resolution.  It just appends the default domain of the workstation to the end of the shortname when querying DNS.  So if your workstation is something like workstation.acme.com and you try to reach http://intranet what you are actually trying to browse is http://intranet.acme.com and not http://intranet.contoso.com.

    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

    Monday, April 03, 2017 11:24 AM
  • Assuming you are in the same domain, also edit bindings and alternate access mapping.
    Monday, April 03, 2017 4:20 PM
  • Sorry this was my bad. I realize i put in the wrong description.

    The DNS I created was:
    intranet.cool (http://intranet.cool.contoso.com)

    And I was setting my HNSC URL to:
    http://intranet.cool

    But intranet.cool is not pingable, and so this URL will not work on a SharePoint HNSC. URL has to be pingable to work.

    So our solution was to have the DNS entry:
    intranet instead of intranet.cool 

    brgs

    Bjørn

    Wednesday, April 05, 2017 12:55 PM