locked
Can't resolve to homeserver.com RRS feed

  • Question

  • For a few weeks I can't reach my homeserver.

    When I use nslookup I get:

    C:\Users\Administrator>nslookup https://myname.homeserver.com
    Server:  mijnmodem.kpn
    Address:  192.168.2.254

    *** mijnmodem.kpn kan https://myname.homeserver.com niet vinden: Non-existent domain

    Where mijnmodem.kpn is used by my ISP to connect to my dsl-modem.

    Question is why homeserver.com resolves to this adres? My homeserver seems stable, should I contact my ISP?

    Tuesday, May 14, 2013 11:07 PM

Answers

  • nslookup doesn't require a protocol; just use myname.homeserver.com.

    Note: to learn more about most command line commands, you can type <command> /? at the command line, so for nslookup you would type nslookup /?.


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

    • Marked as answer by Ken Warren Wednesday, May 15, 2013 2:03 AM
    • Unmarked as answer by Andy Qi Tuesday, May 21, 2013 9:45 AM
    • Marked as answer by Andy Qi Tuesday, May 21, 2013 9:45 AM
    Wednesday, May 15, 2013 2:02 AM

All replies

  • Have you tried this from the Internet or just from your internal LAN?

    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.

    Tuesday, May 14, 2013 11:36 PM
  • nslookup doesn't require a protocol; just use myname.homeserver.com.

    Note: to learn more about most command line commands, you can type <command> /? at the command line, so for nslookup you would type nslookup /?.


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

    • Marked as answer by Ken Warren Wednesday, May 15, 2013 2:03 AM
    • Unmarked as answer by Andy Qi Tuesday, May 21, 2013 9:45 AM
    • Marked as answer by Andy Qi Tuesday, May 21, 2013 9:45 AM
    Wednesday, May 15, 2013 2:02 AM
  • Without the protocol nslookup workes as expected:

    C:\Users\Administrator>nslookup myname.homeserver.com
    Server:  mijnmodem.kpn
    Address:  192.168.2.254

    Niet-bindend antwoord:
    Naam:    myname.homeserver.com
    Address:  xx.xx.xx.xxx

    Why I get the first part, I don't understand but the second part seems to be the proper result.

    tracert and ping both work.

    When I connect locally to the webserver it works.

    I suspect the ISP or modem blocking the requests. Any suggestion how I can determine wihich one of the two is causing the problem?

    Wednesday, May 15, 2013 8:54 AM
  • Did a portscan and http and https requests answered by server.

    This did fit the local working web access, but not the not working internet web access.

    So I backup the config of the dsl modem, put it back to factory settings, restored the config and.... all working.

    Thursday, May 16, 2013 7:18 PM