DNS records

A DNS record is one line of instructions attached to your domain. Each line answers a narrow question. An A record says which server address the domain points to. A CNAME record says a name is really just an alias for another name. A TXT record holds a short piece of text, usually there to prove you own the domain or to tell mail systems which servers are allowed to send email as you. None of them do anything flashy. Together they are the reason typing a domain into a browser or hitting send on an email actually goes somewhere.

Every domain has a full set of these records sitting in whatever account manages its DNS. That account, not your website host and not your email provider, is the real control panel for your business’s online identity. Change a record there and every visitor’s browser eventually sees the change, because DNS is the layer that sits in front of everything else.

Why it matters to you

Most business owners never look at DNS records until something breaks, and by then it is usually because nobody could say who had access to change them. A vendor set them up years ago, the login lives in an old inbox, and the business is stuck asking permission to fix its own domain. I have seen this exact situation more than once: a client whose domain, mail and analytics were scattered across accounts that were not theirs.

Records themselves are cheap and simple. What is expensive is not knowing where they live. If your nameservers point somewhere you cannot log into, you do not actually control your domain, no matter what the registration paperwork says.

How I set it up

Before I touch anything, I find out where the DNS records currently live and who can access that account. If they are scattered or held by a vendor, the first job is consolidating them into an account the business owns outright, then adding records as needed: one for the website, one or more for mail, and TXT records for whichever services need to prove the domain is really yours.

I keep this list short on purpose. Every record is one more thing that can be misconfigured, so I only add what a working service actually needs, and I document what each one does before I walk away from the project.

What it looks like in practice

You will not look at these day to day. What you should be able to do, at any point, is log into the account that holds them and see every record listed plainly: what it points to, and why. If a marketing tool asks you to “add a TXT record to verify your domain,” that request goes to whoever holds this account, and it takes minutes, not a support ticket to a vendor who may or may not still answer.

That access is the difference between owning your domain and renting it from whoever happened to set it up first.