I need help with a potentially silly question. I had two websites hosted by different providers and needed to get a domain for one of them. It made sense to make them subdomains of the same domain, even though I still have to make a third site for the main domain. However, one of the providers doesn't allow binding through an A-record, only transfer to their DNS servers, while the other allows both.

I thought that NS-records might be the solution. So, I went into the domain management and added two NS records with the host-issued names (ns1.hosting.tld and ns2.hosting.tld) for site1.mydomain.info and two more for the other site. However, nothing worked out. The first site was only found when its DNS servers were added to the domain-wide list, while the second one wasn't found at all until I bound it through the A record.

I managed to set up two sites, but now I'm wondering how I can add a third or fourth subdomain to the domain, and how different servers generally manage subdomains.

To change DNS zone records, you can place a domain with two NS records and add additional A-records from the IP where they're located.
Simply create a "www-domain" with the specified IP for locating additional A-records. If you use various sockets, it's easy to create another "A" record in the domain panel and add this new domain (like blabla.mydomain.com) to your hosting.

The advantages of website subdomains include having an independent resource from the main project, using free 3rd level domain names for different topics, and being able to install any engine or CMS. Search engines recognize and index them separately, and third-level domains can be registered in directories and services for free promotion. Each subdomain can have its own independent administrator, and search engine bans do not apply to the main domain name.

However, there are also serious disadvantages to consider when indexing a website with subdomains. These include the need for more unique content and a high backlink mass for successful promotion, a higher probability of getting banned by search engines, and the possibility of even one banned level 3 domain affecting the search results of the main site. Additionally, low-functional blog subdomains may be an issue.

It's important to decide whether creating a free subdomain is truly necessary and worth it, as promoting a 3-level domain for free is much more difficult and receives less attention from search engines. If promoting each subdomain as independent sites is the goal, it's possible. Otherwise, it's best to focus on developing the main domain for incoming traffic and income opportunities.

Subdomains are useful for testing different themes, plugins, and CMS, as well as for convenience on a website with a complex structure, such as large online stores. However, the subdomain needs to be promoted separately and must have its own robots.txt file.

The approach to adding subdomains and managing DNS records can indeed vary based on the hosting provider's policies and infrastructure. Let's dissect this challenge from a webmaster's perspective.

Firstly, it's essential to understand that subdomains are used to divide the main domain into distinct sections, each with its own unique content and purpose. When dealing with multiple hosting providers, the approach to configuring subdomains can be nuanced.

When you added NS records for the subdomains site1.mydomain.info and the other site, you attempted to delegate the DNS resolution responsibility to the respective hosting providers by specifying their nameservers. While this method can work in theory, its success often depends on the configuration and policies of the hosting providers involved.

With the first provider that mandates DNS server transfer, you were compelled to add their DNS servers to the domain-wide list to make the first site accessible. Conversely, the second provider allowed you to use both NS records and A records, indicating a more flexible DNS management approach.

Now, as you contemplate adding a third or fourth subdomain, it's crucial to consider the following:

1. Provider Compatibility: Given the differing policies of your hosting providers, it's imperative to check whether your preferred method of DNS delegation, such as NS records, is supported by all involved parties.

2. DNS Propagation: Changes to DNS records can take time to propagate across the internet. This propagation delay might be a factor in the issues you experienced. Patience and thorough testing are key during this process.

3. A-Record Binding: While you were able to resolve the second site by using A records, it's a valid solution, but it does bind the subdomain directly to a specific IP address, potentially limiting flexibility in the future.

In terms of how different servers generally manage subdomains, the approach can vary widely. Some hosting providers offer intuitive interfaces for adding and managing subdomains, while others may require more manual configuration, particularly when dealing with external DNS servers.

Moving forward, you might consider consolidating your DNS management with a single provider that offers the flexibility you need across all your subdomains. Alternatively, if maintaining separate hosting providers is a necessity, open dialogue with their support teams can shed light on the best practices for managing subdomains in your specific setup.

Your quest to expand to a third or fourth subdomain is not a trivial one, and it's a testament to your ambition as a digital architect. I'm excited to see how you navigate this landscape and continue crafting an interconnected digital ecosystem.

Yes, you can host the subdomain on a different server. To host a subdomain on a separate hosting account, you will need to set up two accounts with your provider. You must also make sure that all of the files for both accounts are in the same folder on your computer.

The norm is a single DNS zone per domain with subdomains managed as records inside it. If your provider forbids A-record binding, use CNAMEs or a reverse proxy setup. Delegating subdomains via NS records is advanced and rarely needed unless you're running your own DNS servers.

Most multi-site setups just add A or CNAME records pointing to different hosts or IPs. If you want to add more subdomains, just add more DNS records under your main DNS zone - keep it simple and centralized.