Skip to main content
nxtdev.xyz supports seven DNS record types. Each type has its own set of required fields and validation rules enforced at save time. The sections below document every field, its constraints, and a practical example you can adapt for your own use.
An A record maps a host to an IPv4 address. Use it to point your subdomain (or a sub-host) directly at a server.Use case: Point your apex subdomain at a VPS.
example A record
An AAAA record maps a host to an IPv6 address. It works identically to an A record but accepts IPv6 notation.Use case: Serve traffic over IPv6 from a dual-stack server.
example AAAA record
A CNAME record creates an alias from one hostname to another. The content must be a hostname — IP addresses are rejected.Use case: Point your subdomain at a Vercel deployment.
example CNAME record
A TXT record stores arbitrary text. Common uses include SPF policies, DKIM public keys, and domain ownership verification tokens.Proxying is not available for TXT records.Use case: Add an SPF record to authorize your mail sender.
example TXT record
An MX record specifies the mail server responsible for accepting email for a host. Lower priority values are tried first.Proxying is not available for MX records.Use case: Route incoming email through a third-party mail service.
example MX record
An SRV record advertises the location of a specific service. The DNS name it creates follows the pattern _service._proto.host.subdomain.nxtdev.xyz.Proxying is not available for SRV records.Use case: Advertise a Minecraft Java server so clients can connect with just your subdomain name.
example SRV record
An NS record delegates DNS authority for a zone to one or more nameservers.Proxying is not available for NS records.
Adding NS records at the apex (@) enables delegation mode for your subdomain. While delegation is active, all DNS editing is locked. See the Delegation documentation for details on how to manage this.
Use case: Delegate a sub-zone to your own nameservers.
example NS record