0

switching to paid plan

Hello Team,

i have been previewing your product for a little over 30 days now with the Windows client installed on 3 end user laptops and also running your Linked IPv4 addresses plugged into our SonicWall appliances at 3 of our SSLVPN tunneled sites. Our requirements are as follows

9 Office sites each with a SonicWall appliance all connected by SSLVPN. 

about 160 Users and end points

Right now each of the 3 office test sites has an individual profile and I will make one for each of the remain office sites

 

I have a couple of questions .

  1. If am using Linked IP for the SonicWall's does it defeat the purpose of give the users the ability to Enable/Disable the Windows client?

Our machines are domain joined so each of the larger offices has it's own Domain Controller and private DNS servers. The primary DC is located at the corporate office. All of this wonderfully syncs with Azure/O365

 I  am still having the issue of internal names resolving when using the corporate VPN, so I have been reading about the different methods on resolving that (see what  I did there?)

  1. Since we have a corporate VPN do I need to run the Windows client? I like the reporting feature that shows the machine name in the logs. I feel that is a must for troubleshooting in this size environment.
  2. What would be the cost to just use it on 9 firewalls as opposed to subscribing 150 users?
  3. What are the developer plans for this service? Is this something that we can depend on being maintained in the future for a production environment?

I have attached a screenshot of the analytics for the first 30 days on the corporate site. The other sites will not have as much traffic

 Thank you for your time and consideration in advance. 

2 replies

null
    • dnsfanboy
    • 6 mths ago
    • Reported - view

    There is like no delevoper communication at all.

    I don't know what do you mean by windows client. You can identify each user like this:

     
    DNS-over-TLS/QUIC

    Prepend the name to the provided domain (the name should only contain a-z, A-Z, 0-9 and -). Use -- for spaces.

    For "John Router", you would use John--Router-3da27f.dns.nextdns.io as your DNS-over-TLS endpoint.

    DNS-over-HTTPS

    Append the name to the provided URL (the name should be URL encoded).

    For "John's Firefox", you would use https://dns.nextdns.io/3da27f/John's%20Firefox as your DNS-over-HTTPS endpoint.

     

    Windows 11 comes with the option to put the DoH directly on the adapter and not only for the browser.

    • Michael_Minnis
    • 6 mths ago
    • Reported - view

    This is what I was referring to as the Windows client

     

Login to reply

Content aside

  • 6 mths agoLast active
  • 2Replies
  • 173Views
  • 2 Following