locked
Are there additonally supported domains beyond homeserver.com? RRS feed

  • Question

  • I'm not one to beat a dead horse, but I haven't found the answer to the specific question I have (I apologize if there already is one; I couldn't find it). I've looked through several threads -- like http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=2040938&SiteID=50 -- but they don't address the issue I have.

     

    I have been using Dynamic DNS of one flavor or another for years. Some clients I've had to run on a box (not a big deal with a dedicated WHS, I know) and some work in my router's built-in DynDNS client. However, I'm not looking for redirection like that. Let me explain why:

     

    When I installed WHS, I was less-than-exited about myserver.homeserver.com. I already had good redirection going straight to my own sub domain (at a domain I own). But I did get excited when WHS automatically generated an SSL certificate signed by "Go Daddy Secure Authentication Authority" valid for 5 years! According to http://www.godaddy.com/gdshop/ssl/ssl.asp that's worth about $90! Besides not having IE7 barf at your SSL certificate not being trusted, it makes connecting with other programs and other machines all that much easier. It also makes your friends and family feel better when you give them a URL that IE7 doesn't cry foul on.

     

    For a minute, I thought I had the solution by registering one of my domains with Windows Live Domains (http://domains.live.com). Unfortunately when I went in with my passport to change the Domain Name on WHS, it didn't appear in the drop-down. Now obviously the drop down is there for a reason. I assume that the feature was built to allow multiple domain choices, though homeserver.com is the logical choice for everyone to use. However, with both security and eventual DNS clutter on homeserver.com in mind, the ideal choice would be to allow not only subdomains on homeserver.com (and whatever else MS decides to register later... hopefully soon) but also custom domains registered with Windows Live.

     

    Now that all of that's out of the way, here's what I'm asking... can I find out:

    1. Will we be able to use something other than homeserver.com when choosing our Windows Live Custom Domain in WHS (that still generates a trusted SSL certificate)?
    2. Will we be or are we now able to use domains registered at Windows Live Domains with WHS?
    Tuesday, December 4, 2007 6:47 PM

Answers

  • There are no additional supported domain names for Windows Home Server at this time.  Here is how I deal with wanting vanity domain access to my home server...

     

     

    I use my ___.homeserver.com domain name and have the trusted cert. 

     

    I have 2 vanity domain names, one that I redirect to the default http://___/homeserver.com/home that I have customized to my liking ... and the other redirects to the remote login page. 

     

     

     

    Wednesday, December 5, 2007 9:16 PM

All replies

  • Maybe I should have asked this question in the original post: does anyone else want functionality like this? It seems like that'd be the case from some of the conversations on the forums...

     

    Tuesday, December 4, 2007 7:27 PM
  • Good questions. I believe the answer is that the SSL cert from Godaddy is only for the homeserver.com domain. The certificate doesn't even include the machine name, so it causes an error should you try to reach your server while on your local network, using a url like http://server.

    And Windows Home Server only lets you choose an address in the homeserver.com domain.
    Wednesday, December 5, 2007 1:39 AM
    Moderator
  • If you want to use a domain name other than one in the homeserver.com domain, you will have to purchase and apply a certificate yourself. That will work, assuming you know how to do so. If you decide to go that route, I suggest you get a certificate that includes the machine name, because otherwise accessing your remote access site from your premises via the URL http://server will generate a certificate error.
    Wednesday, December 5, 2007 4:50 AM
    Moderator
  • There are no additional supported domain names for Windows Home Server at this time.  Here is how I deal with wanting vanity domain access to my home server...

     

     

    I use my ___.homeserver.com domain name and have the trusted cert. 

     

    I have 2 vanity domain names, one that I redirect to the default http://___/homeserver.com/home that I have customized to my liking ... and the other redirects to the remote login page. 

     

     

     

    Wednesday, December 5, 2007 9:16 PM
  • You can always submit the idea of Vanity domains as a suggestion via Connect as explained in the Suggestions forum on this site.  Or better yet - add a vote to this suggestion

     

    https://connect.microsoft.com/WindowsHomeServer/feedback/ViewFeedback.aspx?FeedbackID=277080

     

     

    Thursday, December 6, 2007 1:02 AM
  • I'm not able to follow that link to see what I'd be voting for; can you make sure that the public has access to it?

     

    Of course I could use one of my domains to link it (with a CNAME record) but was looking for a direct solution so I didn't have to use the homeserver.com domain at all. I guess it's a moot point since there aren't current plans -- from what I can see -- to support anything else.

     

    As far as buying my own SSL certificate, I'm all too familiar with that process. Mainly I'm just looking for a way to do it for free since I was putting up with not using one in the first place!  But really I was just hoping for an answer on whether homeserver.com was about to be joined by something else in the dropdown. From what I've seen, the answer is no, not anytime soon, at least.

     

    Thanks for all of the great input.

    Thursday, December 6, 2007 4:03 PM
  •  TraekM wrote:
    Maybe I should have asked this question in the original post: does anyone else want functionality like this? It seems like that'd be the case from some of the conversations on the forums...

     

    Definitely yes. And I think it would be many of us.

    Thursday, December 6, 2007 4:14 PM
  •  Traek wrote:

    I'm not able to follow that link to see what I'd be voting for; can you make sure that the public has access to it?

    You will have to register on Connect to see that.
    Thursday, December 6, 2007 5:17 PM
    Moderator
  • My biggest fear is that using the .homeserver.com domain will make my WHS much more suseptible to attack if/when exploits become known.  A blackhat would only need to querry the entire domain to find WHS nodes.

     

    I would prefer to just use a custom domain.  Not for vanity purposes.  For security reasons.

     

    jnoel

    CISM

    Tuesday, January 15, 2008 8:44 PM
  •  

    Why the hell did I get an msn alert and e-mail regarding this thread????
    Tuesday, January 15, 2008 8:49 PM