Same NS records to multiple domain names

Started by icellular01, Nov 16, 2022, 01:40 AM

Previous topic - Next topic

icellular01Topic starter

Hey there,

I was wondering if it's possible to use the same NS records across multiple domains without any issues? Specifically, I have created NS records for example.com:

    ns1.example.com
    ns2.example.com

Along with A-records for both example.com and *.example.com, which are functioning perfectly with the server IP values. However, when I attempted to specify NS records for other domains using the aforementioned ns1 and ns2, they failed to resolve to the same IP:

    ;; connection timed out; no servers could be reached

Is it possible to have NS records from one domain work on other domains as well? Any help would be appreciated.

Thanks!
  •  

carldweb

I'm having trouble understanding what you are trying to accomplish. Typically, a record will indicate the IP address of the server hosting your website. To allow your site to be accessible from multiple domain names, you need to register A records for each domain name pointing to the same IP address.

It sounds like you might be a bit confused about NS records - they are essentially the storage location where CN, A, MX records, and others are stored. If you have multiple domains purchased from a registrar like GoDaddy, you can use their NS servers for each domain and then create the desired records within the GoDaddy settings.
  •  

MartinL

Yes, it is possible to use the same NS (Name Server) records across multiple domains without any issues. In fact, this is a common practice called "glue records." Glue records allow you to specify the authoritative name servers for a domain by including the IP addresses of those name servers along with the NS records.

The issue you mentioned, where the NS records failed to resolve to the same IP for other domains, is likely due to configuration or connectivity issues. When you create NS records for other domains using the same ns1 and ns2 values, you need to ensure that the associated name servers (ns1.example.com and ns2.example.com) are properly configured and reachable.

Here are a few things you can check to troubleshoot the issue:

1. Verify that the name servers (ns1.example.com and ns2.example.com) are correctly configured and have the appropriate DNS settings.
2. Check if the name servers are accessible from the internet and not blocked by firewalls or network restrictions.
3. Confirm that the IP addresses specified in the NS records match the IP addresses of the name servers.
4. Ensure that the DNS zone files or configurations for the other domains are correctly set up and pointing to the correct NS records.

By double-checking these factors, you should be able to resolve the connectivity issue and have the NS records from one domain work on other domains as well. If you continue to experience difficulties, it may be helpful to consult with your DNS provider or system administrator for further assistance.

additional details on using the same NS records across multiple domains:

1. Glue Records: When you register a domain, you typically specify the primary and secondary name servers provided by your DNS provider. These DNS servers are associated with glue records, which store the IP addresses of the name servers along with the NS records. Glue records are important for resolving the initial DNS lookup for your domain.

2. Name Server Configuration: To use the same NS records for multiple domains, you need to ensure that the name servers themselves are properly configured. This involves setting up the necessary DNS software, configuring zone files or databases, and specifying the appropriate DNS settings. The name servers should be able to respond to DNS queries and provide the correct information for all associated domains.

3. DNS Zone Files: Each domain has its own DNS zone file, which contains the DNS records specific to that domain. When you create NS records for other domains using the same name servers, you need to ensure that the zone files for those domains contain the correct NS records pointing to the shared name servers.

4. DNS Propagation: After making changes to your NS records, it's important to allow time for DNS propagation. This process can take up to 24-48 hours for the changes to propagate globally and for the new NS records to become effective. During this propagation period, different DNS resolvers across the internet may still cache the previous DNS information, causing temporary inconsistencies.
  •