Actions
Forum Thread Details
  • Replies 59 replies
  • Subscribers 64 subscribers
  • Views 2201 views
  • Users 0 members are here
Related

URL response Fail!

stevesmythe

I can't connect to the server this morning. It fails with code "error" : "0". It has worked every other day I have tried (53 so far!).

Parents

  • It's not only you ... I'm having trouble too. I suspect they probably have an issue with their server, routing or DNS.

     

    - Gough

  • in reply to Gough Lui

    The problem in my tracing seems to be an NXDOMAIN returned for avnetagent.iotconnect.io

     

    It seems that some servers can still resolve it, whereas others cannot.

    image

     

    Result is:

    13.77.82.141

    173.201.188.161

     

    Perhaps shoving it into your HOSTS file could temporarily overcome the issue.

     

    EDIT: Confirmed, adding the binding of 13.77.82.141 avnetagent.iotconnect.io into my HOSTS file, flushing DNS resolver cache (ipconfig /flushdns) and restarting the app allowed it to submit correctly.

     

    - Gough

  • in reply to Gough Lui

    - any chance you guys can look into why your DNS servers aren't reliably propagating?

     

    - Gough

  • in reply to Gough Lui

    I added 13.77.82.141 avnetagent.iotconnect.io into hosts, flushed the DNS resolver cache and restarted the app. The url is resolving correctly but can't be reached. I also tried 173.201.188.161. It seems I have a different problem.

     

    image

  • in reply to stevesmythe

    I don't believe that you can ping the address - the server at 13.77.82.141 there doesn't seem to respond to pings, but the one at 173.201.188.161 does.

     

    I suspect perhaps a firewall or un-cooperative ISP/router? Perhaps worth trying a tracert to each server and seeing where the trail ends. For me, it seems that my traffic (from AU) arrives at LAX then gets sent through SN, AT, BN (all MSN) before being "lost" in a sea of non-responding routers for 13.77.82.141. For the other, my traffic arrives at LAX, then goes through ASH, EQIX (GoDaddy) before ending up at one of their shared hosting/VPSes.

     

    Have you also tried restarting your router? Else if you have a VPN, you could try going through that.

     

    - Gough

  • in reply to stevesmythe

    It was working when I just changed the host file.

    But after running ipconfig /flush dns . it has stopped working, the url response fail is back.

  • in reply to cline

    Flushing DNS Cache is necessary in case there is a NXDOMAIN response cached, which will result in it failing (quickly) for a while until the entry expires. HOSTS entry should override the need to actually resolve it. Try clicking the 'Send to Server' button more than once. I suspect there may be another name which it tries to resolve that is not the one we have singled out which might explain the failure ...

     

    - Gough

Reply
  • in reply to cline

    Flushing DNS Cache is necessary in case there is a NXDOMAIN response cached, which will result in it failing (quickly) for a while until the entry expires. HOSTS entry should override the need to actually resolve it. Try clicking the 'Send to Server' button more than once. I suspect there may be another name which it tries to resolve that is not the one we have singled out which might explain the failure ...

     

    - Gough

Children
No Data