Fix 10 Mbit/s conversion error and DNS zone example inconsistencies

This commit is contained in:
Djeex
2026-09-07 13:42:30 +02:00
parent 485c5d5578
commit 5548287c65
6 changed files with 17 additions and 15 deletions
+6 -5
View File
@@ -23,12 +23,13 @@ You can enter _records_ into this DNS zone to direct requests properly. You can
Example of a DNS zone for the domain `mydomain.com`:
```
$TTL 3600
@ IN SOA ns1.dns.me. dns.net. (2024051800 86400 3600 3600000 60)
IN NS ns1.dns.me.
IN NS ns2.dns.me.
IN A 203.0.113.0
www IN CNAME mydomain.com
sousdomaine IN CNAME mydomain.com
IN A 203.0.113.10
www IN CNAME mydomain.com.
subdomain IN CNAME mydomain.com.
```
In this example:
@@ -36,8 +37,8 @@ In this example:
- `$TTL 3600` tells global name servers that the records are valid for 1 hour (after which they need to re-check).
- `IN SOA ns1.dns.me. dns.net. (...)` indicates `ns1.dns.me` as the primary DNS server, with refresh intervals.
- `IN NS` records define the authoritative name servers for the domain.
- `IN A 203.0.113.0` means `mydomain.com` points to IP `203.0.113.0`.
- `subdomain IN CNAME mydomain.com` means `subdomain.mydomain.com` points to the same destination as `mydomain.com`.
- `IN A 203.0.113.10` means `mydomain.com` points to IP `203.0.113.10`.
- `subdomain IN CNAME mydomain.com.` means `subdomain.mydomain.com` points to the same destination as `mydomain.com`.
So, if you want to point `mydomain.com` to your server, you can do it by adding an `A` record pointing to your server's public IP address.