To recap in the meanwhile it gets to the Wiki:
- Concurrent Simultaneous Requests is now settable
- DNS Servers (RouteOS DNS Client Settings): goes through them sequentially passing on to the next only if it doesn't receive an answer (fails).
Further clarification regarding this on the wiki would be great, as from the current
wiki:
When both static and dynamic servers are set, static server entries are more preferred, however it does not indicate that static server will always be used (for example, previously query was received from dynamic server, but static was added later, then dynamic entry will be preferred).
Does all this get "reset" if e.g. the cache is reset? When is the Dynamic One "forgot" and the process picks back the first Server and goes down the list sequentially only if the DNS server timeouts?
Does Enabling/Disabling DNS Server impacts Client settings/behaviour in any way??
A diagram of the decision algorithm to define active DNS server when both/only multiple static & Dynamic DNS Servers are present will be really helpful.
As important as Traffic block diagram IMHO. DNS service is key, specially client portion behaviour, as it's the typical most fast/resilient setup, to point routers statically to internal cache(s) resorting to query outside DNS servers only as the last resort, putting the Mikrotik DNS Server as close to clients as possible.
however it does not indicate that static server will always be used (for example, previously query was received from dynamic server, but static was added later, then dynamic entry will be preferred
Why? It seems more natural to behave just in the opposite way; if I'm adding a new static entry, it may very possibly be because I prefer that over any dynamic, e.g. I want to include a DC, I may want to include static entries in any requests...