DNS configuration problems can prevent your site from loading through Pressidium EDGE.

Use this guide to check whether your domain is pointing to the correct records, whether DNS is resolving as expected, and whether the issue is related to configuration rather than propagation.

What this guide covers

This guide helps you troubleshoot:

  • Incorrect DNS records
  • Missing DNS records
  • Conflicting DNS records
  • Domains resolving to the wrong destination
  • DNS records that have not propagated yet
  • DNS-related connection issues

When to use

Use this guide when:

  • Your site does not load after DNS setup
  • Your domain still points to the previous host or service
  • Your domain does not resolve
  • The wrong IP address or CNAME appears in DNS checks
  • The root domain works but www does not, or the other way around
  • You recently changed DNS and are not sure whether the issue is configuration or propagation

Prerequisites

Before you start, make sure you have:

  • Access to your DNS provider
  • Access to the Pressidium Dashboard
  • The expected DNS values for your site
  • The domain or subdomain you want to check

Symptoms

DNS configuration problems may appear as:

  • The site does not load through the domain
  • The domain points to the wrong IP address
  • The domain does not resolve
  • www and the root domain behave differently
  • DNS lookup tools show unexpected values
  • The browser shows a connection, redirect, or SSL-related error

Check the DNS records

Open your DNS provider and review the records for the affected domain.

Check:

  • The record exists
  • The record type is correct
  • The record value matches the value shown in Pressidium EDGE
  • There are no old records pointing to a previous host
  • There are no duplicate records for the same hostname
  • The root domain and www version are both configured as needed

Common record types include:

  • A record: points a domain to an IP address
  • CNAME record: points a subdomain to another hostname

Use the DNS values shown in the Pressidium Dashboard as the source of truth for your setup.

Verify DNS resolution

After checking the DNS provider, verify what the domain actually resolves to.

For an A record, run:

dig example.com A

Or:

nslookup -type=A example.com

For a CNAME record, run:

dig www.example.com CNAME

The result should match the value expected by Pressidium EDGE.

If the result still shows the old value, the issue may be DNS propagation or cached DNS.

Check DNS propagation

If the DNS records are correct but not all locations show the new value yet, propagation may still be in progress.

DNS propagation can take up to 48 hours.

Review DNS Propagation Delays for expected timeframes, cache-clearing steps, and propagation checks.

Check for conflicting records

Conflicting DNS records can cause unpredictable results.

Check for:

  • Multiple A records for the same hostname
  • A CNAME record and another record type on the same hostname
  • Old records still pointing to a previous host
  • Incorrect www configuration
  • DNS records managed in a different DNS provider than expected

Important: Your active DNS provider is controlled by the domain’s nameservers. If you update DNS records in the wrong provider, the public DNS result will not change.

Common issues and solutions

Domain still points to the old host

Check the active nameservers for the domain and confirm you edited DNS records in the correct DNS provider.

Then check for old A or CNAME records and remove or update them as needed.

Domain does not resolve

Confirm that the required DNS record exists.

Also check that:

  • The hostname is correct
  • The record type is correct
  • The record value is not empty
  • The domain’s nameservers are active

Root domain works but www does not

Check the DNS records for both versions.

The root domain and www are separate hostnames. Each one needs the correct DNS configuration.

www works but root domain does not

Check the root domain record, usually shown as @ in many DNS providers.

Make sure it points to the expected EDGE value.

DNS is correct but the site still does not load

If DNS resolves correctly, the issue may not be DNS configuration.

Check:

  • The site is added in the Pressidium Dashboard
  • The domain is attached to the correct site
  • SSL is active or still provisioning
  • The origin is reachable
  • There are no firewall or routing issues

DNS changes were made recently

If the records were updated recently, wait for propagation.

Avoid making repeated DNS changes unless you find a clear mistake in the record value.

Verification

DNS configuration is correct when:

  • The DNS provider shows the expected records
  • Public DNS lookups return the expected values
  • The root domain and www version behave as intended
  • The Pressidium Dashboard does not show a DNS setup issue
  • The site loads through the configured domain

Need help?

Contact Pressidium Support if your DNS records look correct but the site still does not load through Pressidium EDGE.

Include:

  • Domain name
  • DNS provider
  • Current nameservers
  • DNS record type and value
  • Approximate time the DNS changes were made
  • Screenshot of DNS records
  • Screenshot of any Dashboard error
  • Result of a DNS lookup, if available

For DNS provider issues, such as records not saving or nameservers not updating, contact your DNS provider.

Where to go next