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

February 18, 2015

Extensive changes for the YDNS project

I've been thinking of this for some time already and made a decision that will change how the YDNS project will exist in the future. Some of you already know that YDNS was started as a small personal project, because I like to build things on my own and to see how it actually works. But YDNS grew to a level where I am not able to handle it as a one-man project anymore. Other things in my life take more and more time and even the recently launched beta test is not receiving many updates these days.

This have to change. As a result, I'm announcing that YDNS will become a open source project. The underlying source code of it's backend and front-end will be released under a liberal open source license soon. The hosting service (as provided on will stay as-is - and users of that platform don't have to worry, nothing will change there. However I'm also looking for voluntary people who'd like to join the YDNS project to improve documentation and support of the platform.

Once the transition has been completed, all donations will go directly into funding the software, as well as for the hardware running the hosting platform. If you want to get into the team, please contact me via email at

February 3, 2015

YDNS closed beta

YDNS is launching its closed beta period soon. The new version is already online at (Note: We're using a self-signed SSL certificate for the beta period). Registrations are not possible, except for people who apply for a beta invitation.

Interested users may send an email to with the Email address they'd like to use to get an invitation. Once your request has been approved, you'll be able to register using the Email address provided.

Please note that the beta is not final. We'll be doing excessive changes during the beta period to make sure that we'll ship the most reliable DNS hosting platform to date.

January 15, 2015

Last night's outage

Some of our users have noticed that YDNS was unavailable for almost 13 hours, starting on 12 p.m. this morning. This post lists all the details on what happened and what we will do to mitigate such issues in the future.

It all started with an unplanned maintenance in a data center, where we were moving some equipment and servers between racks. That also included the core infrastructure of YDNS, including the web site, database and the primary name server ( The problem here was that all secondary name servers ( and were using the database of the primary name server. While the secondary servers are on physically different locations around the globe, these servers were using the database located in the core infrastructure data center. No replication or similar techniques were used, so the loss of connectivity inevitably led to total failure of YDNS. No DNS queries - not even those to "" could be answered during the maintenance window. The maintenance took about 4 hours and all the servers were back up - except the storage system that hosts the virtual machines for YDNS. After some hours we finally found the cause of this and fixed it. YDNS came back to normal operation.

To avoid such problems in the future, we have changed some things. Each name server node got it's own read-only database server, which uses stream replication to get latest updates from the primary database server. That results in faster lookup speeds when querying DNS records and helps to keep YDNS answering DNS queries in case one or more servers are unavailable. If something like today would happen again, your DNS queries will still be answered, but you wouldn't be able to update any records until the primary database is back (which is linked with the web site and backend).

We currently offer three DNS servers at various locations:

  • (Hamburg, Germany)
  • (Frankfurt am Main, Germany)
  • (New York City, USA)

We will soon deliver a closed beta test of a brand new YDNS, which will also increase the availability and scalability of this service.

Again, we kindly apologise of any trouble caused by the outage last night.

In case you have any questions regarding this, please don't hesitate to leave us an reply or email us at