starred/acme-dns

Fork 0

mirror of https://github.com/acme-dns/acme-dns.git synced 2026-04-27 12:55:48 +03:00

[GH-ISSUE #258] NS records with that host already exist. (Code: 81056) #131

New issue

Closed

opened 2026-03-13 15:52:15 +03:00 by kerem · 4 comments

kerem commented

2026-03-13 15:52:15 +03:00

Owner

Originally created by @sobujbd on GitHub (Feb 21, 2021).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/258

I'm bit confuse about this description - DNS Records

You will need to add some DNS records on your domain's regular DNS server:

NS record for auth.example.org pointing to auth.example.org (this means, that auth.example.org is responsible for any *.auth.example.org records)
A record for auth.example.org pointing to 198.51.100.1

On Cloudflare
I do able to add this,

Type	Name	Content
NS	acme-dns	acme-dns.example.org

But, When I'm trying to add this,

A	acme-dns	89.89.89.89

I had received NS records with that host already exist. (Code: 81056)

And If I add the DNS record such as way,

Type	Name	Content
NS	acme-dns	ns.acme-dns.example.org
A	ns.acme-dns	89.89.89.89

And set the config.cfg file

# domain name to serve the requests off of
domain = "acme-dns.example.org"
# zone name server
nsname = "ns.acme-dns.example.org"
# admin email address, where @ is substituted with .
nsadmin = "admin.ns.acme-dns.example.org"
# predefined records served in addition to the TXT
records = [
    # domain pointing to the public IP of your acme-dns server 
    "acme-dns.example.org. A 89.89.89.89",
    "ns.acme-dns.example.org. A 89.89.89.89",
    # specify that auth.example.org will resolve any *.auth.example.org records
    "acme-dns.example.org. NS ns.acme-dns.example.org.",
]

The host acme-dns.example.org could not resolve!

How do you setup this - https://toolbox.googleapps.com/apps/dig/#NS/@ns.auth.acme-dns.io.

Originally created by @sobujbd on GitHub (Feb 21, 2021). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/258 I'm bit confuse about this description - [DNS Records](https://github.com/joohoi/acme-dns/blob/master/README.md#dns-records) > You will need to add some DNS records on your domain's regular DNS server: > NS record for auth.example.org pointing to auth.example.org (this means, that auth.example.org is responsible for any *.auth.example.org records) A record for auth.example.org pointing to 198.51.100.1 On **Cloudflare** I do able to add this, Type | Name | Content ------ | ------- | --------- NS | acme-dns | acme-dns.example.org But, When I'm trying to add this, A | acme-dns | 89.89.89.89 ---- | ------- | -------------- I had received **NS records with that host already exist. (Code: 81056)** And If I add the DNS record such as way, Type | Name | Content ------ | ------- | --------- NS | acme-dns | ns.acme-dns.example.org A | ns.acme-dns | 89.89.89.89 And set the **config.cfg** file ``` # domain name to serve the requests off of domain = "acme-dns.example.org" # zone name server nsname = "ns.acme-dns.example.org" # admin email address, where @ is substituted with . nsadmin = "admin.ns.acme-dns.example.org" # predefined records served in addition to the TXT records = [ # domain pointing to the public IP of your acme-dns server "acme-dns.example.org. A 89.89.89.89", "ns.acme-dns.example.org. A 89.89.89.89", # specify that auth.example.org will resolve any *.auth.example.org records "acme-dns.example.org. NS ns.acme-dns.example.org.", ] ``` The host **acme-dns.example.org** could not resolve! How do you setup this - https://toolbox.googleapps.com/apps/dig/#NS/@ns.auth.acme-dns.io.

kerem closed this issue

2026-03-13 15:52:20 +03:00

kerem commented

2026-03-13 15:52:26 +03:00

Author

Owner

@AvrumFeldman commented on GitHub (Feb 28, 2021):

From a quick google it seems that Cloudflare doesn't support glue records. Your alternative should be working. Can you confirm that your acme-dns server is responding to queries when directly queried?

@AvrumFeldman commented on GitHub (Feb 28, 2021): From a quick google it seems that Cloudflare doesn't support glue records. Your alternative should be working. Can you confirm that your acme-dns server is responding to queries when directly queried?

kerem commented

2026-03-13 15:52:31 +03:00

Author

Owner

@sobujbd commented on GitHub (Mar 14, 2021):

@AvrumFeldman,

From a quick google it seems that Cloudflare doesn't support glue records. Your alternative should be working. Can you confirm that your acme-dns server is responding to queries when directly queried?

It's something wrong with Cloudflare. As you said, maybe it's that the Cloudflare doesn't support glue records.

This DNS setup instruction works with Namecheap DNS Hosting.

@sobujbd commented on GitHub (Mar 14, 2021): @AvrumFeldman, > From a quick google it seems that Cloudflare doesn't support glue records. Your alternative should be working. Can you confirm that your acme-dns server is responding to queries when directly queried? It's something wrong with Cloudflare. As you said, maybe it's that the Cloudflare doesn't support **glue** records. This [DNS setup instruction](https://github.com/joohoi/acme-dns/blob/master/README.md#dns-records) works with **Namecheap** DNS Hosting.

kerem commented

2026-03-13 15:52:36 +03:00

Author

Owner

@rodrigodc commented on GitHub (Sep 30, 2021):

It works with Cloudflare if you:

Set A ns-acme-dns pointing to your public IP address in Cloudflare, and
Set NS acme-dns pointing to ns-acme-dns in Cloudflare, and,
Start with the default acme-dns config.cfg, and
Adjust it for your domain name (without the ns- prefix) and public IP address.

The first and second itens work around Cloudflare's limitation NS records with that host already exist. (Code: 81056).

@rodrigodc commented on GitHub (Sep 30, 2021): It works with **Cloudflare** if you: - Set `A ns-acme-dns` pointing to your public IP address in Cloudflare, **and** - Set `NS acme-dns` pointing to `ns-acme-dns` in Cloudflare, **and**, - Start with the _default_ acme-dns `config.cfg`, **and** - Adjust it for your domain name (_without_ the `ns-` prefix) and public IP address. The first and second itens work around Cloudflare's limitation `NS records with that host already exist. (Code: 81056)`.

kerem commented

2026-03-13 15:52:41 +03:00

Author

Owner

@gruentee commented on GitHub (Oct 2, 2021):

Nice, thanks for the hint. I'll try that .

@gruentee commented on GitHub (Oct 2, 2021): Nice, thanks for the hint. I'll try that .

kerem referenced this issue

2026-03-13 16:16:52 +03:00

[PR #131] [MERGED] Add Certify The Web to clients list #311