said by mjf:DYNSITE has updated my dynamic IP address twice now. So it appears to be working now.
The built-in DDNS client in my Netopia router has never stopped working with the DynDNS service. The problem is that the DSLR monitors no longer seem to be able to work with a DynDNS hostname. I have reset it to stop using the "static IP" status that it got after the site restore, and several days later after it was obvious that did not work, I deleted that monitor and created a new one (which still does not work).
Here is proof that the DynDNS hostname is resolving and that it is pingable:
C:\>nslookup windcrest.dyndns-office.com
Server: dcs-srv.dcs-net
Address: 192.168.9.2
Non-authoritative answer:
Name: windcrest.dyndns-office.com
Address: 98.87.57.78
C:\>ping windcrest.dyndns-office.com
Pinging windcrest.dyndns-office.com [98.87.57.78] with 32 bytes of data:
Reply from 98.87.57.78: bytes=32 time=52ms TTL=238
Reply from 98.87.57.78: bytes=32 time=53ms TTL=238
Reply from 98.87.57.78: bytes=32 time=52ms TTL=238
Reply from 98.87.57.78: bytes=32 time=54ms TTL=238
Ping statistics for 98.87.57.78:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 54ms, Average = 52ms
About 30 minutes ago I manually entered the current IP address into the line monitor setup, and that works, but it would be a PITA to try to keep up with the frequent IP address changes on that particular (somewhat unstable) DSL circuit.