How to Connect a Domain: DNS Settings and Propagation Explained

DNS settings are the few lines of text that decide where your domain sends people, and a newly registered domain usually points at a parking page rather than at your website. To connect a domain, you change a handful of those settings, wait while the change spreads across the internet, and then check that everything arrived where it should. None of this needs technical training, but it does need care, because a single wrong character can leave your site unreachable or your email silent. The words involved sound intimidating at first: records, nameservers, propagation, time to live. Each of them describes something simple once you see what it does. Taken in the right order, with a note of what existed before you started, the job is far less daunting than it looks.

Connecting comes after buying, so you need to own the domain already or be about to. If you are still deciding what it should be, our business name and domain finder can suggest names for your business with addresses still waiting to be registered, and show how much interest there is in their words, while our guide on choosing the right domain ending will help you settle between a global and a local ending. Once the domain is registered, the same steps apply whichever company sold it to you, because the system underneath is the same everywhere. The screens look different from one provider to another, and the labels vary, but the records do not. Keep the account login for your domain handy before you begin. You will also want the connection details from whoever hosts your website, which they provide for exactly this purpose.

What happens when you connect a domain

Three separate things have to work together for a visitor to reach your site. The registrar is the company where you bought the domain and where its details are held. The DNS, short for the domain name system, is the internet's directory, which turns a name people can remember into the numerical address of the computer holding your website. The host is the company whose servers store the website itself and send it to visitors. Connecting a domain simply means updating the directory entry so that your name leads to your host. Nothing is moved or copied, and your website stays exactly where it is.

A useful way to picture it is the contact list on your phone. Your domain is the name saved in the list, the host's server is the phone number, and the DNS records are the entry that links one to the other. When a customer in Mombasa types your address, her phone quietly looks up the entry and dials the right number. If the entry is missing or wrong, the call goes nowhere, even though both your name and your website exist. That is why most connection problems are not about the website at all. They are about a directory entry that has not been written, has been written wrongly, or has not yet reached the customer's phone.

The directory entry for your domain is managed in one place, decided by the domain's nameservers. Nameservers are the computers that hold the official records for your domain, and by default they usually belong to the registrar. Some hosts ask you to change the nameservers to theirs, which hands them the whole job of managing your records. Others ask you to leave the nameservers alone and add one or two individual records at your registrar instead. Both approaches work, and your host's instructions will tell you which one it expects. What matters is knowing where your records live, because changes made anywhere else will have no effect.

The DNS records you are likely to touch

Most connections involve just two kinds of record. An A record links the bare domain, the version with nothing in front of it, to the numerical address of your host's server, which your host will give you. A CNAME record links one name to another name rather than to a number, and it is commonly used to make the version beginning with www follow the bare domain or point to a name your host provides. Between them, these two records make sure customers reach your site whether or not they type the www at the start. Your host may give you one of each, or two A records, or a slightly different combination. Enter exactly what it gives you, no more and no less.

Two other kinds of record deserve respect even if you never edit them. MX records tell the world where email for your domain should be delivered, and if you already use email at your domain, deleting or overwriting them will stop messages arriving. TXT records hold short pieces of text that prove you own the domain or help other mail servers trust your messages, and services you sign up to will sometimes ask you to add one. A guest house in Zanzibar that already receives bookings by email at its own domain could lose days of enquiries if those records were wiped while connecting a new website. Before you change anything, note what records already exist. That small habit is the difference between a smooth connection and a missing week of email.

Every record also has a setting called time to live, usually shown as TTL and measured in seconds. It tells other computers how long they may keep a copy of the record before checking for a newer one. A long time to live makes lookups slightly quicker but means changes take longer to be noticed, while a short one makes changes show up faster. If you are planning a move, lowering the time to live a day or so beforehand can shorten the wait after you make the real change. Most owners can leave it at whatever the provider suggests. It is worth knowing about mainly because it explains why changes are not instant.

How to connect a domain and change its DNS settings

Start by gathering everything before you touch a single record. From your host, get the exact values it wants, whether that is a pair of nameservers or a set of records with their types, names and destinations. From your registrar, make sure you can log in, and check that the domain is active and not close to expiring. Then open the DNS area of your registrar's account and take a screenshot or copy of every record already there. A dental clinic in Glasgow or a driving school in Ibadan can lose real bookings if an email record disappears, and a screenshot is the simplest way to put things back. Only when you have all of this should you start editing.

