- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Printer Friendly Page
Best method to test Infoblox DNS Resolution as authoritative zone for test.yourdomain.com
02-05-2020 04:50 AM
We transferred a windows server DNS primary zone to Infoblox and are going to switch over the DNS resolution. I would like to ask what we need to test afterwards.
How can we ensure DNS is currently working properly pointing to Infoblox? I assume nslookups, Infoblox DNS logs to start with. Is there anything else you would test, please?
Re: Best method to test Infoblox DNS Resolution as authoritative zone for test.yourdomain.com
02-05-2020 06:50 PM
The only way to test is to perform a nslookup or dig query to the Infoblox DNS server for a record in the zone and check.
If you would like to go a step further, you can run a traffic capture on the DNS server from the GUI and perform a forward lookup to check the packet flow in detail.
Re: Best method to test Infoblox DNS Resolution as authoritative zone for test.yourdomain.com[ Edited ]
02-12-2020 09:16 AM - edited 02-12-2020 09:19 AM
Adding to the previous update
1. You can standup a LINUX machine or Windows system with WSL and use dnsperf/resperf tools to continuously monitor the server and print statistics. You can also monitor authoritative and recursive DNS resolution performance but this is very dependant on the uplink internet connection to the server and the capability of your client machine. If you are already in production, I would recommend staying away performing any stress or soak testing.
2. You can make use of Infoblox Reporting and Analytics solution which comes with various predefined reports such as DNS Query rate and respose rate per member and DNS latency trend dashboard which plots authoritative response latency which should ideally trend around 0-5 milliseconds.
3. There are a lot of stats that can be viewed using the basic CLI command "show dns stats"
4. Use SNMP polling from a monitoring tool for plotting queries, responses, reponse_type trend. You should also be able to perform periodic queries and plot both authoritative and recursive dns response latency.