Hi, @andrewharmer. With the current DNS configuration, everyone in the world goes to San Francisco and no CDN is used at all. This is the current DNS configuration for this site:
flexitreks.com. 300 IN A 104.198.14.52
For the www
subdomain no DNS records exist:
$ dig www.flexitreks.com
; <<>> DiG 9.10.6 <<>> www.flexitreks.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 53691
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.flexitreks.com. IN A
;; AUTHORITY SECTION:
flexitreks.com. 900 IN SOA ns-1907.awsdns-46.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
;; Query time: 66 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Jan 02 19:23:04 PST 2023
;; MSG SIZE rcvd: 131
That shows the start of authority (SOA) record which indicates the request record (for www.flexitreks.com
) for not exist.
This means no CDN is being used. All site traffic goes to a single IP address near San Francisco.
To resolve this, two changes are required.
1. The DNS record below must be created (while replacing <site subdomain here>
with the correct subdomain):
www.flexitreks.com. 1800 IN CNAME <site subdomain here>.netlify.app.
So, if the site’s subdomain is example
(meaning example.netlify.app
), then the CNAME type DNS record would be this:
www.flexitreks.com. 1800 IN CNAME example.netlify.app.
2. The site’s primary custom domain (found under Site Name > Settings > Domain management > Custom domains) would need to be changed from flexitreks.com
to www.flexitreks.com
.
To summarize, first the CNAME record for the www
subdomain should be created and ten the site’s primary custom domain must be changed from flexitreks.com
to www.flexitreks.com
. If both of those changes are made, the site performance will improve drastically as people will be directed to their closest CDN node geographically. This means that people in Australia will be directed Australian CDN nodes, people in the EU will be directed to EU CDN nodes, etc.
If that doesn’t resolve the issue or if there are questions, please let us know.