November 3, 2016

Updates issued

Today we've installed updates to the YDNS service that fixes a few bugs, most notably one which prevented users to add domains. For the time being we have deactivated the ability to add slave domains at all, since that functionality never worked correctly. The web redirector service has gone as well. These features may come back later, but due to the lack of time we aren't able to provide a full update at this time.

July 8, 2016

Removal of the SPF record type

Starting today, it's not possible to create any new records with the SPF record type. As of April 2014, SPF records MUST be published in TXT records only (see section 3.1 of RFC 7208). Support for SPF is still available in most DNS servers, but filter software will most likely look up TXT records to find them.

Existing records are not removed, but we encourage users that make use of these record type to migrate their records to TXT pendants.

About SPF

SPF (short for Sender Policy Framework) is a open standard that's purpose is to prevent sender address forgery. It's commonly used in mail servers to verify whether a mail server is allowed to send mail on behalf of a specific domain name. More information about SPF can be found on the project's website at

April 20, 2016

Planned maintenance on May 2

We will perform a planned service maintenance on May 2, 2016 at 8:00 AM, which will affect the availability of the service.

Affected services

The following services are affected by this maintenance:
  • Website
  • API
  • Nameserver


As we have changed our hosting recently, we have to migrate our main infrastructure to a new server. YDNS is also affected: The web server (which also provides the API endpoints) and the primary nameserver ( are affected and are unavailable for up to thirty (30) minutes. We've prepared things to keep the downtime as minimal as possible.

Updates to records will not be possible during this time. Our servers will reject changes starting 8:00 AM with HTTP status code 423 (LOCKED), so we can copy the database in an consistent state to the new server. Once the service is back up, updates are accepted again.

DNS requests and answers however are not affected, as ns2 and ns3 will remain active and will answer requests appropriately. ns1 will be unavailable, and most DNS resolvers will try the next name server listed in the name server list of the specific zone.

Update: The maintenance has been completed.

March 2, 2016

Certificate updates

We replaced the SSL certificate for with a new one, issued by Let's Encrypt. All HTTP requests going to will be redirected to, except for API requests. That way, we can maintain existing updater configurations. If you have the chance to update your configuration, consider changing the endpoint host to