aziontech · PedroMiolaSilva · Apr 11, 2025 · Jul 11, 2026 · Jul 11, 2026
@@ -3,16 +3,16 @@ title: Edge DNS
 description: >-
   Host domains, DNS zones, and records with Azion routing solutions and Edge
   DNS.
-meta_tags: 'Edge DNS, DNS, routring'
+meta_tags: 'Edge DNS, DNS, routing'
 namespace: documentation_products_intelligent_dns
 permalink: /documentation/products/secure/edge-dns/
 ---
 
 import LinkButton from 'azion-webkit/linkbutton'
 
-**Edge DNS** is a domain hosting service that is part of Azion's traffic routing solution. By using it, your domains will be hosted on Azion distributed infrastructure using the same performance and security solutions built for other Azion products, combining techniques to optimize requests with protection against **Distributed Denial of Service (DDoS)** attacks. 
+**Edge DNS** is a domain hosting service that is part of Azion's traffic routing solution. With Edge DNS, your domains are hosted on Azion's global infrastructure using the same performance and security solutions built for other Azion products, combining request optimization techniques with protection against **Distributed Denial of Service (DDoS)** attacks.
 
-Edge DNS works as an authoritative DNS solution that allows the customers to manage their domains, zones, and records through a friendly and intuitive interface. It's designed for those that want high performance and high availability for their hosting and their domain. 
+Edge DNS works as an authoritative DNS solution that allows customers to manage their domains, zones, and records directly from Azion Console. It's designed for customers who need high performance and high availability for their domain hosting.
 
 ---
 
@@ -40,7 +40,7 @@ After configuring Edge DNS, you can test if your zone is processing your informa
 
 ## Edge DNS Records
 
-<LinkButton link="/en/documentation/products/guides/secure/add-records/" label="go add records guide" severity="secondary" />
+<LinkButton link="/en/documentation/products/guides/secure/add-records/" label="go to add records guide" severity="secondary" />
 
 ### Zone Name
 
@@ -76,7 +76,7 @@ This is the DNS response to the registered record. For example, an IPv4 address.
 
 ### TTL (seconds)
 
-This is the time a response can be cached for on a resolver server. Time-to-live (TTL) is a value in an IP packet that tells a network router whether or not the packet has been on the network too long and should be discarded.
+This is the time, in seconds, that a DNS response can be cached by a resolver. When the TTL expires, the resolver discards the cached response and queries the authoritative nameserver again for a fresh answer.
 
 ### Policy
 
@@ -91,7 +91,7 @@ By choosing the *Weighted Policy*, there'll be two more fields to be completed,
 
 From this point on, this set of information will be synchronized with the **Edge DNS** service. Your settings are saved and distributed to the Azion network practically in real time.
 
