Major FRONTEND and API update

Update Record

Welcome back and lets get started.

The API got some new endpoints for your settings. Its now possible to change your username, email and reset your apikey.

How to change my username?

curl --get "" \
  -d apikey=${apikey} \
  -d action=username \
  -d value=MyNewUsername

How to change my email?

curl --get "" \
  -d apikey=${apikey} \
  -d action=email \

How to reset my apikey?

curl --get "" \
  -d apikey=${apikey} \
  -d action=apikey

All of this is possible through the frontend as well.

AND You can now reserve a subdomain through the frontend.
Just click on the “Reserve Record” button in the domain section and reserve your beloved subdomain with one click.

That means that all api functions are available through the frontend and every one can use this very easily. Very exciting and ready to implement new features!


What’s my IP?


Welcome back,

we have been writing about this earlier, but wanted to bring all the tools you need to use this free and secure dynamic dns alternative.
It’s possible to get your public ip within the BlaBlaDNS ecosystem in a secure way. The address is and can only be reached through https.

When you update your records you can now use this little service. Example?

curl --get "" \
  -d apikey=${apikey} \
  -d name=${name} \
  -d content=$(curl -4

Be safe!

Feature Update: Delete


we have been busy behind the curtains and happy to present two new features for BlaBlaDNS:

– New API endpoint to delete records
– Update and delete records through the website

Finally you can delete records yourself that are not needed anymore. It is as easy as requesting the status of your records. The documentation got updated as well.

curl --get "" \
  -d apikey=${apikey} \
  -d name=${name}

For the usability of our user, its now possible to update and delete the records through the website:


Happy clicking 🙂

Introducing: Bug Bounty Program


It doesn’t matter how much and how often you test before the launch. Some bugs will not show up. Of course this happened to TokenDNS and two bugs were found by truly amazing users.

One bug didn’t allowed to register when you are using a + in the email address. This is supported by gmail to track how your email got into the wrong hands. Is fixed and you are more than welcome to register with a plus in your email address.
The other was a problem with the api. When you reserved five records, it was not even possible to update them or get the status. How I see it, this was a major problem and probably would go on for a while if the user hadn’t reported it. Obviously fixed in the meanwhile.

I am very thankful for the bug reports and thats why the bug bounty program is launched. Whenever you find a blocker bug in the website or the api, please report it to us and we will upgrade your account with some freebies 🙂

Lets find these nasty bugs!


Hello Internet!

Welcome to our new Blog.

TokenDNS is a api first and truly free dynamic dns service. I build it because I couldn’t find anything suitable for me. Looking for a free service that is offering a little bit more than usual provider was going to be impossible.
Most dynamic dns provider does not allow AAAA records or that I can set my own TTL. In most cases this is not really necessary, but I like to have that freedom. With that in mind TokenDNS was born.

When talking to a DDNS provider you always use a API to update your records – no one wants to do this manually. The API had to be easy to implement in all the different router and operation systems, but on the same site plain and clear.

Note: When using TokenDNS at the moment all subdomains will be registered under

How to use TokenDNS?

1. Register
Before you can use the DDNS service you need to create an account on When you confirmed your email, you are able to login and receive your API key in the Settings.
This is necessary to make sure that you don’t change any records of your friends, but don’t worry we don’t have any logs.

2. Reserve a name
In the beginning you can only reserve a name using the API. Soon this will be possible through the web interface as well. Its not difficult and can be done with a easy curl request.
In my example I will use as an example:

curl --get "" \
  -d apikey=${apikey} \
  -d name=www5

When the status is 200 the name was free and you own it now. Congratulations! When you get a 400 someone else was faster and that given name is already gone. Try another!

3. Update your A/AAAA record
If you want to use your subdomain with your own services you need to update the records from time to time. Just another curl request:

curl --get "" \
  -d apikey=${apikey} \
  -d name=www5 \
  -d content=$(curl -4

You like IPv6, right?

curl --get "" \
  -d apikey=${apikey} \
  -d name=www5 \
  -d type=AAAA \
  -d content=$(curl -6

You did it! Now you can use your subdomain for whatever you want to use it. The API has some defaults, that can be changed. More about that in the documentation.

3.1 Automation with cron
Whenever we can automate something, we should do this. The easiest way on a Linux/Unix server is using cron to update the records every hour (or whenever you want). We just need to create following file and its taken care of:

echo "0 * * * * root curl -s --get -d apikey=${apikey} -d name=www5 -d content=$(curl -s -4 >/dev/null" > /etc/cron.d/tokendns

4. Check the status
Well sometimes DNS is not the fastest, but you want to make sure that we have the correct information and that your problem will be solved soon. Thats where the status comes into place. Its possible to check for changes before the TTL of your subdomain expires:

curl --get "" \
  -d apikey=${apikey} \
  -d name=www5

I hope you will enjoy TokenDNS and can use it to make your life a little bit easier. New features will arrive soon and more integration guides will be made available. Any question?


UPDATE: At the moment it’s not possible to register with a plus in the email address. Will be fixed soon! Fixed at 26.01 at 10:39pm GMT.