BQM fault?

For some reason my BQM is all of a sudden showing 100% packet loss. The connection is definitely up and I am able to manually ping the address yet BQM shows as solid red. Any ideas?

EDIT: I am monitoring using a dynamic dns host name, out of curiosity I set up another monitor using the IP address only and that seems to be working. While the one using the host name is still showing 100% packet loss. Maybe a DNS issue with BQM.

Edited by quadrophenic (Thu 09-Jan-20 08:19:43)

Have you tried doing a standard ping of the DNS address? Have you confirmed the DNS is pointing to the correct IP?

Yes, ping from an external PC to the hostname resolves correctly and receives a response.

But what about an external ping to your actual IP address?

In reply to a post by RobertoS:

But what about an external ping to your actual IP address?

External ping to the ip address is fine. BQM is working when using the ip address. Only the BQM using the hostname is not working.

Summary:
BQM to hostname - 100% packet loss
BQM to IP address - working and responding
External manual ping from PC to hostname - resolves correctly and receives a response
External manual ping from PC to IP address - working and responding

Are you using an Asus router with the free asus DDNS by chance? That seems to have problems with resolution since the change of the year. (I moved to a different DDNS provider).

No, it is a No-ip account. It was working fine until Tuesday around 1am.

In reply to a post by quadrophenic:

No, it is a No-ip account. It was working fine until Tuesday around 1am.

Have you tried pinging by name from an outside website that is different to Thinkbroadband?

This site is interesting, just found it by Google:
https://www.dotcom-tools.com/ping-test.aspx

Yes i have tried using this site f8lure.mouselike.org and it is working fine.
After I proved this to be working I went back to thinkbroadband and disabled the monitor and left it for half an hour and restarted it. Miraculously it started working again!

I had already tried this but I left it a little longer this time.

Thanks all for the input

Perhaps the site caches the DNS lookup so that it doesn't keep hitting DNS servers, stopping and restarting it later might have cleared that cache.