dyndns reliability

[CootesNest]

I implemented an he.net dyndns update for my domain a couple of weeks ago as my isp had broken my static IPs.

After a couple of days, my domain stopped resolving correctly and went back to an IP address that was in use about a week before, even though the GUI showed that the correct records were in place (somewhere).  After a few hours (I did not measure this), the resolution started to work again.

Is this common behaviour and if so, is it likely that I've made a fundamental mistake in the updating process or similar (I was using curl on a 5 min cycle).

tia
tc

[passport123]

I have been using HE's dyndns for a few years.  The service has been very reliable for me.  I have never had an IP address revert as you did.


The only time I ever had an issue occurred when I was testing my update script, and I was running it a few times within a short period of time.  I got back an error message indicating that I was making too many changes.  Outside of that test scenario, I have never had an issue with it. 

I use it to maintain one IPv4 and two IPv6 addresses.