Feature request: support for DNS in packages

Really anoying part i that i should put, for example, IP for VPN servers.
Many providers have vpn server address as domain name, for example vpn.corbina.net. And they sometimes changing. And more than that - there is servers in rotation, so if one of them will fail, resolver can pick another and connect. Not in routeros, anyway…

So i ask for adding domains support in every place where it can be used -

  1. tunnels (ipip, gre, etc) - for example for connecting remote offices i can use gw1…gw2 subdomains
  2. VPN clients (already described)
  3. NTP client (pool.ntp.org will pick best server)
  4. Remote logging

Asked lots of times before. This request is several years old, actually. They simply refuse to do that. Reasons unknown.

we are considering to allow to enter domain name instead of IP address. but the problem start when this IP is entered in somewhere like firewall where a lot of traffic and it has to be resolved over and over again. that goes for logging and firewall. So in these 2 and similar places, it most probably will not happen.

why firewall? I primary ask for VPN support.

Why no cache the dns resolve in a “variable” with a “timeout” value?

ie:

/ip firewall mangle
add action=accept chain=prerouting disabled=no src-address=mikrotik.com

1st packet:

[in] ------> [mangle] ------> [domainfound] ------> [cacheddns?] ------> [no] ------> [resolve dns] ------> [internal cache domain ip for x time] ------> [apply mangle rule] ------> [out]

2nd packet:

[in] ------> [mangle] ------> [domainfound] ------> [cacheddns?] ------> [yes] ------> [read ip from cache (more faster than resolve)] ------> [apply mangle rule] ------> [out]

[…]

When the time for cache expires RouterOS resolve the dns again, this timeout must be edited by users so some people with lot of rules can give it a big timeout (ie: 10d) and people with small rules or that are using it only with VPN, NTP can give it a small timeout (some hours)