I get quite often Nameserver unstable messages from the dude for our
nameservers. Testing them with the host command in a loop is 100%
successfull and fast. Timeouts are 30s, testing for our own webservers address.
Dude 4.0b3 runs on windows7.
Anyone seen this? Any idea?
The default Dude DNS probe tests for DNS resolution of mikrotik You may find that although your own DNS server is fine, there are problems upstream that are causing issues with timeout of the resolution. Try changing the probe to resolve something that your DNS server is authoritative for.
It’s the caching Nameserver which makes problems. As this is exactly what I want to test …
As answers should come from the cache there shouldn’t be a timeout?
I cant see any delay using the host command. I’ve done a small script which does a lot
of dns-querys in a loop.