# Issue with the https certificate

**URL:** <https://answers.netlify.com/t/issue-with-the-https-certificate/87166>\
**Category:** Support\
**Tags:** netlify-dns-https-ssl\
**Created:** [March 7, 2023, 9:07am UTC](https://answers.netlify.com/t/issue-with-the-https-certificate/87166 "2023-03-07T09:07:31Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![pierobond](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/pierobond/32/48579_2.png) [@pierobond](https://answers.netlify.com/u/pierobond)\
**Post date:** [March 7, 2023, 9:07am UTC](https://answers.netlify.com/t/issue-with-the-https-certificate/87166/1 "2023-03-07T09:07:31Z")

</div>

My https certificate stopped working and I cannot figure out why.  
My netlify site is [https://marcopierobon.netlify.app/](https://marcopierobon.netlify.app/) and I’m trying to access it via [https://www.pierobon.net](https://www.pierobon.net).

The domain is hosted on godaddy, and I’ve applied the suggested CNAME dns entry

 ![image](https://global.discourse-cdn.com/netlify/original/3X/4/9/4950d6f36d7d4f053612b524bdaededeada89b25.png)

In the netlify control panel I don’t see any error.

Yet, when I try to access [https://www.pierobon.net](https://www.pierobon.net) I get an invalid certificate error.

What am I doing wrong?

---

<div class="post-metadata">

**Author:** ![Melvin](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/melvin/32/23606_2.png) [@Melvin](https://answers.netlify.com/u/Melvin)\
**Post date:** [March 7, 2023, 10:40am UTC](https://answers.netlify.com/t/issue-with-the-https-certificate/87166/2 "2023-03-07T10:40:26Z")

</div>

HI @pierobond,

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

I see you have configured Netlify DNS for the domain here:

> **[Netlify](https://app.netlify.com/teams/marcopierobon/dns/pierobon.net)**
>
> Start building the best web experiences in record time

However, you are using [domaincontrol.com](http://domaincontrol.com) name servers instead of the Netlify name servers.

```auto
host -t ns pierobon.net
pierobon.net name server ns69.domaincontrol.com.
pierobon.net name server ns70.domaincontrol.com.

```

I also show that you have External DNS setup for the domain:

`A Record` for `pierobon.net` pointing to `75.2.60.5`:

```auto
host pierobon.net
pierobon.net has address 75.2.60.5
pierobon.net mail is handled by 10 aspmx.l.google.com.
pierobon.net mail is handled by 20 alt1.aspmx.l.google.com.
pierobon.net mail is handled by 20 alt2.aspmx.l.google.com.
pierobon.net mail is handled by 30 aspmx2.googlemail.com.
pierobon.net mail is handled by 30 aspmx3.googlemail.com.

```

`CNAME Record` for `www.pierobon.net` pointing to `marcopierobon.netlify.app`:

```auto
host www.pierobon.net
www.pierobon.net is an alias for marcopierobon.netlify.app.
marcopierobon.netlify.app has address 34.73.83.172
marcopierobon.netlify.app has address 54.161.234.33
marcopierobon.netlify.app has IPv6 address 2600:1f18:2489:8200::c8
marcopierobon.netlify.app has IPv6 address 2600:1f18:2489:8202::c8

```

You’ll want to either use [Netlify DNS](https://docs.netlify.com/domains-https/netlify-dns/) or [External DNS](https://docs.netlify.com/domains-https/custom-domains/configure-external-dns/) and not both.

We have a Support Guide here on how to detect a inactive DNS Zone:

> [@\[Support Guide\] How to detect and fix inactive Netlify DNS zones](https://answers.netlify.com/t/support-guide-how-to-detect-and-fix-inactive-netlify-dns-zones/21742):
>
> Last reviewed by Netlify Support - July, 2025 What is an “inactive Netlify DNS zone”? First, it would help to define the term “DNS zone”. Quoting [wikipedia](https://en.wikipedia.org/wiki/DNS_zone), it says: A DNS zone is any distinct, contiguous portion of the domain name space in the [Domain Name System](https://en.wikipedia.org/wiki/Domain_Name_System) (DNS) for which administrative responsibility has been delegated to a single manager. To paraphrase, a DNS zone is a collection of all the DNS records for a production domain. When you add production domains to Netlify DNS we cre…

The solution is either to delete the DNS Zone as [outlined here](https://answers.netlify.com/t/support-guide-how-to-detect-and-fix-inactive-netlify-dns-zones/21742#solution-1-delete-the-inactive-dns-zone-8). Or to use Netlify’s name servers mentioned [here](https://app.netlify.com/teams/marcopierobon/dns/pierobon.net#name-servers). If you decide to use Netlify’s name servers, you’ll need to remove the External DNS configuration of the `A Record` pointing to `75.2.60.5` and the `CNAME Record` pointing to `marcopierobon.netlify.app`.

Having both External DNS and Netlify DNS configured can cause issues with the SSL Certificate getting generated or renewed.

Let us know if you have any questions.

---

<div class="post-metadata">

**Author:** ![pierobond](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/pierobond/32/48579_2.png) [@pierobond](https://answers.netlify.com/u/pierobond)\
**Post date:** [March 7, 2023, 4:18pm UTC](https://answers.netlify.com/t/issue-with-the-https-certificate/87166/3 "2023-03-07T16:18:06Z")

</div>

Thanks. I’ve deleted the DNS zone in netlify a couple hours ago, but I still get the same error.  
How long should it take?

---

<div class="post-metadata">

**Author:** ![SamO](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/samo/32/41847_2.png) [@SamO](https://answers.netlify.com/u/SamO)\
**Post date:** [March 7, 2023, 4:30pm UTC](https://answers.netlify.com/t/issue-with-the-https-certificate/87166/4 "2023-03-07T16:30:21Z")

</div>

Up to 48 hours. If you are still experiencing this issue in 2 days please reach back out.

---

<div class="post-metadata">

**Author:** ![Melvin](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/melvin/32/23606_2.png) [@Melvin](https://answers.netlify.com/u/Melvin)\
**Post date:** [March 7, 2023, 4:56pm UTC](https://answers.netlify.com/t/issue-with-the-https-certificate/87166/5 "2023-03-07T16:56:30Z")

</div>

Hi @pierobond,

Thanks for the follow-up. You should be all set with the SSL Certificate.
