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.
FieldRequiredConstraints
hostYes@ or a relative label; max 63 chars; lowercase alphanumeric, ., _, -
contentYesValid IPv4 address. Private ranges (10.x, 192.168.x, 172.16–31.x) are blocked.
ttlNoInteger, 60–86400. Defaults to 3600.
proxiedNotrue or false. Routes traffic through Cloudflare when enabled.
Use case: Point your apex subdomain at a VPS.
example A record
Type:    A
Host:    @
Content: 203.0.113.42
TTL:     3600
Proxied: true
An AAAA record maps a host to an IPv6 address. It works identically to an A record but accepts IPv6 notation.
FieldRequiredConstraints
hostYesSame rules as A record host.
contentYesValid IPv6 address. Private ranges are blocked.
ttlNoInteger, 60–86400. Defaults to 3600.
proxiedNoAvailable for AAAA records, same behavior as A.
Use case: Serve traffic over IPv6 from a dual-stack server.
example AAAA record
Type:    AAAA
Host:    @
Content: 2001:db8::1
TTL:     3600
Proxied: false
A CNAME record creates an alias from one hostname to another. The content must be a hostname — IP addresses are rejected.
FieldRequiredConstraints
hostYesRelative label or @; max 63 chars.
contentYesValid hostname (max 255 chars, no consecutive dots, not an IP).
ttlNoInteger, 60–86400. Defaults to 3600.
proxiedNoAvailable for CNAME records.
Use case: Point your subdomain at a Vercel deployment.
example CNAME record
Type:    CNAME
Host:    @
Content: cname.vercel-dns.com
TTL:     3600
Proxied: false
A TXT record stores arbitrary text. Common uses include SPF policies, DKIM public keys, and domain ownership verification tokens.
FieldRequiredConstraints
hostYesRelative label or @; max 63 chars.
contentYesString, 1–1024 characters.
ttlNoInteger, 60–86400. Defaults to 3600.
Proxying is not available for TXT records.Use case: Add an SPF record to authorize your mail sender.
example TXT record
Type:    TXT
Host:    @
Content: v=spf1 include:sendgrid.net ~all
TTL:     3600
An MX record specifies the mail server responsible for accepting email for a host. Lower priority values are tried first.
FieldRequiredConstraints
hostYesRelative label or @; max 63 chars.
contentYesValid hostname (not an IP).
priorityYesInteger, 0–65535. Defaults to 10 when left blank.
ttlNoInteger, 60–86400. Defaults to 3600.
Proxying is not available for MX records.Use case: Route incoming email through a third-party mail service.
example MX record
Type:     MX
Host:     @
Content:  mail.example.com
Priority: 10
TTL:      3600
An SRV record advertises the location of a specific service. The DNS name it creates follows the pattern _service._proto.host.subdomain.nxtdev.xyz.
FieldRequiredConstraints
hostYesRelative label or @; max 63 chars.
serviceYesMust start with _, e.g. _minecraft. Lowercase alphanumeric and -.
protoYesOne of _tcp, _udp, or _tls.
priorityYesInteger, 0–65535. Defaults to 0.
weightYesInteger, 0–65535. Defaults to 0.
portYesInteger, 1–65535.
targetYesValid hostname (not an IP).
ttlNoInteger, 60–86400. Defaults to 3600.
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
Type:     SRV
Host:     @
Service:  _minecraft
Proto:    _tcp
Priority: 0
Weight:   0
Port:     25565
Target:   mc.example.com
TTL:      3600
An NS record delegates DNS authority for a zone to one or more nameservers.
FieldRequiredConstraints
hostYesRelative label or @; max 63 chars.
contentYesValid nameserver hostname (not an IP).
ttlNoInteger, 60–86400. Defaults to 3600.
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
Type:    NS
Host:    @
Content: ns1.example.com
TTL:     3600