Dyndns - Hostname blocked due to abuse
-
Hi Guys,
I'm on the latest 2.0-BETA4 (i386) built on Wed Nov 24 04:23:54 EST 2010 (nanobsd 2g). This problem of dyndns abuse was not there before my last firmware upgrade which was about 20 days back. So I read another thread on the subject which was for pfsense version 1.2.3 and it seems to be mostly a cronetab related issue.
I think my copy of pfsense updates dyndns every hour as per the crontab file below:
PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin HOME=/var/log #minute hour mday month wday who command # # # pfSense specific crontab entries # Created: November 24, 2010, 5:47 pm # 0 * * * * root /usr/bin/nice -n20 newsyslog 1,31 0-5 * * * root /usr/bin/nice -n20 adjkerntz -a 1 3 1 * * root /usr/bin/nice -n20 /etc/rc.update_bogons.sh */60 * * * * root /usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 sshlockout 1 1 * * * root /usr/bin/nice -n20 /etc/rc.dyndns.update */60 * * * * root /usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 virusprot # # If possible do not add items to this file manually. # If you do so, this file must be terminated with a blank line (e.g. new line) #I tried to do a manual edit the dydndns update to:
59 23 * * * root /usr/bin/nice -n20 /etc/rc.dyndns.update
but could not save it as it says its a read only system file. Any suggestions how to solve the issue ?
I've been locked out of the dyndns twice, not wanna land blocking it for the 3rd time and risking my account.
thanks.
-
according to your crontab,
dyndns is set to update at 1:01 AM, every day, every month.
if it were set to run every hour, it would look like this:
- 1 * * * root /usr/bin/nice -n20 /etc/rc.dyndns.update
as for editing crontab, install the Cron package and edit from the GUI.
crontab specifically says the file should not be edited manually, and from what i can see, you have not
"terminated [the file] with a blank line (e.g. new line)"also, log in as root via SSH, and not "admin" to edit files owned by root.
-
Install the cron package to edit cron jobs. You edit them in the config, not in the crontab file.
DynDNS update happens when your WAN IP changes. If you are being locked out for too many changes, I'd really be looking at why your WAN connection is changing IPs so frequently.
The DynDNS code will not issue an update request if the IP stays the same, unless 24 hours has passed.
