TXT record ins't propagation with name "_acme-challenge"

Help
1

I’m problem to configurate SSL in my domain quasebuda.com that is hosted in Godaddy.
When configured a TXT like this:

TXT _acme-challenge.quasebuda.com PUhUPUz... 600 segundos

There ins’t propagation, but when configured a TXT like this:

TXT @ PUhUPUz... 600 segundos

There is propagation, but certbot can not verify my domain because not have the name “_acme-challenge.quasebuda.com” and yes the name “.quasebuda.com” that is the same that “@” in my case.

So, I’m searching in the web and finded that should configure the name to “_acme-challenge.quasebuda.com” and yes to “_acme-challenge.cam”, like this:

TXT _acme-challenge.cam PUhUPUz_Dqm6tmjpV_6jrzqwujHoXgzGopK85s8bXD0 600 segundos

There ins’t propagation. So I’m tryed also:

TXT _acme-challenge PUhUPUz_Dqm6tmjpV_6jrzqwujHoXgzGopK85s8bXD0 600 segundos

and also there ins’t propagation.

I don’t know what to try anymore.

Sorry if my english is wrong. I’m study english and I’m tryed not using google translation. You can correcting me, it help me.

2

Hi @quasebuda

checking your domain there is no correct and no wrong TXT entry visible - https://check-your-website.server-daten.de/?q=quasebuda.com#txt

com
com1127×424 15.1 KB

Create one new entry, then recheck the domain.

If you want to create a certificate with the main domain name, the first blue marked part should have a value. Or two, if you want to create a wildcard.

The second blue marked -> value, if you want to create a certificate with the www-domain name.

1 Like
3

but I set up:

TXT _acme-challenge.quasebuda.com PUhUPUz... 600 seconds

but ins't propagating. Only is propagated with name ".quasebuda.com" in TXT.

4

That's the wrong name, that doesn't help.

Where do you create these entries? Perhaps it's the wrong place.

Share a screenshot of that menu.

Or is it possible that GoDaddy blocks these _acme-challenge entries?

Check the output of my own domain - https://check-your-website.server-daten.de/?q=server-daten.de#txt

definition
definition1127×409 14.8 KB

That's the required output to confirm one wildcard *.server-daten.de (server-daten.de is confirmed via http-01 validation, so only one entry is required and created).

5

Look:

godady-print-registros
godady-print-registros.png1105×644 41.2 KB

but I already tried configure the TXT with name “_acme-challenge.quasebuda.com” or “_acme-challenge” or “_acme-challenge.cam”, and none those worked. Only “.quasebuda.com” is worked.

6

That

is correct - https://check-your-website.server-daten.de/?q=cam.quasebuda.com#txt

com
com1136×317 12 KB

But that's the domain name if you want a certificate with the domain name

cam.quasebuda.com.

7

I’m change to:

godady-print-registros2
godady-print-registros2.png1032×132 7.67 KB

right?

8

Use the online tool to check your domain and to see, if the TXT value is visible.

9

Ok, thanks.

I’ll wait until propagate, I think this will work, I was looking here:

but it never propagate, but as it showed me that with name “.cam” was ok, I think removing it will work, let’s wait to confirm.

10

That record exists now.

_acme-challenge.quasebuda.com. 600 IN   TXT     "PUhUPUz_Dqm6tmjpV_6jrzqwujHoXgzGopK85s8bXD0"
1 Like
11

Still not, look:

12

It still exists. That check is a few hours old.

13

Click the button "Check" to start a recheck of your domain. Your older result - 41 seconds required to query all informations.

1 Like
14

True, now is ok. Got it generation the certification now.

Thanks all.

2 Likes
15

But I’m receiving NET::ERR_CERT_COMMON_NAME_INVALID to the certification.

16

There is a gitlab certificate installed, so the domain name is wrong.

How do you install your certificate?

What’s the client you use?

17

I am using certbot, and then copying the full and private key to my gitlab page in the gitlab pages settings.

18

Gitlab had already set up a certificate for my domain, so I left theirs on, and now it works.

1 Like
19

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.