Era Host hosting
EraHost – Free Domain, Cheap Hosting!
Client Area
Support 24/7
Menu

Configuring Name Servers (Custom NS Records) in ISPmanager VDS

3 min read
17.03.2025

If you are hosting your own VDS (Virtual Dedicated Server) with ISPmanager, setting up custom name servers (NS records) allows you to manage domain DNS directly on your server.

Custom Name Servers in ISPmanager VDS
Setting up custom NS records on a VDS running ISPmanager.

For the broader ISPmanager DNS surface, see Managing DNS in ISPmanager; for the install and lifecycle, How to Install and Manage ISPmanager Lite on a VPS.

What Are Custom Name Servers?

Custom name servers let you use your own domain for DNS resolution instead of your hosting provider defaults.

For example:

  • Instead of using ns1.hostingprovider.com
  • You can create ns1.yourdomain.com and ns2.yourdomain.com

Steps to Configure Custom Name Servers in ISPmanager

Assign Static IPs to Your Server

Before setting up name servers, ensure your VDS has at least two static IP addresses (one for each NS record).

If you have only one IP, you can use the same IP for both NS records.

To check your current IPs:

ip a

Configure DNS Zone for Your Domain

  1. Log in to ISPmanager (https://your-server-ip:1500).
  2. Navigate to "Domains" > "DNS Manager".
  3. Click "Add DNS Zone" and enter your domain name (yourdomain.com).
  4. Set your DNS Zone Name to yourdomain.com.

Add NS Records

  1. Click "Add Record".
  2. Choose "NS" (Name Server) from the dropdown.
  3. Enter the Name Server details:
Type Name Value
NS @ (root domain) ns1.yourdomain.com
NS @ (root domain) ns2.yourdomain.com
  1. Click "Save".

Add A Records for Name Servers

  1. Click "Add Record".
  2. Choose "A" (Address Record).
  3. Enter the following details:
Type Name Value (IP Address)
A ns1 192.168.1.1 (Replace with your VDS IP)
A ns2 192.168.1.2 (Replace with your second IP)
  1. Click "Save".
Linux VDS
High performance for your projects
  • Root access and flexible setup
  • Control panel
  • NVMe disks
  • DDR5
Linux VDS

Update Your Registrar with Custom Name Servers

Now that the name servers are set up in ISPmanager, you must update your domain registrar settings.

Go to Your Domain Registrar

  1. Find the "Manage Nameservers" or "Custom DNS" section.
  2. Enter your custom name servers:
  3. ns1.yourdomain.com
    ns2.yourdomain.com
  4. Save and wait for DNS propagation (can take 24–48 hours).

Restart DNS Service

To apply changes, restart the DNS service on your VDS:

sudo systemctl restart named  # For BIND
sudo systemctl restart pdns   # For PowerDNS

Check if the DNS server is running:

systemctl status named

Verify Your Custom Name Servers

Method 1: Using dig Command

Run:

dig ns yourdomain.com

If correctly set up, you should see:

;; ANSWER SECTION:

yourdomain.com.  3600  IN  NS  ns1.yourdomain.com.

yourdomain.com.  3600  IN  NS  ns2.yourdomain.com.

Method 2: Using Online Tools

Troubleshooting Custom Name Server Issues

Issue Possible Fix
Name servers not resolving Check if NS and A records are correctly set in ISPmanager.
Propagation taking too long Flush local DNS: ipconfig /flushdns (Windows) or sudo systemctl restart systemd-resolved (Linux).
Domain registrar rejecting NS Ensure the NS records match the assigned IPs in ISPmanager.
DNS service not starting Check logs with journalctl -xe -u named.
  • Custom NS records allow full DNS control for your domains on ISPmanager VDS.
  • Setting up NS and A records correctly ensures proper domain resolution.
  • Update your domain registrar with the correct name servers.
Frequently asked questions
Branding (ns1.yourdomain.com instead of ns1.your-host.com) — important for resellers who don't want their upstream provider visible to clients. Otherwise it's pure overhead — most single-VPS owners get the same reliability and better redundancy by delegating to Cloudflare/Route53.
If your nameservers live under the same domain (ns1.yourdomain.com manages yourdomain.com), resolvers face a chicken-and-egg: to resolve yourdomain.com they need ns1.yourdomain.com — but to find ns1.yourdomain.com they need yourdomain.com. The glue record at the registrar provides the IP directly, breaking the loop.
dig NS yourdomain.com +short from an external resolver. The answer should list your custom NS hostnames. Also check the glue with dig +trace yourdomain.com — the parent zone (.com) should hand off to your nameservers with IPs, not a CNAME chain.
No. If the VPS goes down, both nameservers go with it. Real redundancy needs two physically separate IPs/locations. For low-stakes single-site setups, ns1 and ns2 on one VPS is acceptable; for businesses where DNS uptime matters, use a managed DNS provider with anycast or pair your VPS with a secondary on a different host.
Related articles
How to Configure Name Servers for Hosting (NSHosting Guide)
How to Link a Domain with Yahoo Mail and Use It as a Corporate Email
Fix: "The Record We Detected Doesn't Match All the Expected Values" (MSOID CNAME Issue)