33 lines
1.3 KiB
Markdown
33 lines
1.3 KiB
Markdown
# DNS Management by Domain
|
|
|
|
Not all domains use Cloudflare DNS. Some use SiteGround, which has no programmatic API access.
|
|
|
|
## SiteGround-Managed Domains
|
|
|
|
`itpropartner.com` DNS is managed at **SiteGround** (nameservers: `ns1.siteground.net`, `ns2.siteground.net`).
|
|
|
|
**Implications:**
|
|
- DNS updates must be done manually through the SiteGround control panel (Germaine's account)
|
|
- Cloudflare API will return no results for these domains even with a valid API token
|
|
- The `CLOUDFLARE_API_TOKEN` in .env has DNS permissions but only applies to Cloudflare-hosted zones
|
|
|
|
**Discovery:** Confirmed Jul 10, 2026 — `host -t NS itpropartner.com` returned SiteGround nameservers. Previous attempts to use Cloudflare API for DNS record management on this domain silently failed.
|
|
|
|
## Cloudflare-Managed Domains (verified)
|
|
From zone listing Jul 10, 2026 — 13 zones. Notable:
|
|
- `germainebrown.com` (MXroute for email, Cloudflare for DNS)
|
|
- `forefrontwireless.com` / `forefrontwireless.net`
|
|
- `iamgmb.com`
|
|
- `debtrecoveryexperts.com`
|
|
- `apextrackexperience.com`
|
|
- `itpropartner.com` ← DNS at SiteGround, NOT Cloudflare despite having a zone entry
|
|
|
|
## DNS Provider Detection Pattern
|
|
|
|
Always verify nameservers before using the Cloudflare API:
|
|
```bash
|
|
host -t NS <domain>
|
|
```
|
|
|
|
If nameservers don't include `cloudflare.com`, the Cloudflare API won't work for DNS record management.
|