If your domain is registered with another domain registrar and you wish for our systems to have full DNS control over your domain, you will need to update your domain's name servers or DNS servers. For Windows shared hosting, DNS hosting and Email hosting services the primary name server is ns1.aspnix.com at 15.181.17.1. For Linux shared hosting services the primary name server is nsa.aspnix.com at 52.1.61.50. This change tells the internet to query our name servers for all records related to your domain.

Delegating DNS to us simplifies management because we can automatically configure records for your hosted websites, email addresses, subdomains, and other services. Most users should make this change unless they run their own DNS server or another provider manages DNS for them. In those cases you will instead create and maintain individual DNS records that point to the hosting IPs and mail servers assigned in your account control panel.

#Name Servers by Hosting Platform

#Windows Shared Hosting, DNS, and Email

Our Windows environment uses a single primary name server. Set this value at your registrar. While some interfaces require both primary and secondary entries, the primary alone is sufficient for the majority of configurations. The server handles resolution for all web, mail, and custom DNS needs on Windows shared plans.

  • ns1.aspnix.com - 15.181.17.1

#Linux Shared Hosting

Linux shared hosting uses its own dedicated primary name server. Update your registrar with this hostname to delegate authority. The configuration works identically to the Windows process but routes queries to the Linux infrastructure.

  • nsa.aspnix.com - 52.1.61.50

#How to Change Your Domain Name Servers

The exact interface varies by registrar but the process follows the same general steps. Begin by logging into the account associated with your domain registration. Navigate to the domain overview or advanced DNS settings area. Disable any domain lock or privacy features that might prevent changes.

  • Find and select the nameservers configuration option, often under a tab labeled DNS, Nameservers, or Domain Management.
  • Switch from default or registrar nameservers to custom or third-party.
  • Enter the ASPnix name server hostname exactly as provided above. If a second name server field is present, use the same value or contact support for the current secondary recommendation.
  • Remove any previous nameserver entries, save the updates, and confirm the transaction. Record the timestamp for later troubleshooting.

DNS propagation begins immediately but can take anywhere from a few minutes to 48 hours to complete worldwide as caches on recursive resolvers expire. During this window some clients may still reach the previous destination while others see the new hosting environment.

#Verifying Your DNS Delegation

After submitting the change, confirm that the new name servers are live before assuming the update is fully effective. Use command-line tools available on Windows, macOS, or Linux to query the current authoritative servers. These checks bypass local cache and speak directly to public DNS infrastructure.

bash 
nslookup -type=NS yourdomain.com

# Expected output should reference ns1.aspnix.com or nsa.aspnix.com

dig NS yourdomain.com

The output must list the ASPnix name server(s). If it still shows the old values, the change has not propagated, the registrar update was rejected, or local DNS cache is interfering. Flush your local resolver cache with ipconfig /flushdns on Windows or sudo systemd-resolve --flush-caches on Linux systems.

#When to Manage Individual DNS Records Instead

If you run your own DNS server or have another provider managing your DNS, do not change the name servers. Instead, update your DNS records to point to the correct IP addresses and mail servers assigned in your ASPnix control panel. This typically requires an A record for the root domain and www subdomain, an MX record for email delivery, TXT records for SPF and DKIM, and any CNAMEs needed for additional services. This approach demands ongoing maintenance whenever hosting details change.

In summary, using our name servers is the simplest and least error-prone way to integrate your domain with shared hosting. Always verify the values before saving at the registrar, allow adequate time for global propagation, and test resolution from multiple geographic locations. Refer to additional knowledge base articles covering email setup, FTP configuration, and database connectivity once DNS is confirmed live.