none
Windows Home Server 2011 cannot propagate DNS for domain.homeserver.com for Remote Web

Answers

  • A lot of people could not figure this out and there are a lot of wrong skeptical answers from both microsoft specialists and just regular users.

    As a microsoft partner in Canada i have the fortunate exposure to multitude of environments and hardware.

    The real answer to my original questions which was discovered from testing multiple routers from the same internet connect (using Rogers Home Cable Internet).

    We tested on Juniper SSG-5 Router - Works no problem

    We tested on Linksys E1200 - Works no problem

    We tested on D-Link DIR-655 with original firmware A2 version 1.2 - failed

    Then we upgraded D-Link DIR-655 with latest firmware A2 version 1.34NA - Works no problem

    So at the end of the day, unless there is a real outage at .homeserver.com --- chances are, your router cannot do proper NAT translation to forward the DNS information to your ISP (internet provider)

    That's the real answer and real solution.


    MattLok

    • Marked as answer by mattlok Friday, June 29, 2012 2:39 AM
    Friday, June 29, 2012 2:39 AM

All replies

  • Hi,

     

    According to the problem description, this issue occurred with Windows Home Server 2011. For the Windows Home Server 2011 related issue, the best resource for you is Windows Home Server forum. The community users of Windows Home Server forum are familiar with this product. You’d better continue troubleshooting with your original post.

     

    If no clue can be found, you may also contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Windows Home Server Support Professional can assist with your request. Please be advised that contacting phone support will be a charged call.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

     

    Regards,

     

    Arthur Li

     TechNet Subscriber Support  in forum

    If you have any feedback on our support, please contact  tngfb@microsoft.com . 


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, April 27, 2011 5:58 AM
    Moderator
  • A lot of people could not figure this out and there are a lot of wrong skeptical answers from both microsoft specialists and just regular users.

    As a microsoft partner in Canada i have the fortunate exposure to multitude of environments and hardware.

    The real answer to my original questions which was discovered from testing multiple routers from the same internet connect (using Rogers Home Cable Internet).

    We tested on Juniper SSG-5 Router - Works no problem

    We tested on Linksys E1200 - Works no problem

    We tested on D-Link DIR-655 with original firmware A2 version 1.2 - failed

    Then we upgraded D-Link DIR-655 with latest firmware A2 version 1.34NA - Works no problem

    So at the end of the day, unless there is a real outage at .homeserver.com --- chances are, your router cannot do proper NAT translation to forward the DNS information to your ISP (internet provider)

    That's the real answer and real solution.


    MattLok

    • Marked as answer by mattlok Friday, June 29, 2012 2:39 AM
    Friday, June 29, 2012 2:39 AM