Closed hobybrenner closed 6 days ago
Oh and DNS Shield and Ad block etc, are disabled on UDM Pro as they were prior.
Further digging, it appears that its forwarding lookups to the servers set for the internet connection from the vlans, which are currently the legacy resolvers. Appears to be ignoring CTRLD daemon for whatever reason
I did a little more testing this morning, and it acts like dnsmasq isn't forwarding lookups to ctrld daemon. I can do a local nslookup from the unifi device pointing at 5354 and it works, so maybe something changed there. Just odd that doing the uninstall cleared things out and is now failing. The latest version seemed to work until I went back to complete that step, and hasn't worked since.
Update. Now that I had time to revisit, apparently a combo of a Magic Folder I configured previously and the uninstall to clear the interfaces triggered my condition. I removed the split route with the Magic folder, redid my install on the UDM Pro with my original toml and all is well again. Thanks.
Decided that I had a moment free to run an update this morning... bad choice.
I did the following on Unifi UDM Pro with Network 8.6.9
Upgrade Notice If your machine has virtual interfaces, it is advisable to conduct uninstallation prior to upgrading from v1.3.9 to v1.3.10.
ctrld uninstall Ensure all virtual interfaces are in correct/clean state. ctrld upgrade prod Now you can run/install ctrld as usual.
After doing so I noticed in my logs that all requests were going to my default profile via legacy resolvers.
I have several vlans and everything was fine prior to the uninstall and upgrade.
Are the virt interfaces not being reconfigured after I start the service again? I have looked at logs, and tried various configurations with my TOML, as well as multiple reboots of the UDM.
I have attached log output.
log.txt