Telegram Bot
Managing DNS in ISPmanager
3 min read
20.02.2026
ISPmanager includes a built-in DNS management system, allowing you to configure domains, subdomains, and records for websites hosted on your server. You can manage DNS zones, configure name servers, and optimize settings for website performance and security.
For the broader ISPmanager context, see How to Install and Manage ISPmanager Lite on a VPS; for the mail-records side that lives in the same DNS zone, Configuring Mail Records (MX, SPF, DKIM, DMARC) in ISPmanager.
Accessing DNS Management in ISPmanager
- Log in to ISPmanager at:
- Navigate to "Domains" > "DNS Manager".
- Select a domain to view or modify its DNS settings.
https://your-server-ip:1500Adding a New DNS Zone
To create a new DNS zone (for a new domain):
- Go to "Domains" > "DNS Manager" > "Add".
- Enter the domain name (e.g., example.com).
- Choose "Create new DNS zone".
- Assign name servers (NS records) (e.g., ns1.example.com, ns2.example.com).
- Click "OK" to save.
Common DNS Records in ISPmanager
| Record Type | Purpose | Example |
|---|---|---|
| A (Address Record) | Maps a domain to an IP address | example.com > 192.168.1.1 |
| CNAME (Alias Record) | Points a subdomain to another domain | www.example.com > example.com |
| MX (Mail Exchange) | Specifies mail servers for email delivery | mail.example.com |
| TXT (Text Record) | Used for SPF, DKIM, and domain verification | v=spf1 include:_spf.google.com ~all |
| NS (Name Server) | Specifies the authoritative name servers | ns1.example.com, ns2.example.com |
Configuring Name Servers (Custom NS Records)
If you want to use your own name servers, follow these steps:
- Go to "Domains" > "DNS Manager" > Select Domain.
- Add NS Records:
| Type | Name | Value |
|---|---|---|
| A | ns1 | 192.168.1.1 |
| A | ns2 | 192.168.1.2 |
- Update Glue Records at Registrar:
- Log into your domain registrar.
- Add ns1.example.com and ns2.example.com with their respective IP addresses.
- Update the Name Servers in your domain settings to:
ns1.example.com
ns2.example.comConfiguring Mail Records (MX, SPF, DKIM, DMARC)
To ensure email works correctly, add the following:
MX Record
- Points to the email server handling mail:
example.com MX 10 mail.example.comSPF Record (Anti-Spam)
- Prevents unauthorized email senders:
example.com TXT "v=spf1 include:_spf.google.com ~all"DKIM Record
- Ensures email authenticity:
default._domainkey.example.com TXT "v=DKIM1; k=rsa; p=PUBLIC_KEY"DMARC Record
- Defines email security policies:
_dmarc.example.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@example.com"
Propagation and Testing DNS Changes
After making DNS changes, wait up to 24 hours for propagation.
Test DNS Propagation
- Using Command Line:
- Using Online Tools:
nslookup example.com
dig example.comTroubleshooting DNS Issues
| Issue | Possible Fix |
|---|---|
| Website not resolving | Check A records and DNS propagation. |
| Email not working | Verify MX, SPF, and DKIM records. |
| DNS changes not applying | Clear local DNS cache: ipconfig /flushdns (Windows) or sudo systemctl restart systemd-resolved (Linux). |
| NS records not updating | Ensure the correct name servers are set at the domain registrar. |
- ISPmanager makes it easy to manage DNS settings.
- You can configure custom name servers, email records, and security settings.
- DNS changes may take up to 24 hours to propagate fully.
Yes, by default it installs and manages Bind (named) on the same VPS. You can keep DNS on the same host or delegate to an external DNS provider — ISPmanager exposes the zone files either way. For high-availability or low-latency global resolution, delegating to Cloudflare/Route53 is usually a better fit than a single-VPS Bind.
Under /var/named/ on CentOS and /etc/bind/ on Debian/Ubuntu. The panel writes to these files when you edit records in the UI. Editing the files manually works, but ISPmanager will overwrite changes on the next UI save — so if you must hand-edit, also disable panel-level DNS management for that zone.
Drop to 300 (5 minutes) a day before the change. That window is enough for global resolvers to expire the long-TTL value. Bump back to 3600 (1 hour) once the new value is stable; very high TTLs (24 h+) make future changes slow without a meaningful cache-hit benefit.
A resolver in your path has cached the old answer for longer than the TTL suggested. Use dig +trace yourdomain.com to see who's answering with the stale value, or try a different resolver (8.8.8.8, 1.1.1.1) for testing. If global propagation tools show the new IP everywhere except your ISP, that ISP's resolver is the cause and you can't fix it from your side.
mx10.mailspamprotection.com: Understanding and Configuring It
How to Configure Name Servers for Hosting (NSHosting Guide)
NS Hosting: Overview and Management
Hosting
Cloud Solutions
For You
VDS
Website Builders
Our services
Client Area
USD - United States Dollar
EUR - Euro
GBP - British Pound
CAD - Canadian Dollar
CHF - Swiss Franc
JPY - Japanese Yen
AUD - Australian Dollar
RUB - Russian Ruble
TRY - Turkish Lira
CNY - Chinese Yuan
INR - Indian Rupee
UAH - Ukrainian Hryvnia