Due to criminal activities of some users, the zones dnsupdate.info and urown.cloud are offline.
Their current owner will not continue offering these zones for dyndns purposes.
Deleted more abusive hosts that overloaded the database.
Do not send updates if your IP did not change,
use a well-behaved updater software that complies to the specs,
check if your updaters authenticate correctly (check the host view),
do not run multiple updaters for same host entry,
do not use a cronjob and wget or curl,
do not put private network IPs into public DNS.
Updated code to current master branch.
Killed some abusive hosts and user accounts.
I reduced the session cookie lifetime from 14d (Django default) to 10h to reduce the amount of active sessions.
Improved protection against spammers: crap email addresses are not accepted at registration time any more.
Legitimate users of this service: please give a valid, working e-mail address (we won't give it to any 3rd party and won't use it except to send you service-related notifications). Non-working e-mail addresses fill up my postmaster inbox due to the bounces they produce, are a daily annoyance and are thus considered abusive use of the service.
There is an issue with updating zones that have IPv4 name servers.
To get it solved quickly, please enter the IPv6 addresses of your name servers.
See there if you only have IPv4 name servers.
You also need to set your domain to "available" again after fixing this.
We also fixed an issue with the cron jobs.
They are now disabled on the old server and enabled on the new server.
Moved nsupdate.info to new server, upgraded to Python 3.
In case there are any issues, please report them on github.
Did a code and dependencies update (latest github master).
In case there are any issues, please report them on github.
Did a cleanup on the users/hosts/domains, removing all for-sure stale items.
Also vacuumed the database - much cleaner now.
Got rid of some abusers of the service: I deleted quite some hosts and users of the service that did not comply with fair use of the service
(some distributed malware, some were spamming the service with lots of hosts
and users (botnets?), some hid behind one-time email addresses that cause
issues for the service's notification emails).
If your account / your host belonged to that group:
sorry for the inconvenience, but you are not welcome here.
While doing that, I maybe deleted some legitimate hosts accidentally,
especially since the whole domain awsmppl.com looked abusive and I removed it
If you did not abuse the service and I killed your account / host:
I am very sorry about that, but I can't check each case individually.
Just recreate it and try to not look spammy / mass-created / illegal or
Upgraded code to latest github master. Upgraded dependencies.
Enabled donations, see link in the footer. If you like nsupdate.info, please donate!
TLS / SSL: Switched from the problematic StartSSL certificate to a Let's Encrypt certificate.
Long time no changes, but today the nsupdate.info software got an upgrade to current git master code (0.12pre) with a lot of bug fixes. For details, see the change log on github. If anything is misbehaving, file bugs there, please.
Sorry, today the service was extremely slow (up to unusable). I tried to debug the issue for quite some hours (suspecting some issue on the web server / proxy / uwsgi / nsupdate.info app) until I found the issue was caused by one of our DNS servers being offline. I now disabled it and notified the operator. nsupdate.info hosts are back to normal now, nerdpol.ovh hosts are still unusable due to this - we try to fix this ASAP.
We need more active translators! Please see there for more infos!
0.11 is nearly release-ready. Just translations missing...
Upgraded to 0.11dev
Did a host staleness check.
If your host was not updated for a long time (> 300 days), you may have
received an email that you should please update its IP. This is a new
cleanup procedure that should avoid that we have growing numbers of
unused/outdated hosts in the database. If you got such an email, just
follow the included instructions.
Some of these mails bounced because the email address in the user account
was invalid - I assumed that if the email is invalid AND the host has not
been updated for long that likely account and host are not used any more
and deleted them. If this was a wrong assumption please excuse me and just
recreate your account and host (and please give a [permanently] working
email address this time so that we can contact you in case of problems -
we won't give your email address to anybody and only use it for emails
related to this service).
Added a domain check cron job. If you have a domain (not: host) configured
with the service, we check whether the nameserver you gave really answers
queries for that domain (and is reachable). If not, you'll get a notification
via email pointing out this problem and how to solve it.
We somehow got the impression that some of you confused hosts and domains
and did not really want to add a domain, but rather a host. If that was the
case for you, please remove the unneeded / not working domains.
Updated to 0.10dev to give it some practical testing.
Updated to 0.9.1 to fix security issue.
Added Twitter as a way to log in. They still have no IPv6.
Fixed firewall, so google-oauth2 works again.
Upgraded nsupdate.info site to 0.9.0dev - please test the new "Related Hosts" feature (see host settings) if you have IPv6 (or a public IPv4 network with more than 1 IP). Check if the netmask/prefix length is correct.
Also upgraded all the dependencies to latest versions.
If you encounter bugs, please file bug reports on github.
Released nsupdate.info 0.8.0.
Began work on nsupdate.info 0.9.0 features (IPv6 improvements).
We need more translators, see documentation!
Released nsupdate.info 0.7.0.
Began work on nsupdate.info 0.8.0 features (UI improvements, internal API changes, bug fixes).
Upgraded production site to 0.8.0dev code.
Updated translations: de, fr, it
Changed "abuse" policy: if you send way too many no-change updates (e.g.
by using a dumb cronjob with wget/curl instead of a sane update client like
e.g. ddclient), the system will set the abuse flag for your host saturday
morning at 03:00. The cronjob will now only run once a week (was: nightly)
so no-change update "peaks" while setting up a new host / experimenting with
a new update client should be no problem.
Speed up the cronjob by 100x, "database is locked" failure solved that way.
Some other small improvements / fixes.
Fixed google-oauth2 login.
Somehow this was malfunctioning due to a change either on google's side
or in the social auth library we use. I enabled the google+ service in
the google developer console and it started working again.
Moved a long-running cronjob from 02:50 UTC to 08:50 UTC.
The cronjob that flags abusers and resets the client fault counters runs
rather long, so I moved it to a time when I suspect less dyndns2 updates
are coming in.
Fixed a bug in the cron jobs, they work now. If you "abuse" the service
(== update your host frequently even if your IP did not change, e.g. by
a cron job with wget or curl), your host will get flagged as abusive
and will not get updated any more.
You can reset the flag on the web UI, but you should only do that after
switching to a well-behaved update client, e.g. ddclient or python-dyndnsc,
otherwise it will get flagged as abusive again and again.
Hopefully fixed issue #140 - please test and give feedback.
Upgraded all dependencies to current versions.
Added site-specific notes to the footer to document some stuff that people
need to know (and that is site-specific, not software-specific).
Upgraded software to current repo code.
You can delete IP v4 and v6 addresses of hosts now.