Getting Started

Deployment Deployment - Diagnose Migrations Staging

Site Management

Backups Client Reporting Passwords Plugin Automation Plugin Management - Global Plugins & Themes - Diagnose Plugins & Themes - General Plugins & Themes - Git Plugins & Themes - Logs Must Install SMTP White Label WordPress Updates

Caching & Performance

Caching Caching - Blogs/Articles Caching - Diagnose Caching - Git Caching - WooCommerce Redis Optimize & Scale

Security

Security Security - Firewall

CDN & DNS

CDN CDN - AWS CDN - Cloudflare CDN - Diagnose Domains & DNS

Server & Tools

CRON Jobs Database Debug Tool PHP Settings Redirects SEO Tools Server Errors sFTP SSL Monitoring Analytics & Logs

Staq Billing

Staq Billing > Account Staq Billing > Client Staq Billing > Setup

Media

Media Media - Diagnose Media - Optimize

Accounts & Billing

Accounts & Billing

General

WordPress Hosting Website Diagnose Troubleshoot - Other

How to Add NS Records for Subdomains on Staq


On this page

    When managing DNS records with Staq, adding NS records to subdomains is not directly supported in the Staq dashboard. If you require NS records for a subdomain, this must be handled manually by our support team in AWS Route53.

    This guide outlines the process and what information to provide.

    What Are NS Records?

    NS (Name Server) records specify the authoritative name servers for a domain or subdomain. These are often required by third-party services, such as Klaviyo or ExactTarget, to manage DNS for specific subdomains.

    Limitations in Staq

    While the Staq dashboard allows you to manage most DNS record types, NS records for subdomains must be added manually by our team if the DNS is hosted on Staq. This limitation applies only to subdomains.

    Steps to Add NS Records for a Subdomain

    1. Gather Required Information

    To request NS records for a subdomain, prepare the following:

    • Subdomain name (e.g., email.example.com)
    • List of NS records to be added (e.g., ns1.exacttarget.com, ns2.exacttarget.com)

    2. Submit a Support Ticket

    Lodge a support ticket with all the gathered information.

    3. Manual Update by Staq Team

    Once your ticket is submitted, our team will manually add the NS records in AWS Route53 for your subdomain.

    4. Verification

    After the NS records are added, the subdomain will point to the specified name servers. You may use tools like MX Toolbox to verify the changes.

    Examples of Requests

    Example 1: Adding NS Records for Klaviyo

    Request:

    • Subdomain: send.example.com
    • NS Records:
      • ns2.klaviyo.com
      • ns3.klaviyo.com
      • ns4.klaviyo.com

    Support Action: The Staq team adds the NS records in AWS Route53.

    Example 2: Adding NS Records for ExactTarget

    Request:

    • Subdomain: email.example.com
    • NS Records:
      • ns1.exacttarget.com
      • ns2.exacttarget.com
      • ns3.exacttarget.com
      • ns4.exacttarget.com

    Support Action: The Staq team updates the DNS configuration manually to include these NS records.

    Important Notes

    • Visibility: You will not see manually added NS records in the Staq dashboard. However, other record types like TXT or CNAME can still be managed directly.
    • DNS Hosting Requirement: This process is only applicable if the DNS is hosted on Staq. For third-party DNS providers, you can add NS records directly in their interface.

    Conclusion

    While NS records for subdomains cannot be managed through the Staq dashboard, our support team is equipped to assist you. Simply provide the necessary details via a support ticket, and we’ll ensure your subdomain points to the appropriate name servers.

    Need some help?

    We all do sometimes. Please reach out to our support team by dropping us a support ticket. We will respond fast.