Good stuff as usual. You may cover this in your next video, but two other issues related to local name resolution arise if you don't use the UDM for client DNS... - on the VLAN where UniFi Devices reside, those devices will lose the ability to resolve 'unifi' which is one way they know where the controller is (may have adoption issues) - on the VLAN where your workstation is located, you will lose the ability to resolve the direct host name which allows a direct local connection when using unifi cloud management locally
These things also confuse people when they're used... - DNS Shield, will override what is set on WAN - Ad Blocking, will override what you set on LAN, but will use WAN - Content Filtering, will override what you set on LAN, and override WAN by using cleanbrowsing DNS (either family-filter or adult-filter) Local name resolution still works if using Ad Blocking and Content Filtering, but (oddly) Content Filtering will break direct local connections on a VLAN where it's enabled, so Direct Connection won't work when using unifi cloud management from a VLAN that has Content Filtering enabled.
Thanks for the suggestions. These two issues are both due to the fact that they are features of DNSmasq which runs on UniFi router. If UniFi router is bypassed, the features will be gone
great and very informative thank you
Good stuff as usual.
You may cover this in your next video, but two other issues related to local name resolution arise if you don't use the UDM for client DNS...
- on the VLAN where UniFi Devices reside, those devices will lose the ability to resolve 'unifi' which is one way they know where the controller is (may have adoption issues)
- on the VLAN where your workstation is located, you will lose the ability to resolve the direct host name which allows a direct local connection when using unifi cloud management locally
These things also confuse people when they're used...
- DNS Shield, will override what is set on WAN
- Ad Blocking, will override what you set on LAN, but will use WAN
- Content Filtering, will override what you set on LAN, and override WAN by using cleanbrowsing DNS (either family-filter or adult-filter)
Local name resolution still works if using Ad Blocking and Content Filtering, but (oddly) Content Filtering will break direct local connections on a VLAN where it's enabled, so Direct Connection won't work when using unifi cloud management from a VLAN that has Content Filtering enabled.
Thanks for the suggestions. These two issues are both due to the fact that they are features of DNSmasq which runs on UniFi router. If UniFi router is bypassed, the features will be gone
You know what? All of what you list here are already in my plan to cover in the near future:)
@@hz777 haha, good! :)
Another great video mate
Very good video, thank you 👍