DNS Management for Domains, Websites & Applications
Manage DNS records, connect domains to websites and applications, configure email routing, and protect your domain from one centralized DNS management environment.
DNS management is the process of creating, updating, and maintaining the DNS records that control how your domain connects to websites, email services, applications, and other online resources. Instead of changing DNS settings across separate tools, you can manage the records associated with your domains and subdomains from a centralized interface.
Use DNS records to point a domain to a web server, route email through the correct mail provider, connect subdomains to applications, verify third-party services, and configure domain security policies. Common records such as A, CNAME, MX, TXT, and NS each control a different part of how your domain communicates with internet services.
With Cloudoora DNS Management, you can manage DNS records, monitor DNS changes, configure DNS security features such as DNSSEC, review configuration history, and automate DNS updates through available management tools. This gives you greater control over the DNS configuration behind your websites, email, and applications.
Manage Your DNS →What Is DNS Management ?
DNS (Domain Name System) is the system that translates domain names into the information computers and internet services use to locate websites, servers, and other resources. DNS management is the process of creating, updating, securing, and maintaining the DNS records that control those connections. In practice, managing DNS records lets you control where your domain and subdomains point and which services they use. For example, you can point a domain to a web server with an A record, connect a hostname to another service with a CNAME record, route domain email using MX records, or verify a third-party service with a TXT record.
What Can You Manage With DNS
With Cloudoora DNS Management, you can manage these DNS configurations from a centralized environment, giving you greater control over how your domains connect to websites, email, applications, and other services.
Point a domain to a website or web server
Configure DNS records so visitors are directed to the correct hosting environment.
Connect domain email services
Use MX and related DNS records to route email and support email authentication.
Configure subdomains
Point subdomains such as www, api, mail, or application-specific hostnames to the appropriate services.
Verify domains and services
Add TXT and other supported records when third-party platforms require domain ownership verification.
Connect third-party services
Configure DNS records required by external applications, platforms, and cloud services.
Control DNS settings
Update records, adjust TTL values, review changes, and apply available DNS security controls.
Why DNS Management Matters
DNS is part of the infrastructure behind your website, email, and applications. A single incorrect or outdated DNS record can send traffic to the wrong destination, interrupt email delivery, delay infrastructure changes, or expose your domain to unnecessary security risks. Effective DNS management helps keep these connections accurate, controlled, and easier to troubleshoot.
Your DNS records determine where a domain or subdomain sends visitors and application traffic. Correct A, AAAA, and CNAME records can connect domains to the appropriate web servers, application endpoints, and hosting environments. Keeping these records accurate is especially important when moving a website, changing servers, or adding new application services.
How DNS Resolution Works
When someone enters a domain name such as example.com, the browser does not immediately know which server hosts the website. DNS resolution is the process of finding the DNS information associated with that domain and returning the address needed to reach the requested service. The lookup typically moves from the user's device and DNS resolver through the DNS hierarchy until an authoritative DNS server provides the record for the domain. The result is then returned to the browser or application, which can connect to the destination.
Browser & DNS Resolver
The browser first checks available local DNS information, such as its cache. If it does not have a usable answer, the device sends the DNS query to a DNS resolver, usually provided by an internet service provider, network administrator, or public DNS service.
The resolver is responsible for finding the authoritative answer on behalf of the user.
Root & TLD Name Servers
If the resolver does not already have the required information cached, it follows the DNS hierarchy. The root name servers direct the resolver toward the appropriate Top-Level Domain (TLD) name servers, such as the servers responsible for .com, .org, or .net.
The TLD servers then identify which authoritative name servers are responsible for the requested domain.
Authoritative DNS Server
The resolver contacts the domain’s authoritative DNS server, which holds the actual DNS records for that domain. Depending on the request, this may return an A, AAAA, CNAME, MX, TXT, or another DNS record.
For a website, an A or AAAA record can provide the IP address needed to reach the hosting server.
DNS Response
The authoritative answer is returned to the DNS resolver, which sends the result back to the user’s device. The browser can then use the returned IP address to establish a connection with the website or application.
The resolver may cache the DNS response according to the record’s TTL, allowing subsequent requests to be answered more quickly without repeating the entire DNS lookup.
Manage Common DNS Records
Managing DNS effectively starts with understanding what each record controls. DNS records tell resolvers where your domain, subdomains, email services, and other online resources should connect. Choosing the correct record type helps you point domains to servers, route email, verify services, and control DNS behavior without unnecessary configuration changes.
A Record — Point a Domain to an IPv4 Address
An A record connects a domain or subdomain to an IPv4 address. It is commonly used to point a website or application hostname to the IPv4 address of its hosting or cloud server.
Example use: Point example.com to the IPv4 address of your web server.
AAAA Record — Connect a Domain to an IPv6 Address
An AAAA record points a domain or subdomain to an IPv6 address. Use it when your website, application, or server is reachable over IPv6.
Example use: Connect app.example.com to an application’s IPv6 address.
CNAME Record — Point One Hostname to Another
A CNAME (Canonical Name) record makes one hostname an alias of another hostname. It is useful when a subdomain needs to follow the destination of another domain name rather than pointing directly to an IP address.
Example use: Point www.example.com to example.com or connect a subdomain to a hostname provided by a third-party service.
MX Record — Route Email for Your Domain
An MX (Mail Exchange) record specifies which mail servers receive email for your domain. When changing email providers or setting up business email, the correct MX records are essential for directing incoming messages to the intended mail service.
Example use: Configure your domain to deliver email to your business email provider.
TXT Record — Verify Domains and Configure Email Policies
A TXT record stores text-based DNS information used for purposes such as domain verification, email authentication, and service configuration. TXT records are commonly used with SPF-related email policies and verification codes provided by third-party platforms.
Example use: Add a verification value to prove domain ownership or configure an email authentication policy.
NS Record — Identify Authoritative DNS Servers
An NS (Name Server) record identifies the authoritative name servers responsible for a domain’s DNS configuration. When a domain uses a particular DNS provider, its authoritative name servers determine where the domain’s DNS records are managed.
Example use: Delegate DNS management for a domain to the appropriate authoritative name servers.
CAA Record — Control Certificate Issuers
A CAA (Certification Authority Authorization) record specifies which certificate authorities are authorized to issue SSL/TLS certificates for a domain. This provides an additional control over certificate issuance and can help reduce the risk of an unauthorized certificate being issued.
Example use: Restrict certificate issuance for example.com to your approved certificate authority.
TTL — Control DNS Record Caching
TTL (Time To Live) determines how long DNS resolvers can cache a DNS record before requesting an updated value. A shorter TTL can be useful before planned DNS changes, domain migrations, or server moves, while longer TTL values can reduce how frequently stable records need to be queried.
Example use: Lower the TTL before a planned website migration so DNS changes can be refreshed sooner.
DNS Management Best Practices
Good DNS management is not only about creating records—it is also about making controlled changes, verifying the results, and protecting the DNS configuration that connects your domains to websites, email services, and applications. These practices can reduce configuration errors and make DNS changes, migrations, and troubleshooting more predictable.
Verify DNS Records Before Saving Changes
Before updating a DNS record, check the record type, hostname, destination value, and TTL against the service you are connecting. A small error in an A, CNAME, MX, or TXT record can send website traffic or email to the wrong destination.
For important changes, compare the new configuration with the existing records before removing or replacing anything.
Use TTL Strategically
TTL (Time To Live) controls how long DNS resolvers can cache a record. Consider lowering the TTL before a planned website migration, server change, or DNS update when you need the new value to be picked up sooner.
After the change has been verified and the DNS configuration is stable, a longer TTL can reduce repeated DNS queries and keep established records cached for longer.
Check DNS Propagation After Updates
Don’t assume a DNS change is active everywhere immediately. After updating your DNS records, use DNS lookup or propagation-checking tools to verify that the expected values are being returned from different locations.
This is particularly useful after changing A, CNAME, MX, NS, or TXT records, moving a website to a new server, or switching DNS providers.
Keep DNS Changes Documented
Record important DNS configuration changes, including what was changed, when it was changed, and why. Documentation makes it easier to identify the cause of unexpected website, email, or application issues and helps teams safely manage DNS during infrastructure changes.
For business domains, keeping track of important records and their intended purpose can also prevent accidental deletion or conflicting configurations.
Protect DNS Access
DNS controls critical connections between your domain and online services, so access to DNS management should be restricted to authorized users. Use strong account security, appropriate permissions, and available DNS security controls such as DNSSEC where applicable.
Avoid making DNS changes from untrusted environments and review who has permission to modify important domain records.
Review Important DNS Records Regularly
Periodically review your A, AAAA, CNAME, MX, TXT, NS, and CAA records to identify outdated destinations, unused subdomains, incorrect configurations, or records left behind after a service migration.
Keeping DNS records organized helps reduce configuration conflicts and makes future domain, website, email, and hosting changes easier to manage.
Cloudoora DNS Management Features
Centralized DNS Management Dashboard
Manage DNS records and domain settings from a single interface instead of switching between different DNS tools. Create and update supported A, CNAME, MX, and TXT records for websites, email services, subdomains, and connected applications while keeping your domain configuration organized.
DNS Propagation Monitoring
After changing a DNS record, verify whether the new configuration is resolving as expected. DNS propagation monitoring lets you check how changes appear across different locations, helping you distinguish an active configuration from a change that is still propagating or returning an unexpected result.
DNS Change History & Audit Logs
Know what changed when a DNS configuration needs troubleshooting. DNS audit logs provide visibility into previous DNS modifications, helping you review configuration history and identify changes that may have affected a website, email service, subdomain, or application.
One-Click DNS Record Templates
Simplify repetitive DNS record management with pre-configured templates for common records such as A, CNAME, MX, and TXT. Instead of entering every configuration manually, use templates to speed up common website, email, and service setup tasks.
DNSSEC Support
Add an additional layer of DNS security with DNSSEC on supported domains. DNSSEC uses cryptographic validation to help resolvers verify the authenticity of DNS responses, helping protect your domain’s DNS resolution from certain forms of tampering.
DNS Management API
Automate supported DNS record changes through the Cloudoora API and connect DNS management with your infrastructure or deployment workflows. This is useful for teams that need programmatic DNS updates as part of application deployments, automated infrastructure changes, or other repeatable workflows.
DNS Management for Websites, Email & Applications
DNS management becomes useful whenever a domain needs to connect to a website, email provider, application, SaaS platform, or external service. The exact DNS records you configure depend on what you are connecting, but the goal is the same: direct each domain or subdomain to the correct service and keep those connections manageable as your infrastructure changes.
Website DNS Management
Connect your domain and subdomains to websites and web servers by configuring the appropriate DNS records. A and AAAA records can point hostnames to server IP addresses, while CNAME records can connect a hostname to another domain name.
This is particularly useful when launching a website, moving hosting providers, changing servers, or creating subdomains for different parts of a website.
Email DNS Management
Use MX records to specify where email for your domain should be delivered. Additional TXT-based DNS records can support email authentication, domain verification, and policies required by your email provider.
Proper email DNS configuration is important when setting up business email, migrating between email providers, or connecting a domain to a third-party mail service.
Application & API DNS
Use DNS to connect application domains and subdomains to web applications, APIs, and backend services. For example, you can use a subdomain such as api.example.com for an API while keeping www.example.com connected to your website.
This makes DNS management useful for teams running separate frontend, backend, API, and service environments.
SaaS & Multi-Service DNS
Modern businesses often use multiple platforms for websites, applications, email, analytics, payments, customer portals, and other services. DNS management provides a central place to maintain the records that connect your domain and subdomains to these services.
Keeping those configurations organized becomes especially important as your number of applications, subdomains, and third-party integrations grows.
Domain Verification & Third-Party Services
Many external platforms require you to add a TXT or other DNS record to verify that you control a domain. DNS management makes it easier to add, update, and remove these verification records when connecting services.
This can include website platforms, cloud services, email providers, security tools, analytics platforms, and other third-party applications.
DNS Security With DNSSEC
DNSSEC (Domain Name System Security Extensions) adds a layer of cryptographic validation to DNS by allowing resolvers to verify that DNS responses are authentic and have not been altered. For domains that support DNSSEC, it strengthens DNS security by protecting the integrity of DNS data as it moves through the DNS resolution process.
DNSSEC adds digital signatures to DNS data, creating a chain of trust between a domain’s authoritative DNS information and validating DNS resolvers. When DNSSEC validation is enabled, a resolver can verify whether the DNS response it receives matches the signed information published for the domain.
Unlike encryption technologies, DNSSEC does not encrypt DNS queries or hide the domain being requested. Its primary purpose is to provide authentication and integrity for DNS responses.
Monitor & Troubleshoot DNS Changes
DNS changes do not always appear everywhere at the same time. When a website, email service, subdomain, or application is not resolving as expected, the first step is to verify the DNS records, authoritative nameservers, propagation status, and cached responses. A structured DNS troubleshooting process can help identify whether the problem is an incorrect record, DNS caching, incomplete propagation, or another configuration issue.
Check DNS Propagation
After updating a DNS record, check how the new value is resolving from multiple locations. DNS propagation checking can help you determine whether an A, AAAA, CNAME, MX, TXT, or other record is returning the expected value across different DNS resolvers.
This is especially useful after changing web hosting, moving a server, switching DNS providers, adding a subdomain, or updating email DNS records. If some locations still return the previous value, the change may still be affected by DNS caching and TTL.
Verify DNS Records
Before troubleshooting the website or application itself, confirm that the DNS record contains the correct record type, hostname, destination, and TTL. For example, an A record should point to the intended IPv4 address, while a CNAME should reference the correct hostname.
For email problems, check the domain’s MX records and relevant TXT-based email authentication records. For website and application issues, review the A, AAAA, and CNAME records associated with the affected hostname.
Identify Incorrect DNS Configuration
If a domain is resolving to the wrong server or a service is unavailable, look for common DNS configuration errors such as an incorrect IP address, hostname typo, conflicting records, outdated nameservers, or an accidentally removed record.
Also verify that the domain is using the intended authoritative DNS nameservers. If the nameservers point to a different DNS provider, changes made in another DNS dashboard may not control the records being returned to users.
Understand DNS Caching and TTL
DNS resolvers can cache records for the period specified by their TTL (Time To Live). This means a DNS change can be correct on the authoritative server while some users or networks continue receiving the previous cached value.
Before a planned migration or server change, a lower TTL can help reduce the caching period for future lookups. After confirming that the new configuration is working, TTL can be adjusted according to the stability and requirements of the DNS record.
Troubleshoot Website DNS Issues
If your website is not loading after a DNS change, check the DNS configuration before assuming the hosting server is unavailable. Confirm that the domain resolves to the correct IPv4 or IPv6 address, verify the authoritative nameservers, check DNS propagation, and make sure there are no conflicting records.
For persistent problems, compare the DNS response from multiple resolvers and review recent DNS changes. This helps separate a DNS configuration problem from an issue with the web server, application, SSL/TLS configuration, or hosting environment.
Frequently Asked Questions
DNS management is the process of creating, updating, securing, and maintaining the DNS records that determine how a domain connects to websites, email services, applications, and other online resources. It includes managing records such as A, AAAA, CNAME, MX, TXT, and NS, as well as monitoring DNS changes and applying security controls such as DNSSEC.
To manage DNS records, identify the domain or subdomain you want to configure, select the appropriate record type, enter the required destination or value, and save the change. After updating a record, check DNS propagation and verify that the expected value is being returned.
With Cloudoora, supported DNS records can be managed from a centralized DNS management environment.
The records required depend on how the website is hosted. An A record can point a domain to an IPv4 address, while an AAAA record can point it to an IPv6 address. A CNAME record can be used when a hostname needs to point to another hostname.
A website may also require TXT or other DNS records for domain verification, security, or connected third-party services.
Email delivery primarily relies on MX records, which identify the mail servers responsible for receiving messages for your domain. Your email provider may also require TXT records for domain verification and email authentication policies such as SPF.
Always use the exact DNS values provided by your email service when configuring business email DNS.
An A record points a hostname directly to an IPv4 address, while a CNAME record points one hostname to another hostname.
For example, an A record can point example.com to a server IP address, while a CNAME can point www.example.com to example.com or another hostname.
DNS changes become visible according to factors such as TTL, resolver caching, and the DNS configuration being changed. Some changes may appear quickly, while previously cached records can continue returning the older value until their cache expires.
After changing DNS, use DNS lookup or propagation-monitoring tools to check how the new record is resolving from different locations.
DNSSEC (Domain Name System Security Extensions) adds cryptographic validation to DNS responses, allowing validating resolvers to verify the authenticity and integrity of signed DNS data.
It can provide additional protection against certain DNS spoofing and cache-poisoning scenarios. Whether you should enable DNSSEC depends on your domain, DNS provider, registrar, and security requirements. Incorrect DNSSEC configuration can also cause legitimate DNS queries to fail validation, so it should be configured carefully.
Check the updated DNS record using a DNS lookup or propagation-checking tool and compare the returned value with the configuration you intended to publish. Check from multiple locations when possible, especially after changing A, CNAME, MX, NS, or TXT records.
If different locations return different results, consider TTL and DNS caching before assuming the configuration is incorrect.
A DNS configuration error can cause a website or application to resolve to the wrong server, prevent a subdomain from working, interrupt email delivery, or prevent a third-party service from verifying your domain.
If a problem occurs, check the record type, hostname, destination value, nameservers, TTL, and recent DNS changes before making additional modifications.
Yes, many common DNS tasks can be performed without advanced networking knowledge when a DNS management interface provides clear record fields and configuration guidance. However, you should understand what the record is intended to do before changing important website, email, or application DNS settings.
For more complex configurations or troubleshooting, DNS support can help identify the appropriate records and configuration.
Yes, API-based DNS management can automate supported DNS record operations and reduce repetitive manual changes. This can be useful when domains, subdomains, applications, or infrastructure change frequently.
Cloudoora provides a DNS Management API for supported DNS automation workflows, allowing DNS changes to be incorporated into programmatic infrastructure and application processes.