Is it a feature or a bug that RouterOS’s DoH functionality turns off local DNS static entries completely until you disable DoH completely?
I was bored and decided to enable DoH since Tik doesn’t do DNSSEC and what not but noticed my local DNS entries were ignored and sent to cloud flare to resolve until I disabled DoH and went back to the basic UDP DNS.
So I guess is this a bug or a feature in regards to this issue?
It’s definitely known. In my opinion it either bug or weird feature. I don’t remember any official comment from MikroTik, how do they see it.
LOL I’m sure they are going to ignore it and roll out RouterOS7 maybe in the next 5 years with the issue ongoing.
It is quite similar to previously repaired “*) dns - do not use DoH for local queries when a server is specified;” in 6.47.1 - in both cases DOH took priority from specified server or local static entry.
Unfortunately this is known issue (for any forum user), reported several times since 6.47 was released (possibly in earlier beta as well, but I did not follow up that one). I haven’t seen any public acknowledgement in any announcement/release topic.
Welp it's posted on here and I also put in a bug report about it since I already have a verified bug with OVPN client and non Mikrotik OVPN servers the support team has no clue why it doesn't work so if they fix those issues I might think about buying more Tik hardware after they fix it lol.
It’s weird because it’s working fine here, my static entries are working and I use doh … (I’m using 6.48, but didn’t notice a problem before).
Static entries do work, but behavior changed a bit. I’ve described the issue in v6.47 release thread.
In short:
Without DoH a single A record does cover everything. With DoH enabled it will check for AAAA record upstream.
You’re right, I confused it with FWD records. Simple ones should work (and do work for me).
Followup post with additional description: http://forum.mikrotik.com/t/v6-47-stable-is-released/140100/113