What Is DNS? How Your Domain Name Finds Your Website

DNS (Domain Name System) is the system that translates a domain name such as example.com.tr into the IP address of the server where your website lives. When a visitor types your address, the browser first asks DNS, "Which address is this name at?" and connects to the server once it gets the answer. Whether your site loads and whether your email reaches the right place both depend on your DNS records being correct.

What is DNS?

Every server on the internet has a numeric address: its IP address. People, on the other hand, remember names. DNS translates between the two. In the common analogy, it is the phone book of the internet.

DNS is not a single list stored on one server. It is a hierarchical, distributed system shaped like a tree. At the top are the root servers. The root server system consists of 13 root server identities (A through M), operated by 12 independent organizations. Each identity has many copies spread around the world. Below the root are the servers for extensions such as .com and .tr, and below those are the servers that hold the records for individual domain names.

How does DNS work? The journey of a query

When a visitor types example.com.tr into the browser, these steps happen in the background:

1. Cache check: The browser and the operating system check whether they have looked up this name recently. If the answer is in the cache, the process ends here.
2. Question to the resolver: If not, the question goes to a recursive resolver, usually run by your internet service provider or by a DNS service you have chosen.
3. Search from the root: If the resolver doesn't know the answer, it is referred to the root servers, then to the .tr servers, and from there to your domain's authoritative nameserver.
4. Answer: The authoritative nameserver returns the domain's IP address. The resolver stores this answer for the length of the TTL and passes it to the browser.
5. Connection: Now that the browser knows the IP address, it connects to the server and requests the page.

This journey usually takes the blink of an eye. By standard, DNS queries run over port 53.

DNS records you should know as a business owner

When you open your domain's DNS settings, you see a table. Each row is a record. The ones you will run into most often:

Most of these records are part of the core definition of DNS, the RFC 1034 and RFC 1035 standards from 1987. The AAAA record used for IPv6 was added later.

Where do you set the nameservers?

At the registrar where you bought your domain, you specify which nameservers your domain should use. For example, your hosting company gives you two addresses such as ns1.hostingcompany.com and ns2.hostingcompany.com. From then on, you manage your DNS records in that company's control panel. Knowing which panel to edit solves many "I changed it but nothing happened" problems.

TTL: why does "DNS propagation" take time?

Every DNS record has a TTL (Time To Live) value. It is measured in seconds and tells resolvers, "Keep this answer for no longer than this." If the TTL is 3600, the record stays in cache for one hour.

That is why, when you change a record, not every resolver in the world sees the new value at the same time. A resolver holding the old answer in its cache keeps returning the old address until the TTL runs out. People call this "DNS propagation." In reality nothing is spreading; caches are simply expiring.

Practical tip: A day before a planned change such as a server migration, lower the TTL of the relevant record (for example, to 300 seconds). After the change, once everything works, raise the TTL again. This shortens the transition.

How does DNS affect your website and your business?

• Availability: If DNS doesn't respond, your site won't load even if your server is running. That is why the reliability of your nameserver service matters.
• Email: If the MX record is wrong or deleted, incoming email won't reach you. If TXT records such as SPF are missing, the email you send may land in the recipient's spam folder.
• Speed: Each new visitor triggers a DNS lookup. A DNS provider with fast, widespread infrastructure shortens the first connection.
• Security: When attackers use fake DNS answers to send users to the wrong site, it is called DNS poisoning (spoofing). DNSSEC is an extension that verifies DNS answers really come from the authoritative source and haven't been altered. Note: DNSSEC does not encrypt data; it only proves that the data is authentic.

Common DNS mistakes

1. Changing nameservers without moving the old records. Setting up only the A record at a new provider and forgetting the MX and TXT records is one of the best-known reasons email stops working.
2. Editing in the wrong panel. If your domain is registered with one company and your nameservers are at another, the records are managed in the second company's panel.
3. Forgetting the www record. example.com.tr loads, but www.example.com.tr doesn't.
4. Conflicting records for the same name. A name cannot have a CNAME and other records at the same time; this leads to unexpected behavior.
5. Losing access to the DNS panel. If only your former agency knows the panel login, even the simplest change can take days.

Our experience

In website projects, we make a copy of the domain's existing DNS records before going live. That way the email (MX) and verification (TXT) records aren't lost when the nameservers change. For server changes, we lower the TTL in advance and plan the switchover, and we make sure access to the DNS panel stays with our client. We cover ownership and renewal of the domain itself in detail in our post What is a domain name?.

Frequently asked questions

Conclusion

Visitors never see DNS, yet your website and your email depend on it. Knowing which panel manages it, keeping a copy of your records and making changes with the TTL in mind prevents most problems. In our web design and WordPress development projects, we treat domain and DNS settings as part of the launch plan. If you are planning a new site, we also recommend reading what to check before commissioning a corporate website.