pangolin_mirror/docs-v2
1
0
Fork 0
mirror of https://github.com/fosrl/docs-v2.git synced 2026-10-29 15:09:10 +01:00
Code Issues Packages Projects Releases Wiki Activity

Add dns config new feature

Browse Source
This commit is contained in:
Owen
2026-10-28 16:53:58 -04:00
parent 0e3d47ac2b
commit 273c071b96
2 changed files with 16 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/docs/manage/domains.mdx
+16 -2
View File
@@ -100,9 +100,23 @@ More detail on ports, firewalls, and networking for self-hosted setups is in the
<Warning> <Warning>
**Changing nameservers hands over the whole zone, not individual records.** If you point the nameservers for your root domain (e.g. `example.com`) at Pangolin, Pangolin becomes authoritative for **every** record on that domain — including MX/email, TXT/SPF, and any other subdomains you weren't intending to move. Once delegated, you manage DNS for that zone through Pangolin, not your old provider. **Changing nameservers hands over the whole zone, not individual records.** If you point the nameservers for your root domain (e.g. `example.com`) at Pangolin, Pangolin becomes authoritative for **every** record on that domain — including MX/email, TXT/SPF, and any other subdomains you weren't intending to move. Once delegated, you manage DNS for that zone through Pangolin, not your old provider.
Some registrars — Cloudflare included — only let you delegate NS records at the root, and **don't allow you to add other records once Cloudflare is no longer authoritative** for that zone (since it's no longer serving the zone at all). Practically, this means: Some registrars — Cloudflare included - only let you delegate NS records at the root, and **don't allow you to add other records once Cloudflare is no longer authoritative** for that zone (since it's no longer serving the zone at all). Practically, this means:
- Delegating `*.example.com` moves the entire domain, including email and any other services, to Pangolin's nameservers. - Delegating `*.example.com` moves the entire domain, including email and any other services, to Pangolin's nameservers.
- Delegating a subdomain instead (e.g. `*.apps.example.com`) avoids this — the root domain and its other records stay with your existing provider untouched. - Delegating a subdomain instead (e.g. `*.apps.example.com`) avoids this - the root domain and its other records stay with your existing provider untouched.
- If you must delegate the root and still need other records (MX, TXT, etc.) that your old provider managed use a subdomain delegation / CNAME setup instead and maintain these records in the root provider. - If you must delegate the root and still need other records (MX, TXT, etc.) that your old provider managed use a subdomain delegation / CNAME setup instead and maintain these records in the root provider.
</Warning> </Warning>
## Serving DNS Records
<Note>
Only available on Pangolin Cloud and Pangolin Enterprise when running with the DNS server or in clustered mode.
</Note>
Pangolin can serve arbitrary DNS records on a NS delegated domain. Currently, Pangolin supports serving A, AAAA, CNAME, MX, TXT, SRV, and NS records. Records will not be served until a domain has been verified.
To create a DNS record on a NS delegated domain, navigate to the domain settings in the Pangolin dashboard and add the desired record type (A, AAAA, CNAME, MX, TXT, SRV, or NS) with the appropriate name and value.
<Frame caption="Custom DNS Records in the Pangolin dashboard">
<img src="/images/custom-dns-records.png" alt="Custom DNS Records"/>
</Frame>
public/images/custom-dns-records.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 179 KiB