Connect your domain to your hosting from an iPad

Buying a domain and buying hosting are two separate purchases, and a website only appears when the two are connected. The connection is called DNS, and it is less technical than it sounds: you are simply telling the domain where your website lives. The whole job happens in Safari on the iPad, in two browser tabs — your domain registrar in one, your hosting account in the other. Set aside half an hour, most of it waiting.

If you have not bought either yet, read how to pick a domain name and shared hosting vs website builders first. If you already installed WordPress, you have done a short version of this once — the WordPress guide covers pointing the domain in one step. This guide is the full version, for when that short version does not behave.

Two ways to connect: nameservers or DNS records

There are two ways to make the connection, and you only need one of them.

Nameservers (the easy way). Your hosting provider gives you two nameserver addresses, something like ns1.examplehost.com and ns2.examplehost.com. You paste those into your domain registrar's settings, replacing whatever is there. From then on, your hosting provider controls all of the domain's DNS settings. This is the way most beginners should use: one change, and the host takes care of the rest.

DNS records (the precise way). Instead of handing over control, you keep DNS at the registrar and point just the website at the host. The record you need is an A record: the host name (usually @ for the main domain, and www for the www version) and the server's IP address, which your hosting account shows in its control panel or welcome email. Use this way only if you have a reason to keep DNS at the registrar — for example, your email is set up there and you do not want to move it.

Do not do both at once. If you set nameservers and also add A records at the registrar, the nameserver change wins and the registrar's records are ignored, which makes troubleshooting confusing.

Visit SiteGround

Step 1: Find the nameservers or the IP address

Log in to your hosting account from Safari on the iPad. The nameserver addresses are usually on the account dashboard, in the welcome email, or under a heading like "Account Information". The server IP address, if you are going the DNS-record route, is in the same place. Copy the values exactly — a nameserver with one wrong letter points your domain nowhere.

If the hosting panel looks cramped, use Safari's "Request Desktop Website". Hosting panels are built for wide screens, and the desktop layout is much easier to tap through.

Step 2: Make the change at the registrar

Open your domain registrar in a second Safari tab and find the domain's DNS or nameserver settings. The wording varies — "Nameservers", "DNS Management", "Domain Settings" — but every registrar has this page. For nameservers, choose "Custom" or "Use custom nameservers" and paste in the two addresses. For DNS records, add an A record for @ pointing at the server IP, and another A record for www pointing at the same IP.

Save, and take a screenshot of the before-and-after settings on the iPad. If something goes wrong later, that screenshot is the fastest way back.

Step 3: Wait for propagation — and know what it means

DNS changes spread across the internet gradually, usually within minutes, sometimes over a few hours, and in rare cases up to 48 hours. During that window, different people see different results: the site may load for you but still show the registrar's parking page for a friend. That is normal, not a sign that you broke something.

Check progress by opening your domain in Safari. When the registrar's parking page is replaced by your host's default page — or by your actual site, if you have already built it — the domain has arrived. If nothing changes after a day, re-check the values you typed before assuming the host is at fault: a typo in a nameserver is the most common cause.

Step 4: Check the www version and the secure lock

Two checks beginners skip. First, open both yourdomain.com and www.yourdomain.com. If one works and the other does not, you are missing a record for the broken one — add the www A record, or check that the host redirects www to the main domain. Second, look for the padlock in Safari's address bar. Most hosts issue a free security certificate automatically once the domain points at them, but it can take up to an hour after propagation. If the padlock is missing after a day, your host's control panel will have a security or SSL section where you can trigger the certificate.

The mistakes that leave a site showing the wrong page

1. A typo in a nameserver or IP address. Copy and paste, never retype. One wrong character and the domain points nowhere.
2. Changing records in two places. If nameservers point at the host, edits at the registrar do nothing. Change DNS in only one place: the host's panel, or the registrar's — not both.
3. Forgetting the www record. The main domain works, www does not, and visitors who type www see an error. Always set up both.
4. Breaking email by moving DNS. If your domain's email is set up at the registrar, switching nameservers to the host can stop mail from arriving. Before you switch, note down the mail records (MX records) and recreate them at the host, or keep DNS at the registrar and use A records instead.
5. Panicking during propagation. Changing settings again while the first change is still spreading only restarts the wait. Make one change, save it, and give it hours before touching anything.

When the domain and hosting come from the same company

Sometimes there is nothing to connect: if you bought the domain and the hosting from the same provider, they may already be linked, and the site appears as soon as you install something. If the site still shows a parking page after a day, the steps above still apply — check the nameservers first, because even a same-provider setup can leave the domain pointing at the registrar's default.

The bottom line

Connecting a domain is one decision and one careful copy-paste: nameservers for the easy route, A records if you need to keep DNS where it is. Then wait, check both the plain and www versions, and confirm the padlock. The site itself — pages, design, content — is a separate job; DNS only decides where the domain sends visitors. Once it sends them to your hosting, that part is done, and it rarely needs touching again.