Kinda a preference thing IMO. Leaving /ip/dhcp-server/network's DNS blank is means "inherit" the /ip/dns ones. This allows default config to work... but often being explicit in config is more clear.
The central question is whether you want Mikrotik to do DNS caching? If you do, you need to enter the Mikrotik's IP as the DNS server in the DHCP network.
e.g. if you have a lot of clients... all clients periodically resolving google.com from the internet does increase traffic. And, if you need any local name resolution, then you do need to use the router's IP in the DHCP server's networks. The flip side is Mikrotik getting involved with DNS can occasionally introduce issues/bugs/oddities, so clients using DNS directly from ISP,Google,Cloudflare,etc. avoid that potential.
The central question is whether you want Mikrotik to do DNS caching? If you do, you need to enter the Mikrotik's IP as the DNS server in the DHCP network.
e.g. if you have a lot of clients... all clients periodically resolving google.com from the internet does increase traffic. And, if you need any local name resolution, then you do need to use the router's IP in the DHCP server's networks. The flip side is Mikrotik getting involved with DNS can occasionally introduce issues/bugs/oddities, so clients using DNS directly from ISP,Google,Cloudflare,etc. avoid that potential.
Statistics: Posted by Amm0 — Tue Apr 02, 2024 7:51 pm