Automate your DNS records even more, with services!

We are happy to announce a new feature that is available right now. Everything is running in the cloud and you should not feel any pain to connect your cloud applications with your domain.

Services are here to help you configure the applications you use. We start with Gmail, GitHub and GitLab Pages, Tumblr and Cloudoffice. For each service you need to configure your DNS and we will take care of it from now on.
Just tell us under which record you want to use the service and we will create the necessary records for you.

It can be that easy to configure your domain to use the Google mailserver or Google Apps. No need to copy and paste all the configurations.
Let’s have a look at the API:

curl --get "https://api.tokendns.co/v1/reserve" \
  -d apikey=${apikey} \
  -d domain=${domain} \
  -d name=@ \
  -d service=gmail

You can combine them as well. Just use a comma as separator.

Which services do you use and would like to see?

The TokenDNS NodeJS module is ready

Integrating the TokenDNS API into your application should be as easy as possible. We created a small and fast nodejs plugin that you can use to get started. There is nothing more to say than, check our docs, grab the module from github and look at this example:

var TokenDNS = require('index.js')
var apiKey = 'YOURAPIKEY';

var tokenDnsClient = new TokenDNS(apiKey)

tokenDnsClient.registerDomain({
    apikey: apiKey,
    action: 'add',
    domain: 'example.com',
    method: 'email',
    email: 'webmaster@example.com',
    billing: 'yearly',
    },function(err, res) {
        console.log(res.status);
});

Have fun and let us know when you run in a bug ūüôā

We love the Insomnia REST Client

We love APIs and the Insomnia REST Client is perfect to test new things. You can use it for free and is available for Linux, MacOSX and Windows.

Sometimes it is just easier to get started when you have something on hands. Grab our Insomnia configuration for our TokenDNS API on github and start playing. Add your apikey and domain after importing to get started.

Its never been easier to get productive.

How to use Google Cloud with TokenDNS

When you are using the Google Cloud Platform, you want to automate as much as possible. We want to help!

Starting a new machine in GCE is not a difficult thing and luckily it’s possible to supply a startup script and some metadata to automate the registration of the new machine with TokenDNS.

Configure Startup Script

We need to use a little helper script to make the dns¬†registration. Don’t worry we published it¬†on github.com for you to grab. The¬†register_tokendns.sh¬†script will get executed when the VM starts¬†and use¬†some metadata information that we configured to register it with TokenDNS.
Copy the content of the register_tokendns.sh script and paste it in the Startup Script section when you add a new virtual machine.

Add Metadata

The metadata that we configure are apikey and domain. These are necessary information that you need to provide, otherwise the registration will fail. It would be possible to extend the script to add e.g. tags.

Lets have a look at the Console in the Google Cloud how it should look:

If you want to learn more about GCE and Startup scripts you can look here. They even tell you how to use the CLI and scripts ūüėČ

You own your data. Here is how to export them!

We believe that you should be able to access your data anytime you want. Most DNS provider does not give you the possibility to export all your records without knowing them. You should be able to do so anyways.
That’s why we implemented an export function for all your records. This makes it easier to keep an eye on them and make¬†an backup of your records (just in case).

Request:

curl --get "https://api.tokendns.co/v1/export" \
  -d apikey=${apikey} \
  -d action=records \
  -d domain=${domain}

Response:

{
  "status": "200",
  "domain": "blabladns.xyz",
  "records": [
    [
      {
        "name": "blabladns.xyz",
        "type": "TXT",
        "content": "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCFPb9PnIJB8z2Ev+C+jmNPVVLxGMeqDNKOoa9/9R/C6rgRkLcxFHAB4ibbr7h7ybngirME0jsn4ZgBsweaRSfqdj5Arka1luqEAKxaBW6K6pi9HDvRpWQzFdwQriUcWyyIVsCjYEQLZJdZOD8nX9sJk5u+ihlumstZaTIIUFA/jQIDAQAB",
        "ttl": "300",
        "change_date": "1485196067",
        "tag": ""
      },
      {
        "name": "asd.blabladns.xyz",
        "type": "A",
        "content": "127.0.0.5",
        "ttl": "300",
        "change_date": "1471774941",
        "tag": ""
      },
      {
        "name": "asd.blabladns.xyz",
        "type": "A",
        "content": "10.10.10.10",
        "ttl": "300",
        "change_date": "1485419347",
        "tag": ""
      },
      {
        "name": "facebook.blabladns.xyz",
        "type": "A",
        "content": "188.166.134.65",
        "ttl": "300",
        "change_date": "1469030691",
        "tag": ""
      },
      {
        "name": "facebook.blabladns.xyz",
        "type": "MX",
        "content": "127.0.0.1",
        "ttl": "300",
        "change_date": "1469030795",
        "tag": ""
      },
      {
        "name": "insomnia.blabladns.xyz",
        "type": "A",
        "content": "178.62.218.50",
        "ttl": "300",
        "change_date": "1481653536",
        "tag": "website"
      },
      {
        "name": "www.blabladns.xyz",
        "type": "A",
        "content": "8.8.8.8",
        "ttl": "300",
        "change_date": "1469028995",
        "tag": ""
      },
      {
        "name": "www3.blabladns.xyz",
        "type": "A",
        "content": "127.0.0.12",
        "ttl": "300",
        "change_date": "1483823787",
        "tag": "website"
      }
    ]
  ]
}

API Documentation and our Libraries are updated and ready to get explored.

Register your domains with TokenDNS

YES it is possible to use TokenDNS with your own domains now. From a Dynamic DNS only service we are growing into a full DNS service.
This means you can use all features with your own domains and enjoy great integrations and always be informed what is going on.

Checkout our features like FailoverDNS, Webhooks, Tags or our amazing easy API.

All this comes with a small price tag and great customer support. From 5EUR monthly or 50EUR per year you can use TokenDNS as your primary DNS service.
The fun part starts with the registration of your domain, because the first month is free and you can test our service. If you don’t like it, you don’t need to pay for it. Isn’t that great?

In the coming weeks we will show you how you can get the most out of TokenDNS and how to integrate it in your existing application or system. Our goal is to make it as easy as possible to use our service. This means automation, automation and more features.

REGISTER NOW and let us know in the comments or per email what you would like to see and we will try to make it happen.

How to verify your domain?

When registering a new domain with us you need to verify that you are the owner of the domain. Why? Otherwise you could make some spooky things that we do not approve.

How to verify your ownership?

At the moment we offer three ways to verify a domain. We call it HTTP, DNS or Email. Every option has its own pro and cons. Lets explain them one by one.

Email

The most common and easiest option is Email. You need to have access to one of the following email address. As example we are using example.org which you need to replace with the domain you want to register.

webmater@example.org
admin@example.org

When you register the domain example.org you can specify one of the two mentioned recipients. You will receive an Email with a verification link which you need to open to verify your ownership.
This is very easy and in the normal case very fast. If you don’t have access to these emails, check out the other options.

HTTP

If you don’t have access to Email one other fast way is to use http verification.
After registering your domain with us, you will find some information in the web interface or in the callback of the api call .

What are we expecting? You need to create a html file in your domain root directory with a specific content. This means you need to have access to your current webserver or application.

In the example above you can see that you need to create a file called tokendns-site-verification-febaf9c6a1e96e60.html with the content 657f7c1ff545dff91c39bb56ff653ea4cb177257.
Just create the file and we will take care of the rest and inform you when the domain is validated. In the meanwhile you can start and create your records.

DNS

Our last, but not less used option is by dns. This means that you need to create a TXT record with your current dns provider. If this is easy and fast depends a little bit on your current provider, but most of the times its fast as well.
Lets give you an example how easy it is with us:

The get the necessary informations how the records needs to look is the same way as our http example. Easy to check in the web interface or when you use the api in the callback.

In the end your DNS server needs to responds with something like this:

$ dig example.org txt +short
tokendns-site-verification=7163bf009221f7e4

In the future we might add more options or email recipients, but at the moment this should offer a wide variety and gives everyone a possibility to verify the ownership of the domain.

Let us know if you need something else ūüôā

BlaBlaDNS is now TokenDNS

Welcome back! It was a little bit quite here, but something beautiful happened.

The cute BlaBlaDNS grew into TokenDNS and is now a full DNS service where you can host your own domains. Manage your records through the same webinterface that you know or the easy API.

What changed for the Dynamic DNS service of blabladns.xyz? Nothing! It is all the same, will never cost you a cent and we still have no logs.

Well, we have a new beautiful website: www.tokendns.co

What brings the future? We will show you what you can achieve with TokenDNS and make your life a little bit easier. More features are coming to TokenDNS in the future, but you can already checkout our existing ones:

In the next couple weeks we will show you how to use the API for each service and what you can do with it.

Want to try TokenDNS? Absolutely please! When you register your domain, the first month is free. Register NOW!

Steffen

How to add Messenger notifications to TokenDNS?

What is Messenger?

Messenger is probably one of the most used messenger in the world and everyone who has a Facebook account is using it. After we introduced Facebook as authentication method, its now possible to get notifications when your records changed. No need for any additional app on your phone.

What do I need to use Messenger with TokenDNS?

Its very easy. When you are logged in TokenDNS, just open the Messenger site and click Send to Messenger. Thats it!

Visit my.tokendns.co/messenger now.

 

I want to use the API!

Unfortunately this is not possible ūüôĀ

 

How to add PagerDuty notification to TokenDNS?

pagerduty

What is PagerDuty?

PagerDuty is present in most companies who have on call duty. Most are using it in combination with several monitoring systems. Its easy to handle schedules and organise responsibilities.

What do I need to use PagerDuty with TokenDNS?

For obvious reason you need to have an account for PagerDuty. In PagerDuty you can create so called Services and for each service you can create a Integrations. Each integration has a service key and this is what we need.

Now login to PagerDuty and select the Service that should receive notifications from us:
Configuration -> Services -> Select or Create a Service
If you already have a service, go to Integrations and add a new integration:

pagerduty-1

Please select “Use our API directly” and set a proper name. After hitting the green button you will redirect to the previous page and you can see your Integration Key. This key is our token.
We have everything what we need and can enable notification in TokenDNS. Go to your settings and add PagerDuty to your notifications.

blabladns-add-notification

I want to use the API!

I hear you and like it. Easy as you know it:

curl --get "https://api.tokendns.co/v1/notifications" \
  -d apikey=${apikey} \
  -d action=add
  -d provider=pagerduty
  -d description=${service_description}
  -d token=${token_id}