HomeDNS setup › Netlify

DNS setup

Point img.yourdomain.com
at the relay on Netlify

One CNAME record is all this takes. It serves your images from your own hostname and removes the corner note on Premium.

Step 1

Open the DNS editor

Domains → the domain → DNS recordsAdd new record.

Panel wording changes from time to time. If what you see does not match, look for anything called DNS, Advanced DNS, Zone Editor or DNS Records — they are the same thing. The documentation from Netlify is linked above and is always the authority.

Step 2

Add the record

TypeCNAME
Nameimg — just this, Netlify adds your domain
Valueimg.youcansecureit.com
TTLLeave the default (or 1 hour / 3600)

Worth knowing on Netlify:

Step 3

Check the record is live

DNS changes are usually visible within a few minutes, though registrars are allowed to take up to 24–48 hours. You do not have to wait to find out — ask the internet directly:

dig +short img.yourdomain.com

On Windows, nslookup img.yourdomain.com does the same job. You are looking for img.youcansecureit.com in the answer. Until the record has propagated you will get nothing back, which is normal and not an error.

Step 4

Tell the plugin

In WordPress, open Settings → Image Relay and enter img.yourdomain.com. The relay checks the DNS itself, provisions the hostname and issues an SSL certificate for it — usually live within about fifteen minutes.

From then on your images are served from your own hostname, with no corner note. If the DNS record ever disappears the relay notices within 24 hours and quietly falls back to the shared domain, so your images never break.

If it does not work

The four things that actually go wrong

A record already exists for img

A leftover A, AAAA or CNAME record on the same name wins over the one you just added. Delete the old row rather than adding a second.

The full hostname was typed into the name box

Most panels append your domain automatically, so img.yourdomain.com becomes img.yourdomain.com.yourdomain.com. If dig shows a doubled domain, that is the cause.

The domain is not using these nameservers

Editing DNS at your registrar does nothing if the nameservers point somewhere else — a host, or Cloudflare. Check with dig +short NS yourdomain.com and edit wherever that points.

It is proxied rather than resolved

Cloudflare's orange cloud, and similar “web forwarding” options elsewhere, hide the real DNS answer. The relay cannot verify the hostname and the certificate will not issue. Set the record to DNS only.

Not on Netlify?

The record is identical everywhere — only the panel differs. We have step-by-step pages for thirty registrars and hosts.

Home · Get started · DNS setup · Acceptable use policy · Copyright / DMCA notices · Blocked sources