I’ll second the request from @scorp508 here.
First, many routers allow for setting a network wide DNS server.
Second, the DNS provider has the option to collect any information about every site you visit and resell it. There is a growing community which are using private DNS servers to prevent this data collection.
- Some of these servers are paid/free services.(OpenDNS)
- Some are physical hardware installed inside the network (see https://pi-hole.net/.)
Hardcoding DNS IP Addresses into the product means your users have no choice but to sell our data to these 3rd parties (I’m looking at you 220.127.116.11). Simply make the request to the network DNS and allow the users to do the DNS lookup as they please.
Finally, if you need to control exactly where my data is going (especially when you are sending it to 3rd party data logging services) then send it from your own servers, not from within my network. This product should be transparent in where our data is being sent because it contains considerable personal data.
Personal Data Sense has about me:
- A list of every electronic device in my home (including model number).
- A description of where these devices are.
- Exact frequency and and duration of use.
- Which modes they are being used in.
- When I am home/away (or at least which rooms I have lights on).
When you use a tactic like hardcoding DNS lookups in the software I have much less visibility into where you are sending my data and less control over whether I choose to share it.
I understand the pain of a user with a misconfigured network returning poor reviews, but you have pushed too far in the other direction here, and you are risking all of your data aware correctly configured network users giving 1 star reviews as well.
A second thanks to @scorp508 as well for posting the port rules to block sense DNS lookups in the meantime Static DNS Servers?