What is the correct way to create your own DNS for domains? I am not knowledgeable about this topic, so I am seeking advice from someone who is.

I currently rent a basic VDS from FirstVDS and have rented an additional IP address to use as my own DNS for my domains. Specifically, I have set up the following:

ns1.mysite.com / 00.00.00.01

ns2.mysite.com / 00.00.00.02

My domains currently utilize these DNS and everything is functioning correctly.

Recently, I began renting a server from Hetzner and need to transfer all of my data to their server. I have successfully migrated files and databases using ISPmanager, but I am unsure how to update the DNS settings for all of my sites. Specifically, I want to keep ns1.mysite.com and ns2.mysite.com as the primary DNS, but only change the child DNS for mysite.com.

Since Hetzner has provided me with an IP, I asked them for a second lease to follow the same process as with FirstVDS, but they refused.

Can you provide me with guidance on how to proceed and do this correctly?

Are you experiencing an issue with the transfer process or with your BIND configuration (or any other related matter)?

In case there is insufficient IP addresses for the secondary DNS, dns.he.net offers a free service that supports both Primary and Secondary naming servers. You can choose the type of zone independently.

When initiating the transfer, all you need to do is modify the IP addresses of the DNS servers in the config and registrar, where your domain is parked. There is no need to modify their names.

To obtain additional IP addresses from Hetzner, you need to provide a valid argument. Upon approval, they will include the requested IP in the service package. Refusal reasons are also provided upon request.

If your registrar requires NS servers with different IP addresses, there are two options: acquire a second IP from Hetzner or use free Internet services (as previously mentioned) and enter their IP addresses in the domain registrar panel.

If your registrar does not require different IP addresses, assign the same IP (A-record) for ns1 and ns2 on your ns server hosted on Hetzner. Then specify ns1... and ns2... along with the same IP in the panel.

Configurations can easily be figured out with online tools. The essential A-record will lead you to the server's IP address. If previous ns rates were satisfied, keep the TTL old and update the serial number field (YYYYMMDD[nn]) in the SOA entry during config editing. No need to change cname or mx in this situation. Additional information can be found online with a simple search.

To ensure security, it is advisable to have primary and secondary DNS stored in different physical locations, even if their IP addresses are different. It is generally recommended to have them located in different countries. However, it is crucial to know what you are doing in either case.

From personal preference, I currently store my primary DNS and use BuddyNS as secondary DNS servers, which have functioned well for six months without any grievances. The synchronization between the two servers occurs instantly. Though it is free to use, I prefer to pay $5 every six months to avoid any monthly confirmations.

For those seeking confirmation of their DNS settings, there are online services provided such as intoDNS and DNSsy which can help detect mistakes before they occur.

As a side note, it is essential to secure your DNS settings as it plays a crucial role in directing traffic and ensuring internet security.

To proceed in this situation, you have a few options:

1. Use Third-Party DNS Service: Consider using a third-party DNS service like Cloudflare, Route 53, or Google Cloud DNS. These services provide robust DNS management tools and are generally more reliable than hosting your own DNS server. You can set up DNS records for your domains on these platforms and point them to the IP address of your new Hetzner server.

2. Update Domain Registrar: If you have control over your domain registrar, update the nameservers for your domains to the ones provided by the third-party DNS service you choose. This will allow you to manage DNS records directly from the DNS service's platform, decoupling it from your VDS providers.

3. Alternate DNS Methods: If you still want to host your own DNS server on the new Hetzner server, you have a couple of options. One option is to install a DNS server software like BIND or PowerDNS on the new server and configure it with the necessary DNS records. Another option is to use a DNS management tool like nsd or Knot DNS. Regardless of which method you choose, you will need to ensure that the necessary DNS records are correctly configured to point to the appropriate IP addresses.

Here are some additional steps you can consider if you choose to host your own DNS server on the new Hetzner server:

1. Set up the DNS Server: Install a DNS server software on your Hetzner server, such as BIND (Berkeley Internet Name Domain) or PowerDNS. These are popular DNS server software options that offer robust features and configuration options.

2. Configure DNS Zones: Once the DNS server software is installed, configure DNS zones for your domains. This involves setting up DNS records like A records, CNAME records, MX records, etc., specific to each domain.

3. Update Registrar's Nameservers: Log in to your domain registrar's control panel and update the nameservers for your domains to point to ns1.mysite.com and ns2.mysite.com (the primary DNS servers you set up on FirstVDS). This will delegate the DNS resolution for your domains to your own DNS servers.

4. Configure DNS Records: In your DNS server software on the Hetzner server, configure the necessary DNS records for your domains. Make sure to update the child DNS records for mysite.com to reflect the IP address of your new Hetzner server.

5. Monitor and Test: Once you have set up and configured your DNS server, regularly monitor and test its functionality. Ensure that the DNS records are resolving correctly and that there are no issues with DNS propagation.