Error directing DNS CNAME to Netlify URL

Support
,
1

  • we need to know your netlify site name. Example: gifted-antelope-58b104.netlify.app
    https://offergizmo3dprinters.netlify.app/

  • DNS issues? Tell us the custom domain, tell us the error message! We can’t help if we don’t know your domain.
    My DNS is with Wix
    I created a DNS CNAME entry offer.gizmo3dprinters.com.au that should go to offergizmo3dprinters.netlify.app

When I test offer.gizmo3dprinters.com.au I get this error ( Netlify Internal ID: 01GVC6Y0BRABG6BVX8WFCWT1YG)
https://disk.yandex.com/i/-p1yppv9vNa8gw
When I go directly to the Netlify URL it works fine

Please tell me what I am doing wrong.

2

Have you added offer.gizmo3dprinters.com.au as a custom domain to your site?

See Assign a domain to a site documentation.

1 Like
3

Hi @gizmo,

Thanks for reaching out and welcome to Netlify’s Support Forums!

I do see that you’ve configured the DNS for offer.gizmo3dprinters.com.au to have the CNAME Record point to offergizmo3dprinters.netlify.app. However, the subdomain hasn’t been added to the site here. Please assign the subdomain to the site.

Also note that the apex domain (gizmo3dprinters.com.au) and subdomain (www.gizmo3dprinters.com.au) have not had their DNS configured for External DNS. You can follow the linked Netlify doc to help with configuring the DNS, or you can follow option 1 of our Support Guide here.

4

Hi

Thank you for the help

When trying to add the name I am limited. It will always have gizmo3dprinters.com.au. I can just add something infront/sub domain

On the A record the @ sign is not accepted in the host name field

2023-03-17_13-11-16
2023-03-17_13-11-16970×545 25.4 KB

5

@gizmo An @ is for the apex/bare domain (i.e. https://gizmo3dprinters.com.au).

You need to add offer.gizmo3dprinters.com.au to the site in Netlify as a custom domain e.g.

Screenshot 2023-03-17 at 2.54.54 pm
Screenshot 2023-03-17 at 2.54.54 pm1964×988 121 KB

6

Hi, @gizmo. The domain name is working but SSL is not. The SSL is not working because you have two non-working domain names added here:

https://app.netlify.com/sites/offergizmo3dprinters/settings/domain#production-domains

The solution is:

  • remove all the domain names on the page above (all of them except the netlify.app subdomain which you cannot remove)
  • then add back just offer.gizmo3dprinters.com.au
  • then click Verify DNS configuration button at the bottom of the page
  • once the verification is complete, you may need to click it again to provision SSL

If that doesn’t resolve the issue, please let us know.

7

Hi

I removed everything then only added offer.gizmo3dprinters.com.au
I clicked on verify and it gave this message " DNS verification was successful"
When I click on “Provision certificate” it shows a message box. When I click on that it shows this message "missing certificate

Let’s Encrypt is a fully automated install. We’ll provision a TLS certificate from Let’s Encrypt and install it on our CDN."

I closed the message box and it had this
" We could not provision a Let’s Encrypt certificate for your custom domain.

Please read our troubleshooting guide for some tips on what might be happening."

The troubleshoot says
" A Record for your bare domain should point to 75.2.60.5"
What should I enter as the bare domain?

The second part has this
The CNAME record for your subdomain www should have the value [sitename].netlify.app

I do have offer.gizmo3dprinters.com.au, offergizmo3dprinters.netlify.app
I am worried if I create www.gizmo3dprinters.com.au offergizmo3dprinters.netlify.app that it will break my site.

8

There is no need to change gizmo3dprinters.com.au or www.gizmo3dprinters.com.au. The only subdomain that requires configuration for the Netlify site is offer.gizmo3dprinters.com.au. It appears this is already done as it loads, including with SSL.

Therefore, you need to do anything else. Only offer.gizmo3dprinters.com.au needed configuring as previously explained by others.

10

Thank you everyone for the help. It is working great now.

11

thanks for confirming @gizmo

12

Seems people reading this post are being naughty. They are sending test messages from the URL and that is costing me money. Could we archive this post maybe?

13

I doubt it has much to do with this post specifically.