mirror of
https://github.com/acme-dns/acme-dns.git
synced 2026-04-27 04:45:48 +03:00
[GH-ISSUE #261] Custom DNS record wildcard support #132
Labels
No labels
Documentation
Documentation
bug
enhancement
feature request
feature request
help wanted
pull-request
question
security
security
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/acme-dns#132
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Daniel-Nashed on GitHub (Apr 21, 2021).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/261
"Custom DNS records" are very useful specially for small test environments to be used instead of a larger DNS server.
It looks like an A record cannot be a wild-card entry?
Or is there any trick?
example:
*.mydomain.com. IN A 1.2.3.4If` this isn't possible today, could this be added in future? :-)
@webprofusion-chrisc commented on GitHub (Apr 21, 2021):
The primary purpose of acme-dns is to serve TXT records to satisfy acme certificate DNS validation. The limited DNS features it has are only there so that it can serve these TXT records and act as a basic (self-hosted) delegated nameserver for an authentication-specific subdomain.
What would be the benefit of providing this wildcard support within acme-dns?
@Daniel-Nashed commented on GitHub (Apr 21, 2021):
Thanks for the quick answer. that means I didn't do anything wrong..
I understand the main purpose and it works like a charm!
Wildcard DNS entries would serve the same purpose the current A records have.
In some lab environments you don't want to install a separate DNS server.
But for testing it is often helpful to resolve everything that has no own DNS record to a default host.
When you have two DNS servers in place just for that, this makes the environment more complex.
I really like that you can just add DNS entries almost like in a host file without defining your own DNS zone.
For what I need right now I can use CoreDNS in a container.
Still having wildcards, would let me use ACME-DNS only in this use case.
@webprofusion-chrisc commented on GitHub (Apr 21, 2021):
Maybe this PR? https://github.com/joohoi/acme-dns/pull/174
Looks like it needs more tests to get accepted.
@Daniel-Nashed commented on GitHub (Apr 21, 2021):
Looks good! This is exactly what I was asking for.
Wild cards are always for one domain level. That's the same for certificates.
Sounds like it needs documented test cases to get accepted.