NextDNS Scenario
Hello, we would like to use this solution professionally but we have some questions about how DNS filtering works.
In a per-service deployment scenario using these commands:
Invoke-WebRequest -Uri "https://nextdns.io/download/windows/stable.msi" -OutFile "$env:TEMP\NextDNSSetup.msi"
msiexec /qn /i "$env:TEMP\NextDNSSetup.msi" PROFILE=PROFILEID UI=0 ARP=0
Invoke-WebRequest -Uri "https://nextdns.io/ca" -OutFile "$env:TEMP\nextdns.cer"
certutil -addstore -f root "$env:TEMP\nextdns.cer"
In the event of a shutdown of services at NextDNS, would traffic be completely blocked or would a solution be put in place to guarantee operation with a backup secondary DNS from Google for example?
Is my traffic completely blocked if my service can no longer respond to requests submitted?
4 replies
-
What do you mean by shutdown of the service?
-
In our environment where we manage a computer park remotely, a domain name resolution problem would block all our machines.
In another scenario NextDNS closes what would happen to our stations when your services are stopped.
Thank you again for your answers, we just want to ensure that our park is not cut due to an impossible resolution.
A modification after an incident in offline mode would be unimaginable
Content aside
-
1
Likes
- 2 mths agoLast active
- 4Replies
- 103Views
-
2
Following