locked
WHS2011's dns updater updating IP wrongly? RRS feed

  • Question

  • Installed WHS2011 and port forwarded accordingly. Set up the remote access and added my domain.homeserver.com, detecting WAN ip correctly.

    I have been able to connect to my domain.homeserver.com, but only for at most 15 minutes a day, then connection fails for the next 12-24 hours. Whenever I am able to connect I will do a DNSlookup which will show correctly my wan ip address. Whenever I cannot connect, dnslookup will show my ISP's proxy server's IP which is variable.

    Weird thing is, with DYNDNS and NO-IP services, I can always (100%) reach my server anytime with my homeip.net and no-ip.org domains. I believe microsoft dyndns service is not updating the correct IP (although it is corectly reflected in the remote desktop setup server settings). Is the problem due to transparent proxies? No, because Dyndns's http://checkip.dyndns.com/ and http://checkip.dyndns.com:8245/ report my WAN ip address correctly. http://www.ipchecking.com/ and http://www.whatismyproxy.com/ show the HTTP_X_FORWARDED_FOR header as my WAN ip address, so no issues with the web proxy (am I right?)

    Hence I suspect microsoft's dyndns updater to live domains just hasn't been updating my wan ip address correctly most of the time, although it has been updating correctly occasionally.

    Any ideas?





    • Edited by wonderous Friday, March 9, 2012 5:01 PM
    Friday, January 13, 2012 1:26 AM

All replies

  • In a Command Prompt run "nslookup xxx.homeserver.com" and compare the resultant IP address with your router WAN IP - they should be the same if DNS is working.

     


    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.
    Friday, January 13, 2012 2:16 AM
  • Hi Phil I have answered above, the nslookup reports the same wan IP occasionally, but a isp proxy most of the time..


    Bass and treble are inseparable. Music sounds bad with either absent. The same applies to us The Oh Brothers.

    Friday, March 9, 2012 5:03 PM
  • A proxy server sits between your WAN connection and the Internet at large; ISPs sometimes use them to reduce traffic over their own upstream connection to the Internet. Unfortunately, a proxy server is very likely to cause exactly the issue you describe above. About all you can do is contact your ISP and ask if there is a class of service available which will eliminate the proxy server for your connection.

    I'm not on the WHS team, I just post a lot. :)

    Saturday, March 10, 2012 12:15 AM
  • Like you said it is likely to be the proxy but it is also likely that there's something different about microsoft's dyndns updater from the DYNDNS/NO-IP updaters such that the latter enables connectivity in spite of the proxy 100% of the time but the former allows it only 5% of the time.


    Bass and treble are inseparable. Music sounds bad with either absent. The same applies to us The Oh Brothers.

    Saturday, March 10, 2012 4:31 PM
  • Like you said it is likely to be the proxy but it is also likely that there's something different about microsoft's dyndns updater from the DYNDNS/NO-IP updaters such that the latter enables connectivity in spite of the proxy 100% of the time but the former allows it only 5% of the time.

    That Microsoft uses a different method for updates than DynDNS is likely to be true, but as a practical matter, getting Microsoft to change the way their dynamic DNS updater works is just not going to happen.

    I'm not on the WHS team, I just post a lot. :)

    Sunday, March 11, 2012 12:40 PM