Performance VPS
Foundational VPS
VDS
Specialty Servers
Domain Names
Colocation
Manage DNS Records for Your Domain
Edit A, AAAA, CNAME, MX, TXT, and SRV records for a domain registered with NoBull Networks from MyNobull, with the rules that prevent most DNS mistakes.
If a domain registered with NoBull Networks uses our nameservers, its DNS records are edited right inside MyNobull: no third-party DNS host, no extra login. This guide covers where to find the editor, the record types you will actually use, and the handful of rules that prevent most DNS mistakes.
Open the DNS editor#
- Log in to MyNobull at my.nobullnetworks.com, open Domains, then My Domains, and click the domain.
- Check the nameservers. The DNS editor only takes effect when the domain's nameservers are set to our defaults. If they point elsewhere (Cloudflare, your old host), edit records there instead, or switch nameservers first: Change Nameservers.
- Open DNS Management from the domain's menu. Records are listed as name, type, value, and TTL, with a row to add more.
The record types you will use#
| Type | Points a name at | Typical use |
|---|---|---|
| A | an IPv4 address | The bare domain and subdomains to your VPS: Point a Domain at Your VPS |
| AAAA | an IPv6 address | Same, over IPv6 |
| CNAME | another name | www following the bare domain; verification records some services ask for |
| MX | a mail server name, with priority | Where email for the domain is delivered |
| TXT | free text | SPF, DKIM, DMARC, and ownership verification for Google, Microsoft, and others |
| SRV | a service at a host and port | Game servers on non-default ports, some chat and VoIP services |
Rules that save tickets#
- The name field is relative to the domain. Enter
www, notwww.example.com; use@(or leave blank, depending on the form) for the bare domain. - A CNAME cannot share a name with any other record, so the bare domain uses A/AAAA, never CNAME.
- MX and CNAME values are names, not IPs, and should end with a trailing dot when the editor expects a fully-qualified name (
mail.example.com.). - TTL is how long resolvers cache the answer. 300 while you are changing things, 3600 or more once stable.
- Only one SPF record per domain; combine mechanisms in one TXT rather than adding a second.
Email records in one go#
For a domain whose mail lives with a provider, the provider gives you exact values; the shape is always the same:
@ MX 10 mx1.provider.example.
@ MX 20 mx2.provider.example.
@ TXT "v=spf1 include:spf.provider.example -all"
selector._domainkey TXT "v=DKIM1; k=rsa; p=MIIB..." (from the provider)
_dmarc TXT "v=DMARC1; p=quarantine; rua=mailto:[email protected]"Sending from your own server instead? See Sending Email from a VPS.
Verify#
dig +short A example.com @1.1.1.1
dig +short MX example.com @1.1.1.1
dig +short TXT example.com @1.1.1.1Changes usually show within minutes; anything cached under an old TTL takes up to that TTL to refresh elsewhere.
Prefer a different DNS host?#
That is fine, and common. Cloudflare, your VPS's control panel, or any DNS provider works; simply point the nameservers there and manage records at that host instead. Registration, renewal, and WHOIS privacy stay in MyNobull regardless.
