![]() |
|
#1
|
|||
|
|||
|
Fortunately everything on my server is still intact - files and all.
Stopped the webserver, router and modem but the defacement still exists. How do check where the 'fault' lies? ISP? EditDNS? |
|
#2
|
|||
|
|||
|
I seemed to have fixed it making corrections to two issues:
- observed that my DynDNS client wasn't updating correctly through the correct script URL which apparently had changed to http://dyndns-free.editdns.net/api/d...%&p=%password% - "Record not setup for DynDNS" - logged into EditDNS and updated IP address manually and was prompted to enter a TTL of at least 300. Also switched nameservers back and forth,, updated OpenDNS caches... How these issues MAY be relating to the earlier problem, I have no idea!
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|