If your host asked for a nameserver change, find the nameserver setting for the domain, choose the option to use custom nameservers, and replace the existing ones with the names your host provided, spelled exactly. If it asked for individual records instead, edit or add the A record for the bare domain and the CNAME record for the www version, using the values given. Where an old A record already points somewhere else, change it rather than adding a second one alongside, because two conflicting records send visitors to two different places. Leave the MX and TXT records alone unless your host or email provider has told you to change them. Save each change and check that it appears in the list exactly as you entered it. Then stop editing, however tempting it is to keep adjusting.

Once the records are saved, return to your host and use whatever check or confirmation step it offers. Many hosts look up your records for you and show a message when they can see the domain pointing at them. At that point they usually set up the security certificate that lets your site load with the padlock in the browser, which can only happen once the domain points their way. If the host cannot see the change yet, that does not mean you made a mistake. It usually means the change has not yet spread far enough, a delay known as propagation. Give it some time before you start undoing anything.

Propagation: why the change takes time

Propagation is the name for the period between saving a change and seeing it everywhere. Your new records take effect at the source almost at once, but computers around the world have kept copies of the old ones, and each will only check again when its copy expires. Internet providers, office networks and individual phones all keep such copies. So for a while, a customer in one city may see your new website while a customer elsewhere still sees the old page or an error. Nothing is broken during this period; the internet is simply catching up. Most changes are visible within a few hours, although it can occasionally take up to a couple of days for every copy to expire.

There are a few sensible things to do while you wait. Check your site on a phone using mobile data rather than your home or office connection, since a different network may already have the new records. Open the site in a private browsing window, which ignores some of what your browser remembered. Avoid making more changes in the meantime, because each new edit restarts the wait and makes it harder to tell what is working. If you have customers due to visit the site, a short note on your social media pages saying the website is moving can save confusion. By the following morning, most owners find that everything has settled.

Changes to nameservers tend to take a little longer to settle than changes to individual records, because the information about which nameservers to ask is itself copied widely. They also carry one extra risk worth planning for. When you hand your nameservers to a host, the records stored at your registrar stop being used, so any email or verification records you had there must be recreated with the new provider. Owners who forget this find that the website works perfectly while email quietly stops. Before switching nameservers, compare your screenshot of the old records with what exists at the new provider. Anything missing should be added before the switch, not after it.

When the connection still is not working

If a day or two has passed and the site still does not load, work through the usual causes calmly. The most common is a typing error, such as a missing letter in a nameserver or a stray space at the end of a value, so compare each record character by character with your host's instructions. The next is a leftover record, such as an old A record still pointing at a previous host, which sends some visitors one way and some another. Check too that the domain itself has not expired or been suspended, since registrars sometimes pause domains whose owners have not confirmed their contact email. Finally, make sure you edited the records in the place your nameservers actually point to, not in an account that is no longer in charge. One of these explains most stubborn problems.

Sometimes the site works in one form but not the other, loading with www in front but not without it, or the reverse. That almost always means one of the two records is missing or wrong, so look again at the A record and the CNAME record separately. If the site loads but the browser warns that it is not secure, the security certificate has probably not been issued yet, which most hosts do automatically once they can see the domain pointing at them. Give it a few hours, then ask your host to check. When you contact support, send screenshots of your records and the exact message you see, which turns a long conversation into a quick fix. There is no shame in asking, since even experienced developers double-check these settings.

Once the site loads reliably at your domain, it is worth checking how it looks to search engines as well as to people. The AI Website SEO Checker, one of our AI SEO Tools, looks over a live site and points out what is holding it back, from missing page titles to slow pages. Still without a website? AI Web Maker will put one together around what you tell it about your business, and you can look over the preview for as long as you like without paying. Hosting for the live site is $119 a year, the domain is a separate purchase, and a domain registered at launch is registered together with that hosting. Either way, the effort of connecting a domain is only rewarded when people can find what is at the other end. Make that your next job.

Connecting a domain comes down to a short sequence: gather the values, record what already exists, change only what your host asks for, confirm, and give the internet time to catch up. The vocabulary is the hardest part, and once you know what an A record, a CNAME, an MX record and a nameserver each do, the screens stop looking mysterious. Patience matters as much as accuracy, because most panicked changes are made during propagation and undo work that was already correct. Keep your screenshots and notes somewhere safe, since you may need them again when you add email or move hosts. Done carefully, this is a job you do once and then rarely think about. From then on, your domain will simply lead customers to your door.