ironcore-dev / ironcore-dev/roadmap
IronCore DNS Service (static / manually configured entries)
Open
@peanball is already working on this.
Since Jul 23, 2026.
area/iaas
area/ironcore-api
area/networking
kind/roadmap
- Dominant language
- Shell
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Summary
IaaS providers offer DNS configuration for hosted zones (i.e. subdomains of an existing domain) via UI and API. Using the IronCore DNS service, operators can configure the responses of DNS servers for specific queries.
Scope
In Scope
- DNS Server is provided and can be deployed that can be configured via IronCore DNS CRDs for hosted zones (delegated DNS paths) and their respective base DNS entries of different types. Initially: A, AAAA, CNAME, SRV, TXT, NS, MX. This list can be extended as needed.
- Documentation of common scenarios
Out of Scope
- Kubernetes-managed names for e.g. nodes, endpoints, services, and IronCore specific resources such as Load Balancers are mappable to DNS names.
- Custom integration with other software (e.g. LetsEncrypt, etc)
- DNSSec
- DNS-over-HTTP{,2,3}
Acceptance Criteria
- a DNS server for IronCore is available
- Definition, for which scope each DNS Service is responsible (a single region, or all IronCore zones for a particular operator)
- Redundancy/High availability are addressed
- Users can control the responses by creating CRDs
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.