DNS Simplified: A Records
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.
To kick off this series I’d like to start with the humble and well-known A record. The “A” in A record stands for “Address”. Simply put, an A record is used to find the address of a computer connected to the internet from a name. Whenever you visit a web site, send an email, connect to Twitter or Facebook or do almost anything on the Internet, the address you enter is a series of words connected with dots.
For example, to get to this blog you may have followed a link from another web site pointing to blog.dnsimple.com. In my DNSimple account is an A record that points blog.dnsimple.com to the IP address 184.108.40.206.
When you clicked on this link your computer probably asked a nearby DNS server “Is there an address record for blog.dnsimple.com?”. If the server can answer this question then it replied with: “Yes, the address for blog.dnsimple.com is 220.127.116.11”. If it cannot answer the question directly then it probably went and asked another DNS server if they have the answer, and that server either answered or asked another server, and so on. This process is called “resolving” and is the way that all DNS requests are handled on the Internet. How it does it isn’t important right now, what matters is that ultimately a DNS server answers with the correct answer and your web browser now knows that it should request the DNSimple blog’s home page from 18.104.22.168.
You can actually do quite a bit more with A records, including using multiple A records for the same domain in order to provide redundancy. Additionally multiple names could point to the same address, in which case each would have it’s own A record pointing to the same IP address.
The bottom line: A records are used to map a name to a computer’s address on the Internet, and are one of the primary records used in DNS servers.
I break things so Simone continues to have plenty to do. I occasionally have useful ideas, like building a domain and DNS provider that doesn't suck.
We think domain management should be easy.
That's why we continue building DNSimple.
The Villains of Remote Work
Remote work and small teams come with their own challenges, these are some of mine.
Elapsed time with Ruby, the right way
Elapsed time calculations based on Time.now are wrong. Learn why they are wrong and how to fix them.