How to make domain name dns, but not a host's

Started by HarshMehra, Jul 04, 2022, 10:03 AM

Previous topic - Next topic

HarshMehraTopic starter

Hi there, I have read a lot of articles but still haven't found what I'm looking for. For instance, there's a VDS with ISP installed called Alibaba that provides hosting services. To assign a domain to the account, they require specifying DNS as and

However, the WHOIS information shows the host's DNS, which is not ideal for me. Can someone please explain how I can create DNS like ns1.mydomaine and ns2.mydomaine for a newbie like me who may not fully understand everything? Please don't get upset if I didn't explain something clearly because we've all been in that situation before.


Your writing seems to be of poor quality. Here are some suggestions on how you can resolve your DNS issues:

1. You can easily identify your hosting provider by looking up their IP address on sites like
2. To customize your DNS settings, access your ISP manager panel and set ns1.yourdomain and ns2.yourdomain as the DNS nameservers.
3. Then, in the domain name control panel on the registrar's website, add "Named DNS" and specify the IP addresses for ns1.yourdomain and ns2.yourdomain.
4. Note that some registrars may not allow this configuration if you only have one IP address.
5. In order to ensure optimal DNS setup, it's recommended that you use two different IP addresses from two different category C networks.
    The following users thanked this post: Sevad


Hi, if you want the DNS of your hosting provider, as well as information about it, not to be shown in the whois domain information, you can buy such a function as Whois information protection from the one who registered your domain. Although no matter what you do, it's impossible to hide the host.


The domain name system (DNS) is responsible for ensuring that we can use user-friendly domain names, such as "", to access websites on the internet. While devices on the internet communicate using IP addresses like "," remembering these addresses is difficult. DNS resolves this problem by translating human-readable domain names into their corresponding IP addresses.

When a domain name is entered into a browser, the computer or server automatically recognizes its IP address and sends a request to it - this process is called domain resolving. DNS comprises a hierarchical structure of domain names, including top-level domains like "com" or "org" and domain names like "" DNS servers or NS servers serve domain zones delegated to them and store resource record data for those zones. Root DNS servers store information about which DNS servers serve top-level zones. Meanwhile, DNS servers for top-level domain zones store information about which NS servers serve specific domains.

To find out an IP address, a computer or server accesses the DNS server specified in its network settings, typically the ISP's DNS server. The server checks if the domain is delegated to it and, if not, requests information about the DNS server serving that domain from the root server and then from the top-level domain zone server before making a direct request to the NS server serving the domain.


First, you need to have control over your domain name, which means you should be able to manage the DNS settings for your domain. If your domain is registered with a popular domain registrar like GoDaddy, Namecheap, or Google Domains, you can easily manage your DNS settings through their control panel.

Once you have access to your domain's DNS settings, follow these steps:

1. Log in to your domain registrar's control panel.
2. Locate the DNS management section for your domain name.
3. Look for an option to add or edit custom nameservers. This may be called "custom nameservers," "NS records," or something similar.
4. Enter the nameserver details you want, such as "ns1.mydomaine" and "ns2.mydomaine." Make sure to provide the corresponding IP addresses for these nameservers.
5. Save the changes.

After making these changes, your domain will start using the custom nameservers you specified. It may take some time for the changes to propagate across the internet, so be patient.

Keep in mind that to create custom nameservers, you generally need to have control over a server or hosting environment that can act as a nameserver. This involves setting up DNS software on a server and configuring it correctly. If you're not familiar with server administration, it might be best to consult with a professional or use the default nameservers provided by your hosting provider.

details about creating custom DNS nameservers:

1. Nameserver IP Addresses: When creating custom nameservers, you'll need to associate them with IP addresses. These IP addresses should correspond to the servers or hosting environment where your DNS records will be managed. You might need to contact your hosting provider or server administrator to obtain the IP addresses for your nameservers.

2. Glue Records: In some cases, you may also need to set up glue records. Glue records are DNS records that associate IP addresses with domain names, allowing the DNS to find the correct nameservers for a domain. Glue records are typically configured through your domain registrar's control panel. If your registrar requires glue records, you'll need to provide the IP addresses of your custom nameservers as part of this configuration.

3. DNS Zone Configuration: Once your custom nameservers are set up, you'll need to configure the DNS zone for your domain. This involves creating and managing various DNS records, such as A records, CNAMEs, MX records, and more. The exact steps for configuring your DNS zone will depend on the DNS software or control panel being used. Your hosting provider or server administrator can guide you through this process.

4. TTL (Time-to-Live): When making changes to your DNS configuration, it's important to consider the TTL value. TTL determines how long DNS resolvers and caches should store the information before checking for updates. Lower TTL values (e.g., 300 seconds) allow for faster propagation of changes, but they can put additional load on DNS infrastructure. Higher TTL values (e.g., 86400 seconds) reduce the load but may take longer for changes to take effect. It's generally recommended to set a medium TTL value like 3600 seconds (1 hour) during initial setup and adjust it as needed later.

Remember, managing DNS can be complex, so it's always a good idea to consult with professionals if you're not familiar with the process. Additionally, your hosting provider or domain registrar may have specific instructions or support resources available to help you with custom nameserver setup.