Compare dns file validate zone

You will need to do your own research here. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Learn more. Ask Question. Asked 6 years ago. Active 6 years ago. Viewed times. As a side note, I used GoDaddy's web interface to import the zone file and it worked just fine. Because DNS lookup resolves a domain with the help of this zone file. A zone file is a text file so it can contain syntax errors.

Hence we need to check the syntax and integrity of this important configuration file. For this, we can make use of the command, named-checkzone. Alternatively, we can check the configuration file of BIND. For this, we can make use of the command, named-checkconf. The command usage is as,. In short, to check the BIND9 zone file we can use the command named-checkzone.

Today, we saw how our Support Engineers check the zone file in an Ubuntu server. Never again lose customers to poor server speed!

Let us help you. Your email address will not be published. Submit Comment. Or click here to learn more. Find centralized, trusted content and collaborate around the technologies you use most. Connect and share knowledge within a single location that is structured and easy to search. I am working on switching the nameserves of my domain to a new DNS service. What is the best tool to compare the new settings with the existing DNS setup.

I have tried to use dig with and without nameserver to allow me to make sure that the DNS records match between the old and the new provider. And yey! In inspiration from code-source's answer I created this to check from a known zone file.

Since ANY query does not output the full zone. Input is zonefile in bind format with the first field mandatory and full!! No support for empty first field or shortened yet! Stack Overflow for Teams — Collaborate and share knowledge with a private group.

The above command reads in the zone file for zone. For my last migration, I really needed to do this for both the pre- and post-migration zone file. I ended up doing something like so:. The above command wrote new canonicalized output files into prec or pre-canonical AND postc or post-canonical directories. I now had pre- and post-migration normalized data that was ready to compare. The following command can be used to compare zones:. The above command and its output, show that both zones are equivalent.

No records are missing from them, and no records are different. To interpret the output, let's discuss the columns:. There's nothing fancy about this