-Your domain is now set up and ready to be served by Azion **Edge DNS**. To make sure everything is working well, run some of the tests described in the section [Testing my zone](#testing-my-zone).
+Your domain is now set up and ready to be served by Azion **Edge DNS**. To make sure everything is working well, run some of the tests described in the [test zone guide](/en/documentation/products/secure/troubleshoot/test-zone/).
 
 ### Record Policies
 
@@ -116,7 +116,7 @@ Given a set of Weighted Records, with same *Name* and *Type*, the chances of a s
 
 `Weight of the record / Sum of all Weights`
 
-<LinkButton link="/en/documentation/products/guides/secure/load-balance-dns/" label="go load balance DNS records guide" severity="secondary" />
+<LinkButton link="/en/documentation/products/guides/secure/load-balance-dns/" label="go to load balance DNS records guide" severity="secondary" />
 
 ---
 
@@ -141,7 +141,7 @@ The accepted value's format varies according to the chosen record type.
 | MX    | It must be in the format `[priority] [address]`.<br /><br />Maximum of 10 IP addresses (one per line). | `10 mailserver.example.com`<br /><br /> `20 mailserver2.example.com` |
 | NS    | It must be in FQDN format or be an IP address.<br /><br />Maximum of 10 records (one per line).<br /><br />An NS can't be configured by the main domain of the zone (naked domain).<br /><br />It must point to the servers that have authority over that record. | `ns1.aziondns.net`<br /><br /> `ns2.aziondns.net` |
 | PTR   | Reverse zones lined to IPv6 addresses follow other rules. | After creating a reverse zone, you must create a type PTR record associated with it.<br /><br /> `www.exemplo.com` |
-| SRV   | The zone name must have the following format: `_service._protocol.name`. Example: `_ldap._tcp.azionsrv"`.<br /><br />The response values must be in the format `[priority] [weight] [port] [target]`.<br /><br />Maximum of 10 records (one per line).<br /><br />It must point to the host name that has an A or AAAA record.<br /><br />**Note**: Edge DNS won't validate this automatically. | `0 60 5060 bigbox.example.com` |
+| SRV   | The zone name must have the following format: `_service._protocol.name`. Example: `_ldap._tcp.azionsrv".<br /><br />The response values must be in the format `[priority] [weight] [port] [target]`.<br /><br />Maximum of 10 records (one per line).<br /><br />It must point to the host name that has an A or AAAA record.<br /><br />**Note**: Edge DNS won't validate this automatically. | `0 60 5060 bigbox.example.com` |
 | TXT   | Limited to 1000 characters.<br /><br />Text that is separated by ENTER is considered as different responses by Edge DNS | This domain name is reserved for use in documentation.<br /><br /> `"printer=lpr5"`<br /><br /> `"favorite drink=orange juice"` |
 
 You can set up a domain, such as `www.domain.com`, to be used as a naked domain, that is, only `domain.com`. There are two ways to configure this:
@@ -187,7 +187,7 @@ In order for **Edge DNS** to become the authority over your zones, you must poin
 To point to your DNS registration, use one of the *nameservers* listed in the *Main Settings* tab of your Azion registered zones.
 
 :::note
-It's important to verify that all your records are properly registered and tested at **Edge DNS** before making this appointment. Otherwise, you risk having your service unavailable.
+It's important to verify that all your records are properly registered and tested at **Edge DNS** before making this change. Otherwise, you risk having your service unavailable.
 :::
 
 ---
@@ -205,8 +205,80 @@ The **Domain Name System Security Extensions (DNSSEC)** is a feature of the *Dom
 
 **Massive Redirect** is Azion's serverless integration for processing many simultaneous redirects. It can be used where there is a need to change a significant number of addresses, for example, in domain migrations.
 
-To configure massive redirection for domain migration, access the [Massive Redirect](/en/documentation/products/guides/massive-redirect-integration/) documentation. 
+To configure massive redirection for domain migration, access the [Massive Redirect](/en/documentation/products/guides/massive-redirect-integration/) documentation.
 
+---
+
+## Monitoring and troubleshooting replication issues
+
+When you create or update records in **Edge DNS**, changes are distributed across Azion's global infrastructure in near real time. However, DNS propagation depends on TTL values and resolver caches, which means some resolvers may still return stale responses for a period after a change is applied.
+
+### How replication works
+
+Edge DNS synchronizes zone data across Azion's distributed infrastructure automatically. The time a resolver takes to reflect a change depends on the **TTL (Time to Live)** value set on the record: lower TTL values reduce the window during which outdated responses are served.
+
+### Verifying propagation
+
+To confirm whether a record change has propagated correctly, use the `dig` command against one of Azion's authoritative nameservers directly, bypassing any intermediate resolver cache:
+
+```bash
+dig @<azion-nameserver> <your-domain> <record-type>
+```
+
+Replace `<azion-nameserver>` with any of the nameservers listed in the **Main Settings** tab of your zone in Azion Console (for example, `ns1.aziondns.net` or `ns2.aziondns.net`), `<your-domain>` with your zone's domain, and `<record-type>` with the DNS record type (for example, `A`, `CNAME`, or `MX`).
+
+<LinkButton link="/en/documentation/products/guides/run-the-dig-command/" label="go to dig command guide" severity="secondary" />
+
+### Common replication issues
+
+| Symptom | Likely cause | Recommended action |
+|---|---|---|
+| Record not resolving after update | Resolver is serving a cached response | Wait for the TTL to expire or lower the TTL before making changes |
+| Inconsistent responses across regions | Propagation still in progress | Wait a few minutes and re-query; check the record in Azion Console |
+| Zone not resolving at all | Nameservers not pointed to Azion | Verify that your domain registrar is using Azion's NS records |
+| NXDOMAIN for a record that exists | Record name or type mismatch | Confirm the record name and type in **Edge DNS** match the query |
+
+### Using Real-Time Events to investigate DNS queries
+
+**Real-Time Events** records queries received by your Edge DNS zones, including the query type (`Q Type`), resolution method (`Resolution Type`), and response status code (`Status Code`). Use these logs to identify unexpected query patterns, resolution failures, or anomalous traffic.
+
+<LinkButton link="/en/documentation/products/observe/real-time-events/" label="go to Real-Time Events reference" severity="secondary" />
+
+### Using Real-Time Metrics to track query volume
+
+The **Edge DNS** tab in **Real-Time Metrics** displays the **Total Queries** graph, which shows the total number of queries received by your zones over a selected time range. You can filter by zone using the available filters. A sudden drop in query volume may indicate a misconfiguration or a propagation issue, while an unexpected spike may signal abnormal traffic.
+
+<LinkButton link="/en/documentation/products/observe/real-time-metrics/" label="go to Real-Time Metrics reference" severity="secondary" />
+
+---
+
+## Checking platform status and service disruptions
+
+Azion publishes real-time operational status for all platform components, including **Edge DNS**, on the [Azion Status Page](https://status.azion.com).
+
+### What the status page shows
+
+The status page reports the current health of Azion services across regions and components. For Edge DNS, it reflects:
+
+- **Operational**: all zones are resolving normally across all data centers.
+- **Degraded performance**: query resolution is slower than expected in one or more regions.
+- **Partial outage**: some zones or record types are not resolving in specific regions.
+- **Major outage**: Edge DNS is unavailable in one or more regions.
+
+### Subscribing to status updates
+
+You can subscribe to incident notifications directly from the status page to receive email alerts when Azion opens, updates, or resolves an incident affecting Edge DNS or any other platform component.
+
+### During a service disruption
+
+If the status page reports an active incident affecting Edge DNS:
 
+1. Check the incident details on the status page for the affected regions and estimated resolution time.
+2. Avoid making zone changes during an active incident, as propagation behavior may be unpredictable.
+3. Monitor your TTL values: if your records have low TTL values, resolvers will re-query Azion's nameservers more frequently, which may amplify the impact of a disruption.
+4. Contact **Support** if your service is critically affected and the incident is not yet reflected on the status page.
 
+<LinkButton link="https://status.azion.com" label="go to Azion Status Page" severity="secondary" />
+<LinkButton link="/en/documentation/services/support/" label="go to Support documentation" severity="secondary" />
 
+---