WWW subdomain does not resolve after switch from Netlify to Github Pages

Support
1

Hi,

Netlify is an awesome service, but we found it necessary to switch back to GitHub Pages for our play-project.org. We deactivated the build flow and deleted it, and then changed DNS records at Name.com according to the GitHub Pages instructions.

play-project.org resolves, but the www.play-project.org does not. There is an appropriate CNAME entry our DNS configuration on Name.com.

The response from the dig command looks right to my novice eye.

In some cases, we get a Site Not Found error and the following Netlify Internal ID: 01HTJWY7ERPJ5GCQBC9QJV46XS

I have not posted elsewhere, as this seems to be a specific problem with the way we transferred where we were hosting the domain.

Any help is appreciated!

2

It does resolve. Without SSL. It redirects to the apex domain.

This is what I see

$ dig www.play-project.org
www.play-project.org.	377	IN	CNAME	play-project.org.
play-project.org.	377	IN	A	185.199.108.153
play-project.org.	377	IN	A	185.199.109.153
play-project.org.	377	IN	A	185.199.110.153
play-project.org.	377	IN	A	185.199.111.153

According to GitHub Pages Configuring a subdomain point #5:

For example, if you want to use the subdomain www.example.com for your user site, create a CNAME record that points www.example.com to <user>.github.io.

You have not done this as shown by the output above.

DNS record changes take time to propagate Understanding domain propagation - Name.com Knowledge Base

This is not an issue with Netlify in any way. It is between you, Name܂com and GitHub.

3

You are right. Thank you for pointing out my error! And so quickly.