Skip to main content
The Zone Editor is the canonical place to edit DNS records for any domain that uses Noxity nameservers. It’s a thin layer over the BIND zone file: every change you make here is what real resolvers see, with the TTL you set. Open it from cPanel home → Domains → Zone Editor.
Zone Editor listing every domain on the account with quick actions

​
Record types at a glance

RecordWhat it doesTypical use
AMaps a hostname to an IPv4 addressmybrand.com → 185.232.x.x
AAAAMaps a hostname to an IPv6 addressmybrand.com → 2a02:....
CNAMEAliases one hostname to anotherwww.mybrand.com → mybrand.com
MXTells the world which server handles mail for the domainmybrand.com → mybrand.com (priority 0)
TXTFree-form text. Used for SPF, DKIM, DMARC, and domain verificationSPF record for outgoing mail, Google site verification
SRVMaps a service to a host and portSIP, XMPP, Minecraft Bedrock
CAARestricts which Certificate Authorities can issue certs for the domainLock issuance to Let’s Encrypt only
The SOA record is set by cPanel and you usually don’t touch it.

​
Add a record

The Zone Editor has two views. The list view at Manage lets you see and edit everything. The shortcut buttons (+ A Record, + CNAME Record, + MX Record) on the main page open a one-shot form for the most common types.
1

Click Manage on the right domain

The Zone Editor for that domain opens, showing every record in the zone.
Manage view inside the Zone Editor
2

Click Add Record and pick a type

The dropdown next to Add Record lists every record type the editor supports. Pick the one you need.
3

Fill in the fields

The form changes based on the type. Common fields:
  • Name. The hostname. Use @ for the root of the domain. Use a bare subdomain name like blog for blog.mybrand.com. cPanel auto-appends the domain.
  • TTL. How long resolvers cache the value, in seconds. 14400 (4 hours) is the default. Drop to 300 if you’re about to change a record and want fast propagation.
  • Type. Already set if you picked from the dropdown.
  • Record (value). The IP, hostname, or text the record points at. Format depends on type.
4

Click Add Record

The change is live on Noxity’s nameservers within seconds. Resolvers elsewhere catch up over the TTL window.

​
Edit or delete a record

Each row in the Manage view has Edit and Delete buttons.
  • Edit opens an inline form. Change what you need, click Save Record.
  • Delete removes the record. There’s a confirmation step.
Deleting MX records cuts off inbound mail until you replace them. Deleting an A record on the root takes the site offline. If you’re not sure, take note of the existing values before you change anything.

​
NS records on subdomains

Subdomain NS delegations need a support ticket. The Zone Editor blocks NS records on subdomains by default to keep our nameservers authoritative for your zone. Some setups (a separate DNS provider for one subdomain, a customer who runs their own nameservers under a parent zone) need this. We’re happy to delegate, just open a ticket and let us know which subdomain points where.
If your DNS isn’t hosted with us (the domain uses external nameservers), you don’t have a Zone Editor entry for it at all. Manage records at the provider holding your nameservers.

​
Common record patterns

​
SPF for outgoing mail

A TXT record at @ that includes Noxity’s MailChannels relay.
  • Name: @
  • Type: TXT
  • Record: v=spf1 a mx include:relay.mailchannels.net ~all
  • TTL: 14400
If you already have an SPF record, edit it and add include:relay.mailchannels.net to the existing string. Don’t create a second SPF record on the same name.

​
DMARC

A TXT record at _dmarc.
  • Name: _dmarc
  • Type: TXT
  • Record: v=DMARC1; p=quarantine; rua=mailto:dmarc@mybrand.com
  • TTL: 14400
Start with p=none if you want to monitor without affecting delivery, then move to quarantine and reject once your reports look clean. See Email Deliverability for the full setup.

​
Verify a domain (Google, Microsoft, Stripe)

A TXT record at the name the provider gives you.
  • Name: usually @ or a token like _google-site-verification
  • Type: TXT
  • Record: the exact string from the provider, paste it in.
  • TTL: 14400 is fine, drop to 300 if you want the check to come back fast.

​
CNAME a subdomain to another host

  • Name: shop
  • Type: CNAME
  • Record: mybrand.myshopify.com. (mind the trailing dot, cPanel adds it for you if you forget)
  • TTL: 14400
You can’t put a CNAME at the root of the domain. Use an A record (or ALIAS, where supported) instead.

​
MX records for an external mail provider

Switch your incoming mail to Google or Zoho without leaving DNS.
PriorityNameRecord
1@aspmx.l.google.com.
5@alt1.aspmx.l.google.com.
5@alt2.aspmx.l.google.com.
10@alt3.aspmx.l.google.com.
10@alt4.aspmx.l.google.com.
After the records are in, also flip Email Routing on this domain to Remote Mail Exchanger so cPanel doesn’t try to deliver locally.

​
Common issues

Resolvers cache. Test with dnschecker.org which queries from many networks, or query Cloudflare’s resolver directly with dig @1.1.1.1 mybrand.com. If public resolvers see the new value, your local DNS cache is stale.
Right, that’s intentional on Noxity DNS. Open a ticket with the subdomain and the target nameservers and we’ll delegate it for you.
Some record types (CNAME, SOA, the apex record) can’t coexist with others on the same name. Most others (A, MX, TXT) can. If the editor refuses, you’re probably trying to put a CNAME on a name that already has an A record, or two CNAMEs on the same hostname.
RFC says one SPF record per name. If you’re adding MailChannels and you already have an SPF for Google or Microsoft, edit the existing record to merge them, don’t add a second.
The Zone Editor exposes the common types. For PTR, NAPTR, or anything else, open a ticket. Reverse DNS (PTR) needs to be set at the IP owner’s end anyway, which is us, so that’s a ticket regardless.

​
Need a hand?