Resolving multiple domains to the same project

Support
,
1

Hi,
I am hosting nowpresent.co as my primary domain, and www.nowpresent.co as an alias.
When I go to the domain-management admin section, I get the error
nowpresent.co doesn't appear to be served by Netlify

i also intermittently see “Preparing your domain…” on the nowpresent.co record.

I also want to host the domain nowpresent.com and www.nowpresent.com on the same project. I added the DNS record A 75.2.60.5 on the apex record of nowpresent.com.

I have performed all the troubleshooting steps, and can’t figure out why the SSL is not getting set, why I get the intermittent “Preparing your domain…”, or why the nowpresent.com domain is not resolving correctly.

My DNS hosting is on Amazon R53:

  1. For nowpresent.co
  • NS
    • dns1-dns4 p06 nsone
  • A
    • 75.2.60.5
  • CNAME subtle-axolotl-44c5d1.netlify.app
  1. For nowpresent.com
  • NS
    • dns1-dns4 p06 nsone
  • A 75.2.60.5
  • CNAME subtle-axolotl-44c5d1.netlify.app

THe issue I’m having is that nowpresent.com does not resolve at netlify:
$ curl -s -v http://nowpresent.com 2>&1 | grep -i server
returns nothing

And www.nowpresent.com does not serve SSL. Neither apex nor www do not show up in the SSL/TLS Certificate list in “domain-management”. I have Domains: nowpresent.co, www.nowpresent.co

I added nowpresent.com as “domain alias”, since that seemed correct. I don’t want it to be the primary domain.

I’m certain I’m just misunderstanding something in the configuration. Would appreciate any help.

Thanks!

2

Hi, @nowpresent. This appears to have auto-resolved (meaning, I took no action to fix it) around 12:09 pm PST today. The SSL is working for both www and apex now.

If there are follow-up questions, please let us know.

3

hi @luke
https://nowpresent.com still does not resolve for me. I just tried:
root@chai2104:~# curl nowpresent.com curl: (6) Could not resolve host: nowpresent.com

My DNS A record for nowpresent.com is 75.2.60.5. And SSL certificate is still not being served for www.nowpresent.com:

curl: (60) SSL: no alternative certificate subject name matches target host name 'www.nowpresent.com'
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

Please note that the issue is with the .com (not with .co).

Thanks for your support!

4

A screenshot of my domain-management page is here.

5

It looks like some of the required records for the dns zone were missing. I’ve just recreated those records, the site is back up-and-running.

6

Hi @sid.m
Thanks so much for your help. Please could you tell me which records were added? I don’t see any change in the domain-management screen, but maybe I’m looking in the wrong place.

SSL is still failing for both the apex and www domains:

$ curl https://nowpresent.com
curl: (60) SSL: no alternative certificate subject name matches target host name 'nowpresent.com'
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

$ curl https://www.nowpresent.com
curl: (60) SSL: no alternative certificate subject name matches target host name 'www.nowpresent.com'
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

I also don’t see letsencrypt entries for these domains. My current domains list is: Domains nowpresent.co, www.nowpresent.co

Thanks so much for your support!

7

It’s all working now. I guess it just needed some time? Please let me know if I missed a configuration or DNS entry (or point me to documentation) so I can make a note for next time.

Thanks for the very quick support!

8

Hi, @nowpresent. It is hard to say what the cause was without details collected during the issue and I don’t see the required information posted anywhere here. My best guess is that is was DNS caching related and there is more about this here: