If BQM cached and never refreshed the DNS lookups then all the dyn DNS type services would be broken.

Stopping the pinging for a while and restarting and it then working is usually points to a router having blacklisted the BQM IP address due to the constant pinging of your IP address. Then once it stops for a period of time, the blacklist is removed.

Fair enough, sounds reasonable except that they said it worked using the IP address but not the DNS???

Edited by ian72 (Thu 09-Jan-20 17:05:52)

That would be odd in that case, as should be pinging from the same IP block on our end.

The joys of the IP world where turn off/on is still a fix

I have never needed to stop and restart it for our BT Connection when the IP changes, it normally starts working within 60 seconds.

My DDNS TTL is set to 60, seems that google gets the update about 15 seconds after the changes are made, and TBB seems to get it not long after.

I normally only get the huge RED Bar when our DNS Server decides it doesn't want to update it where I have to do it by hand, other than that its fine.

Paul

Hello there!

I too noticed the same pattern. My ddns hostname's bqm shows a thick red block. Whereas direct ip's bqm shows proper graph.

How can I make the ddns hostname's bqm to show the correct details?

Thank you!

-Gamma