General • Re: Static DNS FWD and To AddressList, problem with cache and routes

Hi, @tamagochi! And thank you again for your post!

I apologize for not paying attention to the thread

Very kind. Don't worry too much, you're already helping!

There are many suggestions, I will try to figure it out. English is not my strong point

We also delete the vpn1_list from the list

Correctly noted! This way there will actually be significantly less action.

I didn't think about when and what should happen to the addresses - recursive route? black hole? remove?

I use this to access via VPN, sites blocked by my local providers, if that's what you're talking about.

In the address lists, we can use not only ip addresses, ip domains, but also dns names.

Yes. This is also a very good idea!

The problem you call "Dead Zone effect" (cool name, could even be the title of a game or demo)
Maybe /ip dns cache flush would solve it

No. Unfortunately, this will not help, since the root of the problem I described in the first post, is that all chrome-like browsers have their own DNS cache. And if there is still a DNS entry in the browser cache, and the corresponding entry in the router’s address list has been deleted for some reason (or has not yet been added, for example, after rebooting the router), then routing stops working because the browser does NOT make a DNS request.


First of all, the option of copying addresses from one list to another using a script frustrates me because of the need for regular processing, even while the network is idle. I agree that this looks concise and provides almost all the required functionality (however, this still does not solve the main problem with the browsers’ DNS cache).
What would be ideal is the ability to initiate the script only after adding new entries to vpn1_list1. But as far as I understand, such functionality is not provided in Mikrotik.

Statistics: Posted by taravasya — Fri Mar 08, 2024 12:43 pm

---