Skip to content

DNSCALE: allow third-party NS records at zone apex#4176

Open
dnscale-ops wants to merge 3 commits intoStackExchange:mainfrom
dnscaleou:fix/allow-apex-ns-records
Open

DNSCALE: allow third-party NS records at zone apex#4176
dnscale-ops wants to merge 3 commits intoStackExchange:mainfrom
dnscaleou:fix/allow-apex-ns-records

Conversation

@dnscale-ops
Copy link
Copy Markdown
Contributor

Summary

  • Stop filtering all apex NS records; only skip DNScale's own nameservers
    (*.dnscale.eu, *.dnscale.com) which are system-managed
  • Remove NsAtApex audit rejection so users can declare third-party NS records
  • Document apex NS behavior and multi-provider DNS setup with NAMESERVER() example

Motivation

DNScale now supports multi-provider DNS setups where users add third-party
nameserver records at the zone apex. The provider was previously blocking all
apex NS records, which prevented this use case.

Changes

File Change
providers/dnscale/dnscaleProvider.go Filter only DNScale's own NS records at apex instead of all NS records; add multi-provider documentation to GetNameservers
providers/dnscale/auditrecords.go Remove NsAtApex rejection
documentation/provider/dnscale.md Add "Nameservers and apex NS records" section with multi-provider example

DNScale now supports multi-provider DNS setups where users add
third-party nameserver NS records at the apex. Stop filtering all
apex NS records and instead only skip DNScale's own nameservers
(*.dnscale.eu, *.dnscale.com). Remove the NsAtApex audit rejection.
GetNameservers returns empty since DNScale assigns nameservers
server-side. For multi-provider DNS, users must explicitly add
NAMESERVER("ns1.dnscale.eu") etc. for registrar delegation.
Add section explaining that DNScale's own NS records are system-managed
and invisible to dnscontrol, while third-party NS records at apex are
supported. Include multi-provider example with explicit NAMESERVER().
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant