Upgraded the site's code and also removed the non-working remote account login buttons.
No new account registrations for now (too many requests to process manually).
2023-04-12:
Set abuse flag for some hosts with permanent authentication issues. Please re-configure your update secret and stop running badly configured updaters.
nerdpol.ovh DNS zone transferred to new nameservers.
2021-11-08:
Custom domains with IPv4 name servers are broken right now, see the updated site notes.
2021-04-08:
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.
2019-04-15:
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.
2018-10-18:
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.
2018-05-02:
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.
2017-07-28:
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
completely.
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
otherwise abusive.
2017-01-20:
Enabled donations, see link in the footer. If you like nsupdate.info, please donate!
2015-01-26:
We need more active translators! Please see there for more infos!
2014-11-21:
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).
2014-11-16:
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.
2014-10-01:
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.
2014-05-30:
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.
2014-01-26:
Added site-specific notes to the footer to document some stuff that people
need to know (and that is site-specific, not software-specific).
