Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
NGINX multiple non-ssl based domains redirecting to same domain. Question Question
400 Error, Bad Request when visiting domain name, IP address loads fine Question Question

Question

www CNAME @ going to 'Park Page'

Posted June 29, 2020 415 views
NginxDNS

I set up an A record in my DNS that is @ points to the IP xxx.xxx.xx.xx and a CNAME www that points to @. The https://exchangetradedconcepts.com works the https://www.exchangetradedconcepts.com/ goes to a page that says Park Page. That seems super odd to me. has anyone encountered this? There are no files in my file system that have the words ‘Park Page’ in them.

NGINX is the web server

Add a comment
austinCoral
By:
austinCoral

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
NGINX multiple non-ssl based domains redirecting to same domain. Question Question
400 Error, Bad Request when visiting domain name, IP address loads fine Question Question

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
1 answer
alexdo June 30, 2020

Hello, @austinCoral

Looking at the DNS everything seems fine and both root www and non www are loading fine tested from my end. Can you please confirm if everything is now working as expected?

DNS changes might take up to 72 hours or even more due to ISP cache and normal DNS propagation. Unfortunately, many of those factors are our of your control. When it comes to DNS propagation there is not much you can do except of setting a lower TTL for the DNS records (A records) in order to speed up the process a bit. As mentioned usually the DNS changes take longer time due to DNS cache from all the IPSs.

Tools like https://www.digitalocean.com/community/tools/dns and https://www.whatsmydns.net can help you check if the records have been updated in various locations.

Regards,
Alex

Reply Report

Related

Looking for something else?

Ask a new question Search for more help