I mean, I’ve run into a pretty wide swath of professionals where making items like the ones you mentioned as automatic as possible can only be a good thing 
I’ve seen there’s a pretty wide range of people and companies installing equipment that needs network connectivity which doesn’t necessarily overlap 1:1 with Network Professionals at this point. Which I guess it could then be argued that they aren’t actually “Professionals”, but that’s a different line of debate I suppose.
And I hope it didn’t seem like I was trying to “gotcha” you with my question, Jeff. I was just trying to understand why people were seeing differences with this behavior after the firmware update and if there might be some way to gain some clarity there 
Interesting points here I think. Although I wonder if would be worthwhile to move that overall discussion to another thread. Not to try and play moderator here 
In regards to the DNS and as a slightly difference example, for sites where there’s a Route10 in place and a requirement to use a specific DNS server, I had already set the DNS server to be delivered to clients using DHCP which seems to have avoided anything like this behavior entirely. So at least I haven’t seen any kind of wholesale rewriting of any DNS request flowing through the router. Just to provide what behavior I’ve seen myself.
And also not to put words in anyone’s mouth, but I did want to say I think those here generally care about the equipment and how it works, at least some amount, otherwise we wouldn’t be hanging in a vendors user forum discussing the user experience. I just wanted to get that out there since sometimes I think critical discussion can be perceived as trying to wholesale bash on a product sometimes and I hope it doesn’t get taken that way.
Understood, probably not the right place to have these types of open and honest discussions.
If you can, just put yourself in our shoes for two seconds. We are a new brand, we are targeting IT professionals and MSPs, and we are trying to avoid as many user experience headaches as possible, while providing highest-level security and automatic encryption so there’s no chance for man-in-the-middle attacks (btw, almost every other vendor uses self-signed certificates…) It’s a delicate balance, and we will support many other custom features in the long-run, but our focus is on frictionless, secure, fast installs, and so we will definitely not support every single feature right out of the gates.
I’m not sure why some customers are seeing perceived differences in DNS behavior, but it’s not anything we can produce internally, so we’re just going to make DOH an option on Route10 for those that want it.
1 Like
1.4h resolves this issue with a DoH toggle
4 Likes