No no, warning is some problem and I want to know which…But I didn’t find, what kind of broblem it is (on internet).
So I don’t know, if it’s bug, or some problem on other side (NTP server). But v 6.49.6 is ok..
It’s a warning, which means very likely nothing’s gonna explode. Lack of similar warning doesn’t mean that underlying problem (whatever it might be) didn’t exist before. In any case, if nobody from MT doesn’t comment on this warning here on forum, you can open a ticket, hopefully you’ll get some sensible answer (and pass it forward to us). OTOH you can wait for next beta (or RC) to verify if the message is here to stay or not.
I’m not seeing that.
Winbox-64 v3.37 on hAP AC3 7.5beta8, using wifiwave2
Toggling mode like crazy, no crash.
I’m not seeing that.
I’m not ‘seeing’ it either. WinBox is just gone. TAB is wifi wave2, not registration (which works normal)
What happened to the scripts? The problem of the environment variables still persists.
viewtopic.php?p=944654#p944663
What’s new in 7.5beta11 (2022-Aug-17 13:14):
*) bgp - improved stability when “default-originate” is configured;
*) console - fixed automatic command completion with keypress;
*) dhcpv6-client - use /128 prefix for IA_NA addresses;
*) dns - added “address-list” parameter for static DNS entries (CLI only);
*) hotspot - improved stability when receiving bogus packets;
*) interface - fixed default interface naming on RB1100x2;
*) leds - fixed default LED configuration for RBwsAP-5Hac2nD;
*) lte - fixed AT channel for Sierra Wireless modems with device ID 0x9091;
*) ntp - fixed NTP server when “use-local-clock” is used;
*) ospf - fixed handling of external forwarding address;
*) sfp - improved stability when using 2.5G optical modules in CCR2116, CCR2216 and CRS518;
*) webfig - allow to specify NTP server as domain name;
*) winbox - enabled all filters by default under “Tools/Torch” menu;
Is this the fix we tested on 7.99 release date Aug/01 18.20.39 to fix qsfp28 stability on CCR2216?
so we can “safetly” upgrade to a testing release.
regards
Ros
Thank you Mikrotik!
Beautifull!!
*) dns - added “address-list” parameter for static DNS entries (CLI only);
WOW!
What is it?
What we also need is improvements in the inverse function:
- higher limit on the maximum number of addresses in a DNS query for an address list (specified as DNS name)
- some way to return subnets from the DNS query and insert them in the address list, e.g. TXT records with 1.2.3.0/24 content and similar.
(the DNS type APL (42) described in RFC 3123 would be ideal for that but it does not seem to be widely recognized)
I’m usually good at spotting what things are for, but I’m gonna need some help here. If I do:
/ip/dns/static add address=192.168.88.10 address-list=dnstest name=device.local ttl=600
Nothing happens at first. Then when router’s DNS resolver receives query for device.local, address list “dnstest” gets new dynamic entry with 192.168.88.10. Cool. But what can I do with it? I first thought it’s supposed to return addresses from address list, I could probably see some possible uses for that. But this?
Probably my fault, I asked for address lists in Routing Rules and it got lost in translation 
you can create address list for advertisements and null route them by DNS
[quote=Naecken post_id=948696 time=1659119517 user_id=174814]
WPA3 on 2.4GHz hAP AC3 stopped working after update from 7.4 - there is no error info in log.
[/quote]
7.5beta11 still same issue, With 7.4.1 all works fine.
Ah I thought as well that was what it would do: instead of an address you provide an address-list and it returns the address(es) in that list when the name is queried.
Apparently not?
If it would work like that, it could be used to mirror address lists between routers…
It is clearly not what I expected reading that line. Have you tried with omitting the IP address?
I expected having multiple dynamic DNS resolved in the address-list that would reflect into the static DNS and so enabling grouping of those resolves, to a custom static DNS entry.
Update: upgraded and tested, if the IP address is omitted then 0.0.0.0 is inserted. If type is stated than an error is displayed (address-list LIST exists).
add name=device.local address-list=LIST type=A
failure: bad A data: IPv4 address expected
Update two: The current working can be used as a temporary activation of a rule giving access by means of an address-list. When the DNS is resolved the TTL values starts a timer for the duration of the set TTL. But what Mikrotik had in mind with this is unknown.
My findings so far:
- if adds addresses to address list, it doesn’t get anything from address list
- it happens when first query for hostname comes and static record exists for it, then it adds its address to list
- if there are more static records with same name, it adds them all
- it uses TTL from static record as address list timeout
- subsequent queries don’t do anything (they don’t reset address list timeout as one might expect) (*1)
- you can set it for all record types, but it only does something with A/AAAA/FWD
- when used with FWD records (which are not real records, just pointers to external servers), it adds addresses from A/AAAA queries and uses their TTLs as timeout
The last thing with FWD records is something that could be possibly useful to create some dynamic access list, because such hostnames can point to different addresses not known in advance. Same could be done with A/AAAA, although if you’re adding static DNS records, you already know their addresses, so you could also add them to address list. This would just make the linking easier, but it would require a fix for (*1), because resolver returns static records with full TTL, while timeout in address list is going down until it expired and address is then removed, but at that point the client can have still valid (possibly for a long time) resolved address.
Edit: It can be a fix/workaround for using wildcards in address list. If you want hostname-based address list, it’s possible for specific hostnames:
/ip firewall address-list
add list=mikrotik address=forum.mikrotik.com
add list=mikrotik address=www.mikrotik.com
But if you want *.mikrotik.com, it’s not possible, because * can be anything, that’s too many combinations to be resolved in advance. But if you do:
/ip dns static
add address-list=mikrotik match-subdomain=yes name=mikrotik.com type=FWD
then it seems to work (I didn’t know it, but you can omit forward-to and then it uses default resolvers), you’ll get address list with addresses of actually used hostnames.
+1 for routing/rules address-lists