Community discussions

MikroTik App
 
kcarhc
Frequent Visitor
Frequent Visitor
Topic Author
Posts: 57
Joined: Thu Feb 01, 2018 9:54 am

FEATURE REQUEST: Add domain names as comments and static list for dns-to-address-list

Wed Jun 21, 2023 5:08 pm

What's new in 7.5 (2022-Aug-30 12:25):
*) dns - added "address-list" parameter for static DNS entries

Since the release of RouterOS 7.5, which introduced support for dns-to-address-list, many configurations that required collecting domain names have been simplified. There is no longer a need for bulky address lists to maintain the corresponding IP addresses. This feature is truly fantastic, and I appreciate MikroTik for implementing it.

However, after using it, I encountered another issue. In the list, there are numerous IP addresses, and it is difficult to determine which IP corresponds to which domain name. Every time I come across an IP, I have to check the DNS cache to find its associated domain name.

Could you consider adding a feature to address this problem? It would be helpful to have a log entry for each dns-to-address-list entry, showing the domain name that the IP is resolved to.

For example, if I configure "google.com," it would be written as an entry in DNS_GOOGLE:
Previously, there would be a list of IPs in DNS_GOOGLE like this:
/ip firewall address-list
add address=8.8.8.8 list=DNS_GOOGLE dynamic=yes
add address=142.250.204.100 list=DNS_GOOGLE dynamic=yes
With the addition of comments, it would look like this:
/ip firewall address-list
add address=8.8.8.8 list=DNS_GOOGLE dynamic=yes comment=dns.google
add address=142.250.204.100 list=DNS_GOOGLE dynamic=yes comment=www.google.com
This way, it would be clear that:
8.8.8.8 corresponds to the DNS result of dns.google
142.250.204.100 corresponds to the DNS result of www.google.com

Additionally, the current dns-to-address-list entries are added as dynamic=yes,
which means they will automatically timeout.
Could you also include an option for static listing, which will not timeout?

Of course, for now, this issue can be resolved by periodically executing CLI commands like:
/ip firewall address-list set [find list=DNS_LIST timeout!="0"] timeout="0"

Who is online

Users browsing this forum: No registered users and 3 guests