Configuring virtualdata.io on netlify (DNS on Route53)

Support
1

Hi there,

I think we’ve set everything up properly according to instructions to get this site:

running as www.virtualdata.io / virtualdata.io

both on route53 as well as netlify - including SSL cert install - but still getting site not found.

DNS seems to have propagated… your assistance is appreciated.

In the Netflix console I see this status:

Primary domain: Awaiting Netlify DNS

However unclear why since we are using Route53 for DNS and are configured as follows:

www.virtualdata.io. CNAME incandescent-sfogliatella-60a0e6.netlify.app
@.virtualdata.io A 75.2.60.5

Thanks,
Jordan

2

@jordanvdc Your site loads fine for me, both via the apex and www (redirected to apex).

You might just be dealing with the DNS propagation, which you could check from multiple locations using a tool like this: https://www.whatsmydns.net

image
image1625×1191 362 KB

3

Indeed it works! Actually found the issue was I set @virtualdata.com instead of virtualdata.com as the A record pointing to the Netlify servers.

Last question - do I need my own SSL certificate for this site (I created one with Sectigo) or can I use Netlify’s own SSL certificate generator?

Thank you.

J.

4

Hi, @jordanvdc. It look like the Netlify managed automatic Let’s Encrypt SSL certificate was provisioned about one hour after this post was made. Netlify will automatically renew that certificate each sixty days which is thirty days before it expires.

That practice (renewing thirty days before expiration) is a Let’s Encrypt recommended best practice to give you time to troubleshoot. If a renewal fails, we will email you automatically and there is still thirty days time to fix the issue.

Everything looks good now. Please let us know if there are any other questions.