Lessons we've learned by organizing our cookbooks including proper naming and maintenance tasks
Everyone has it but not everyone thinks about their WHOIS info. Read on to learn about the importance of WHOIS.
A handy guide to create stunning slides empowering a great presentation to a (not only) technical audience.
Learning our weaknesses and our strengths, in the eyes of our customers, from our exit survey.
Attending a conference as a team turn out to be game changer
Even with a small team it's easy to lose sight of the strategic goals of your business. Read on to how we are attempting to align project development with business goals at DNSimple.
What inspires us to do customer support the good old fashioned way
Making Standard Operating Procedures Great Again
Learn about the most common techniques to protect against certificate mis-issuance and limit the impact of forged SSL certificates.
We are reminded to fail fast and avoid the sunk cost fallacy in operations
My reflections on the preparation for CodeMash and how the conference unfolded for the DNSimple team.
The code-cation or how I learned to stop worrying and learn Golang.
Ask questions, listen to the answers, and study the trade-offs.
Knowing how one is performing on a distributed team is hard. Here's how we've tried to address it.
Tales of a Spaniard evolving in an English environment
Loin des yeux loin du coeur, what team retreats mean for our distributed team.
How do you get your whole team to achieve a shared vision for marketing? This is the story about how we ran through some exercises using the book Traction as the basis.
Talking about the redundancies in DNS and what you can do to help uptime of your services
A place where we share our favorite learning resources.
We went through the process of accreditation with ICANN some time ago. Here's what it does and why we did it.
Sometimes, even the thousand year old legacy tool is still the best tool.
Throughout the years I've watched as DNSimple has grown to the team we are now, and along the way I've observed what works and what doesn't. In this post I'll share 6 lessons I've learned while the company has grown.
Every domain name registration involves at least three entities: a registrant, a registrar, and a registry. We'll look at them each in this post.
Once you nail the basics, you're golden.
Working remotely can mean spending a lot of time alone, a co-working space can help you alleviate feelings of loneliness and brings additional benefits.
Everything you wanted to know about How DNS works (the comic) and never dared to ask.
Discussing our experience at ChefConf
Understanding how to properly configure redirects with HTTP and HTTPS sites.
We develop and maintain a few open source Chef cookbooks, this post talks about them.
One man armed with little experience and a bandolier of questions takes on DNS. And ghosts.
Move over Walkman, there's a new cool kid in town.
One possible use of the DNSimple multiple account feature is to segment your domains into different accounts depending on the level of service.
The results of the first DNSimple documentation day, codename OMG Thursday.
The results of the first DNSimple bug squashing day, codename WTF Thurdsay.
We've looked at resource records in general. Today let's investigate the various types of DNS records.
We occasionally recommend people switch to using Google's public DNS resolvers. Here are some of the reasons why and how you can make that change.
How we reorganized the footer to make it more useful.
People often wonder if they should separate their registrar from their DNS provider. We're taking a look at both sides so you can make up your mind for your domains.
DNS queries and responses fly across the internet all day, but we don't often take a look at what's inside of them. Today we do.
Running a DNS server might not be too hard, but it's usually best not to go alone when maintaining an entire DNS infrastructure. Here's some of the reasons we think managed DNS is a great idea.
Problems with DNS configuration come up all the time. Knowing about the tools to resolve them can really get you out of a bind.
Quality customer support is an important cornerstone of how we do business at DNSimple. In this blog post I'll show you how we do it, what tools we use, and what kinds of challenges we face.
There are a lot of DNS Servers out there. We're looking at some of the top ones here and comparing their features and why some are chosen
An overview of the technical challenges behind the implementation of the Secondary DNS server support.
We're starting a new series of educational posts here starting next month, along with a newsletter.
We believe in the power of education and practice, and we believe in putting our money where it can make a difference. Read on to find out more...
Transferring a domain name from one registrar to another is often complicated and mistakes can cause you downtime and result in lost business. Don't let that happen with our new guide.
Benjamin Fritsch of CodeShip.io shows how they use the DNSimple API with GitHub to continously deploy their DNS zones as changes are made.
Learn about how DNSimple manages changes to over 50 servers across 5 data centers around the world with a team of 5 developers.
Troy Hunt has captured the essence of why we made DNSimple in a pictorial blog post on why he moved to DNSimple.
Security is all about tradeoffs. The story of how Naoki Hiroshima's Twitter handle was stolen from him should cause us all to stop and take some time to think about security.
IO domains do not follow the same renewal procedures as normal TLDs like com, net and org. IO domains must have auto-renewal enabled to be renewed.
Last year I gave a talk at Ignite Boulder titled: "DNS in 5 Minutes". I've been remiss in not sharing this, so here you go.
Here are a couple of things that you should know about before transferring a domain.
We at DNSimple oppose SOPA and any attempt by the US government to try to rule the Internet. DNSimple vehemently opposes any attempts to censor the Internet or to provide the facilities to do so.
SPF stands for Sender Profile Framework. DNSimple provides an easy interface for creating SPF records so you don't have to manage those records on your own.
If you have more than a few domains with GoDaddy then preparing them for transferring away can be a time-consuming process. To help, we've put together this guide.
MX stands for Mail eXchange. MX Records tell email delivery agents where they should deliver your email. You can have many MX records for a domain, providing a way to have redundancy and ensure that email will always be delivered.
CNAME stands for Canonical Name. CNAME records can be used to alias one name to another. For example, if you have a server where you keep all of your documents online, it might normally be accessed through docs.example.com. You may also want to access it through documents.example.com. One way to make this possible is to add a CNAME record that points documents.example.com to docs.example.com. When someone visits documents.example.com they will see the exact same content as docs.example.com.
Today I’m starting a new series of regular blog posts called “DNS Simplified”. In these post it is my goal to describe DNS and domain name concepts so they are easy for anyone to understand.