Domain, DNS, or Hosting: Who Do You Call When Your Website Breaks?

When a website breaks, the right party to call depends on which of three layers failed: your domain registrar, whoever controls your DNS, or your hosting provider. The fastest way to tell them apart is the symptom. A total outage where email is also dead points to the domain or DNS. A site that loads but is slow or shows an error points to hosting. A broken page or form points to the website itself.

First, work out which layer broke

A website is really three separate services stacked on top of each other, and each is usually bought from a different company.

Your domain is the name people type. Your DNS is the directory that points that name at a server. Your hosting is where the site's files actually live.

Naming the broken layer tells you who to call.

The quickest clue is what still works. If both the website and email are dead, the fault is usually high up, at the domain or DNS. If the site loads but one feature is broken, the fault is down in the website itself.

This table maps the common symptoms to the layer and the party who can fix it.

Symptom	Likely layer	Who to call
Site and email both down	Domain or DNS	Registrar, or whoever holds your nameservers
"This domain has expired" page	Domain	Your registrar
Site won't load, email fine	Hosting or a DNS record	Host, or whoever edits your DNS
Site loads but is slow or errors	Hosting	Hosting provider
A page, form, or feature is broken	The website	Your developer
Email stopped, website fine	DNS mail record or mail host	Mail host, or DNS controller

Domain problems go to your registrar

A domain problem is one where the name itself stops working, and it goes to the registrar you rent the name from. The classic sign is a page from your registrar saying the domain has expired, or the address failing to resolve at all.

The usual cause is a lapsed renewal, not a technical fault.

For a .my name, the registrar is a company accredited by MYNIC, the .my registry. For a .com, it is whichever registrar you bought the name through. If you are not sure who that is, a WHOIS lookup on the domain usually names the registrar.

The first thing we check when a whole domain goes dark is the renewal date. A pattern we see is a business that renews late because the reminder went to an email address nobody still reads.

DNS problems go to whoever controls your nameservers

A DNS problem is one where the domain is fine but it points to the wrong place, or nowhere, and it goes to whoever controls your nameservers. That might be your registrar, your host, or a separate DNS provider such as Cloudflare. Control follows the nameservers your domain is set to use.

These faults often appear right after a change. Someone edits a record, or a site moves to a new host, and the change takes time to show everywhere, because servers keep cached copies of the old record. That delay is called propagation. A record edit usually shows within its TTL, the time servers may cache it, while a nameserver change can take up to 24 to 48 hours, Namecheap notes.

If the website went down straight after a migration or a record edit, DNS is the first place to look. The person who made the change is the person to call.

Hosting and website problems are two different calls

Hosting and website faults both let the domain resolve, so people confuse them, but they go to different people.

A hosting fault is about the server. The site is very slow, times out, shows a 503 error, or reads "account suspended." That call goes to your hosting provider. A slow site is often a hosting-headroom problem rather than a broken one.

A website fault is about the files themselves. The server is fine, but a page 404s, a contact form fails, or a feature stops after an update. That call goes to your developer, because the fix is in the code or content, not the server.

Telling the two apart saves a wasted call. If every page is affected at once, suspect hosting. If one page or feature broke while the rest works, suspect the website.

The real problem is usually not knowing who holds the accounts

The hardest outages to fix are not technical, they are the ones where nobody can say who controls each layer. We have seen businesses locked out of their own domain because a former vendor registered it under the vendor's name. When that happens, the right person to call is unknown, and the fix stalls before it starts.

Sort this out before you need it. Keep a short record of who holds the domain, the DNS, the hosting, and the website login, and make sure each account is registered in your business's name. Our website handover checklist lists exactly what to collect.

Frequently asked questions

Why is my email down but my website still works?

Because email and the website are routed by different DNS records, so one can fail while the other runs. Your site is pointed at a server by an A record, while email is routed by a separate MX record to your mail host. A mistake or change to the MX record, or a problem at the mail host, takes down mail while the website loads normally. Start with whoever controls your DNS or your mail service.

How do I find out who my hosting provider is?

Check who you pay each year, then confirm with a lookup. Your bank or card statement usually names the host or registrar you renew with. If the records are lost, a WHOIS lookup names the registrar, and a tool that checks a domain's DNS records can reveal the host behind it. If a vendor set everything up, ask them in writing for the account details, in your name.

My website shows "This domain has expired". What do I do?

Contact your domain registrar and renew immediately. An expiry page means the domain lapsed, not that the site was hacked or the host failed. Renew inside the grace period and the name usually comes back at the normal price.

Wait longer, and for a .my name MYNIC says "you will be charged a redemption fee in addition to the renewal fee of one year". Your files and hosting are usually untouched. Our guide to what happens when a domain expires covers each stage.

Who do I call if I don't know who built my website?

Start with whoever holds the logins, since control matters more than who wrote the code. If the original developer is gone, any competent web developer can take over a site once they have access to the hosting and the domain. The blocker is almost never the code, it is missing account access, which is why owning your domain and hosting in your own name matters so much.

Can one company handle the domain, DNS, hosting, and the website?

Yes, and for most small businesses that is simpler. Keeping all four with one provider, or one agency that manages them for you, means a single call when something breaks. The one rule that still applies is ownership: every account should be registered in your business's name, so you can move to another provider if you ever want to.

Is a slow website always a hosting problem?

No. Slow loading can come from weak hosting, but also from heavy images, bloated code, or a missing CDN, so it is not automatically the host's fault. Uniform slowness across the whole site points to hosting; certain heavy pages dragging while light ones stay fine points to the site. Our guide to why a website is slow walks through the usual causes.

Knowing who to call before you need to

Storming Solutions builds custom-coded websites and maintains existing WordPress sites for Malaysian businesses. Part of that work is making the whole stack legible, so you always know which layer is which and who controls it. We set up domains, DNS, and hosting in the client's name, never our own, so an outage is never made worse by a missing login.

Not sure who holds your accounts, or stuck with a site that is down right now? Message us on WhatsApp or start by confirming which domain you should own. Our web development work sets the foundation up cleanly, in your name, so problems are quick to place and quick to fix.