... | ... | @@ -80,13 +80,13 @@ Now that there is a problem, how do I troubleshoot it? |
|
|
|
|
|
--------
|
|
|
|
|
|
BIND/DNS User
|
|
|
## BIND/DNS User
|
|
|
|
|
|
The typical BIND user who might try Stork is going to already have other tools for managing BIND. Most BIND users have nagios, zabbix or cacti or something similar for fault management. They will also have Provisioning systems vary widely, but there are many open source tools out there for zone file provisioning, as well as many home-grown tools.
|
|
|
BIND users know they have to be able to mine the logs for information. Information about how to set up logs, what to look for - these are the hottest queries in the KB and the most popular webinars. However, over-logging can seriously impact BIND performance.
|
|
|
BIND users have been asking for a supported Prometheus exporter, because it is essential in DNS to monitor the query make-up to spot DDOS attacks.
|
|
|
* The typical BIND user who might try Stork is going to already have other tools for managing BIND. Most BIND users have nagios, zabbix or cacti or something similar for fault management. They will also have Provisioning systems vary widely, but there are many open source tools out there for zone file provisioning, as well as many home-grown tools.
|
|
|
* BIND users know they have to be able to mine the logs for information. Information about how to set up logs, what to look for - these are the hottest queries in the KB and the most popular webinars. However, over-logging can seriously impact BIND performance.
|
|
|
* BIND users have been asking for a supported Prometheus exporter, because it is essential in DNS to monitor the query make-up to spot DDOS attacks.
|
|
|
|
|
|
These users are looking for are solutions for problems they can't address with existing tools. These include:
|
|
|
- troubleshooting performance problems. This requires looking at the platform, and the application together. It also requires, ultimately, also looking at configuration options that affect performance.
|
|
|
These users are looking for are solutions for problems they can't address with existing tools. By definition, none of these are simple problems and all will likely require work in BIND as well as in Stork. These include:
|
|
|
- troubleshooting performance problems. This requires looking at the platform, activity, and the application together. It also requires, ultimately, also looking at configuration options that affect performance.
|
|
|
- troubleshooting issues related to what is in cache. This may require looking at data in the ADB which is not currently exposed to the user.
|
|
|
- monitoring and troubleshooting issues related to zone file updates. These can impact query performance. In case of signed zones, this may also require monitoring signing operations, which can take a long time (e.g. an hour) in case of very large zone files. |
|
|
\ No newline at end of file |