Nobody wants to talk about this stuff. It’s not glamorous. It doesn’t make it into the agency case study or the brand refresh reel. But it’s the difference between a website that works and one that quietly 404s while you’re wondering why leads have dried up.
Your brand can look incredible and still be completely invisible online. Not because your design is wrong. Not because your strategy is off. Because someone forgot to point your A record to the right server.
We **fix this for clients regularly. So let’s talk about it.
The problem with “someone else’s job”
The most common version of this we see goes like this: a business gets a shiny new website built. It looks stunning. The designer hands it over, dusts their hands off, and walks out the door. Then the client goes to point their existing domain at the new host and, nothing. The site doesn’t load. Or it loads intermittently. Or it loads in Australia but not in the US. Or worse, it loads the old site for two weeks because nobody understood what DNS propagation actually means.
This isn’t a rare edge case. This is Tuesday.
What’s actually happening (the non-boring version)
DNS (Domain Name System) is essentially the internet’s phonebook. When someone types your URL into a browser, DNS translates that into the actual server address where your site lives. When you change hosts, move to Shopify, or transfer a domain, that phonebook entry needs to be updated, and it doesn’t update everywhere instantly.
Propagation can take anywhere from a few minutes to 72 hours depending on TTL settings, your registrar, and frankly, the mood of the internet that day.
During that window? Some people see your new site. Some see the old one. Some see nothing. And if you cancelled your old hosting too early, some people see an error page while you’re blissfully assuming everything went smoothly.
The Shopify problem nobody warns you about
Shopify is brilliant for eCommerce. It’s also a DNS minefield if you’re not paying attention.
When you connect a custom domain to Shopify, you’re typically redirecting from your registrar (GoDaddy, Namecheap, Squarespace Domains, wherever you bought it) to Shopify’s servers. Simple enough; except:
- If you have a root domain AND a www version, both need to be correctly configured or one will break
- Shopify needs to verify SSL before it works on HTTPS, and if your DNS isn’t pointing right, SSL doesn’t issue, and browsers block the site with a security warning
- If you’ve had email hosting attached to that domain, those MX records can get wiped in the transfer process, killing your email at the same time your website goes live (genuinely fun timing)
We’ve seen clients launch a Shopify store, post about it everywhere, then spend 48 hours with a broken site because the www redirect wasn’t set and nobody caught it.
Domain transfers: the process that punishes impatience
Transferring a domain from one registrar to another is a process that was designed by someone who hated urgency.
There are authorisation codes. There are confirmation emails that expire. There are 60-day transfer locks that kick in if a domain was recently updated (ICANN rules, not optional). The transfer can take five to seven days even when everything goes perfectly. If you initiate it the week before a launch, you’ve created a problem for yourself.
The real danger is doing a domain transfer at the same time as a website migration. If the domain is mid-transfer, changes to DNS records often can’t be made, you’re in limbo between registrars. Neither has full control. Nothing updates. You wait.
The fix is straightforward: do not transfer a domain during a live project unless you have a very specific reason. Get the site built, get it live, then consolidate your domain management if needed.
What this actually costs you
Lost traffic. Broken email. A launch that lands with a thud instead of a bang.
If your site is down or behaving erratically during a campaign, ad spend is wasted. Email marketing bounces if your MX records are wrong. Google indexes the error page instead of your homepage. Trust is quietly eroded with every customer who hits a broken link.
None of this is dramatic. It just slowly kills momentum.
What we do about it
When we build or migrate a site for a client, we treat the technical handover as a project stage, not an afterthought.
That means checking DNS records before and after migration. It means testing across multiple locations and devices before anything goes live. It means keeping legacy hosting active through the propagation window, not cancelling it the same day. It means knowing which records to touch and which ones to leave alone.
It also means having the conversation with clients upfront: what domains do you own, who owns them, where are they registered, do you have login access? You’d be surprised how often the answer to one of those questions is “I’ll have to ask my old web developer”, and that old web developer is now unreachable.
The unsexy truth
The technical foundation of your website is not exciting content. Nobody’s putting their A records on a mood board. But it’s the infrastructure that everything else sits on; your brand, your traffic, your revenue, your customer experience.
You can have the most beautiful, strategically sound website in your industry. If the DNS isn’t right, no one sees it.
This is the part of web development we take seriously, even when it’s not the part anyone asks about. Because we’ve seen too many brands lose a launch week to something that should have taken twenty minutes to fix.
Get the boring stuff right. Then the interesting stuff gets to shine.
Lange Creative Lab builds brands that work, visually, strategically, and technically. If your website has gremlins in the backend, let’s talk.
