YES - IT IS NOT JUST MY ISP. Why would anyone suspect that EVERYBODY'S ISP is faulty when we have disparate reports of the SAME ISSUE from around the world?
From
http://downforeveryoneorjustme.com/checkip.dyndns.org:
It's not just you! http://checkip.dyndns.org looks down from here. A sample from my spammed message log:
Oct 14 08:56:17 asusb202 ddclient[14614]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 14 09:47:03 asusb202 ddclient[14614]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 14 11:01:37 asusb202 ddclient[14614]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 14 13:04:03 asusb202 ddclient[14614]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 14 13:46:48 asusb202 ddclient[14614]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 14 16:16:06 asusb202 ddclient[14614]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 14 17:12:27 asusb202 ddclient[14614]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 14 17:35:24 asusb202 ddclient[14614]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 15 00:07:55 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 15 00:25:40 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 15 02:16:11 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 15 02:55:09 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 15 04:13:35 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 15 04:30:20 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 15 06:22:42 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 15 07:23:26 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 15 07:48:36 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 15 08:00:33 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 16 10:10:52 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 16 11:02:56 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 16 11:56:41 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 16 13:36:28 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 16 14:15:27 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 16 15:14:35 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 16 17:46:44 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 17 00:32:31 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 17 02:51:54 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 17 04:16:23 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 17 04:32:41 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 17 05:18:38 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 17 06:31:54 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 17 07:20:13 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 17 08:38:11 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 17 12:05:38 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 17 12:31:35 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 17 12:50:32 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
Oct 17 15:16:47 asusb202 ddclient[26368]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds
I've changed my '/etc/hosts' to resolve to 204.13.248.70 and it still keeps shitting the bed.
The original problem occurred with 91.198.22.70 after about 5 years of no problems of this sort with the same IP, so I'd say, yeah, the problem is on DYNDNS's side.