FAQ
We want to give our customers the information they need to get the most out of STACKIT’s DNS. This FAQ section answers common questions. This helps you quickly find solutions and improve your experience. We encourage you to check these FAQ before contacting our support team, as you might find your answer here.
-
Configuration
Why can't I update the SOA record?
The SOA record is automatically managed by the DNS server and updating it manually could cause issues with the zone. We want to prevent users from accidentally breaking the record, which could result in DNS resolution issues for the domain. SOA record can be edited indirectly through the zone values to ensure its correctness and proper functioning. Not all values of the SOA record are adjustable at this time.
I setup a zone and records at STACKIT DNS, but can not resolve any of them from my client. Whats wrong?
DNS is a hierarchical system. Your zone needs to be delegated from the level above. For Top-Level-Domains like example.com you need to register the domain via a registrar. To set the correct configuration at your registrars side see Zone delegation / Registrar setup
The Nameserver for Cloud1 and Cloud2 were changed in the documentation. Which should I use now?
We updated the Hostnames for our public Nameservers to: ns1.stackit.cloud and ns2.stackit.zone to have an additional redundancy at TLD level. Feel free to update your NS records and the delegation to the new hostnames to benefit from it.
Can I create a reverse record (PTR) for a public IP that is assigned to my server?
Yes, please request the record in the the STACKIT Help Center with the information of the public IP and the content of the PTR record.
Can I create a reverse DNS (PTR) record for a public IP assigned to my server?
Yes, you can request a reverse DNS (PTR) record for your public IP. Please submit your request through the STACKIT Help Center, including the following information:
- The public IP address
- The desired PTR record content
-
General information
What is a DNS Resolver?
A DNS server resolving recursive DNS queries on behave of a client.
What is a DNS?
A DNS (Domain Name System) is a hierarchical decentralized naming system that maps domain names to IP addresses and other resource records on the internet.
How does DNS work?
DNS works by translating human-readable domain names into IP addresses that computers can understand.
Why should I use the STACKIT DNS Resolver?
The primary benefits are data sovereignty and security. By using the STACKIT resolver, your DNS traffic remains within our sovereign cloud, preventing your query data from being collected by third-party providers. This enhances your privacy and security posture..
How do I use the STACKIT DNS Resolver?
The resolver IPs for queries via UDP and TCP are
192.214.161.5345.141.74.345.141.74.153The DoH endpoint is:https://dns.stackit.cloud/dns-queryCheck out Create and manage DNS Resolver for more details.
Why should I use DNS?
DNS is essential for navigating the internet and accessing websites and other online resources.
What is a zone?
A DNS zone is a portion of the domain name space that is managed by a specific organization or administrator. It contains information about the resource records for the domain names within that zone.
Who should use the STACKIT DNS Resolver?
The STACKIT DNS Resolver is currently designed for use with STACKIT products and projects.
Does the resolver perform DNSSEC validation?
Yes. The STACKIT DNS Resolver performs DNSSEC validation to protect you from DNS spoofing and ensure that the DNS responses you receive are authentic and have not been tampered with.
What zones are supported?
We support zones of type primary and secondary. Both forward and reverse zones.
The resolver still shows old data (because of caching), how I can refresh it?
The STACKIT DNS Toolbox offers a flush functionality. Query for the record in question and click Flush Record.
What is a primary zone?
A primary zone is a read/write zone that is stored on a primary DNS server. The primary DNS server is authoritative for the zone and is responsible for maintaining the zone’s resource records.
How does systemd-resolved interact with `/etc/resolv.conf`?
On modern Linux, systemd-resolved manages DNS. The /etc/resolv.conf file is now just a link to a local stub resolver (127.0.0.53). This stub forwards all DNS queries to the actual servers configured in /etc/systemd/resolved.conf. Therefore, do not edit /etc/resolv.conf directly, as the system will overwrite your changes.
What is a secondary zone?
A secondary zone is a read-only copy of a primary zone that is stored on a secondary DNS server. The secondary DNS server receives updates from the primary DNS server and is responsible for answering queries for the zone when the primary DNS server is unavailable.
Is the resolver also available via IPv6?
No, currently not. The STACKIT DNS Resolver is currently designed for use with STACKIT products and projects, which also not offer IPv6 at the moment.
What is a reverse zone?
A reverse zone is used for mapping IP addresses to domain names. Unlike forward zones, which map domain names to IP addresses, reverse zones map IP addresses to domain names. Reverse zones are used primarily for troubleshooting and diagnostic purposes.
What is a record set?
A record set is a collection of DNS records that share the same name and record type. For example, all A records for a specific hostname would be part of the same record set.
What is the TTL value and how does it affect DNS resolution?
The TTL (Time To Live) value is a setting that determines how long a DNS record can be cached by a resolver or caching server. A longer TTL means that the record will be cached for a longer period of time, while a shorter TTL means that the record will expire more quickly and need to be refreshed more frequently.
How long does it take for DNS changes to propagate?
DNS changes can take anywhere from a few minutes to several hours to propagate, depending on a variety of factors such as the TTL value of the affected records, the number of DNS servers involved, and the caching behavior of intermediate servers. In some cases, it may take up to 48 hours for changes to fully propagate across the internet.
What is a DNS cache and how does it affect DNS resolution?
A DNS cache is a temporary storage of DNS records that are accessed frequently by a resolver or caching server. The cache helps to reduce DNS lookup times and improve overall performance, but it can also cause problems if cached records are out of date or incorrect.