---
title: "Shopify shows Invalid DNS behind an edge proxy - Serpwise"
description: "Understand why Shopify can show an Invalid DNS warning when a storefront runs through an edge proxy, how to verify the route, and which records not to change."
url: "https://serpwise.ai/learn/shopify-invalid-dns-warning/"
source: "https://serpwise.ai/learn/shopify-invalid-dns-warning/"
---
[← Back to Learn](/learn/)

DNS & Hosting Info

# Shopify shows Invalid DNS behind an edge proxy

Understand why Shopify can show an Invalid DNS warning when a storefront runs through an edge proxy, how to verify the route, and which records not to change.

Your Shopify admin shows a red **Invalid DNS** next to your custom domain, and **Domain isn’t live**. Meanwhile the storefront loads, customers check out, and orders come in. Both things are true at once, and the warning is permanent as long as your store runs through Serpwise.

This is expected. Here’s exactly why, and what happens if someone on your team tries to “fix” it.

## Why Shopify says this

Shopify’s domain checker is a pure DNS comparison. It resolves your records and checks them against two hard-coded values:

| Record          | Type  | Value Shopify expects |
|-----------------|-------|-----------------------|
| `www`           | CNAME | `shops.myshopify.com` |
| `@` (apex/root) | A     | `23.227.38.65`        |

When your store runs behind an edge proxy, `www` intentionally points at your Serpwise edge hostname instead. The checker sees a value it doesn’t recognise, and reports **Invalid DNS** plus **Domain isn’t live**.

That’s the whole mechanism. Shopify is not probing your storefront, measuring uptime, or testing checkout. It is string-matching a DNS record.

This happens with **any** edge or reverse proxy in front of a Shopify store, not just Serpwise. There is no Shopify setting, theme flag, or API call that suppresses the warning. It stays red.

## The store is not down

The traffic path is unchanged from the visitor’s perspective:

```
Visitor → www.example.com (DNS) → Serpwise edge → shops.myshopify.com → Shopify
```

Serpwise receives the request, forwards it to Shopify with the correct host header so Shopify serves your store rather than a 404, applies your SEO rules to the HTML, and returns the response. Storefront rendering, cart, discount codes, and checkout behave exactly as they did before.

TLS for the domain is terminated at the Serpwise edge. Shopify’s own TLS row in the Domains screen typically still shows green because Shopify continues to hold a certificate for the domain even though it isn’t the one visitors are served.

## SEO impact: none

Search engines and AI crawlers resolve DNS the same way visitors do. They reach the Serpwise edge, get a `200`, and see the optimized HTML, including canonicals, structured data, meta robots, and any other rules you’ve configured.

The **Invalid DNS** label is a string in the Shopify admin UI. Googlebot, GPTBot, and PerplexityBot never see it, and there is no ranking or indexing signal attached to it.

## What not to do

Two actions look like fixes and are not.

**Don’t click “I have updated the DNS records”.** It re-runs the same comparison against the same two hard-coded values. Your `www` record still points at the edge, so it fails again and the warning returns. Clicking it changes nothing.

**Don’t change the `www` CNAME back to `shops.myshopify.com`.** This is the one that actually costs you something. It removes Serpwise from the request path:

- Traffic goes straight from the visitor to Shopify.
- Every rule you’ve configured stops being applied, including canonicals, injected JSON-LD, meta rewrites, and header changes.
- The store keeps working. Nothing breaks, no downtime, no lost orders. You simply fall back to plain, unoptimized Shopify.

The failure mode is silent. The site looks fine; the edge SEO layer is just gone. Someone usually notices weeks later when structured data disappears from a crawl report.

## The correct records

Steady state for a Serpwise-fronted Shopify store:

| Record          | Type  | Value                                                      | Handled by |
|-----------------|-------|------------------------------------------------------------|------------|
| `www`           | CNAME | your Serpwise edge target (Serpwise dashboard → DNS panel) | Serpwise   |
| `@` (apex/root) | A     | `23.227.38.65`                                             | Shopify    |

The apex stays on Shopify deliberately. Shopify serves the apex-to-primary-domain redirect, so `example.com` still sends visitors to `www.example.com`, which is where Serpwise is.

Verify with `dig`:

```
dig +short www.example.com CNAME
# expected: your Serpwise edge hostname

dig +short example.com A
# expected: 23.227.38.65
```

## If someone already reverted it

Restoring takes one record change:

1. Open the Serpwise dashboard, go to the domain, open the **DNS** panel.
2. Copy the edge target shown there. It is specific to your domain, so don’t reuse one from another store.
3. In your DNS provider, set the `www` CNAME back to that value.
4. Leave the apex `A` record on `23.227.38.65`.

Propagation is bound by the TTL on the record you just changed. Rules resume applying as soon as traffic reaches the edge again.

## Confirm the store is healthy

If you want proof the warning is cosmetic rather than taking it on faith:

```
curl -sI https://www.example.com/ | head -1
# HTTP/2 200
```

Then check that one of your rules is present in the served HTML, such as the canonical or an injected JSON-LD block:

```
curl -s https://www.example.com/products/example \
  | grep -oE '<link[^>]*rel="canonical"[^>]*>'
```

A `200` plus your rule output in the HTML means the edge is in the path and working. Your Serpwise dashboard showing live request volume for the domain is the same signal from the other side.

## Tell whoever owns your DNS

The realistic risk here is not the warning. It is a well-meaning developer, agency, or ops contractor opening the Shopify admin, seeing red, and reverting the CNAME to make it green.

Send them this page. Add a note in your DNS provider’s record comment field if it supports one:

```
www CNAME <serpwise-edge-target>  # Serpwise edge - do NOT revert to shops.myshopify.com
```

That one comment prevents the most common way stores silently lose their edge SEO layer.

[See pricing](/pricing) or run a [free AI visibility audit](/audit).

From diagnosis to deployment

## Find the issue. Ship the fix.

Use Learn to understand the problem, then run Serpwise against your own site to see what can be approved and deployed.

[Run free audit](/audit/) [Book a demo](/demo/)