Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[New Script]: Set Cloudflare DNS (Ethernet) #485

Open
P0W3 opened this issue Jan 11, 2025 · 0 comments
Open

[New Script]: Set Cloudflare DNS (Ethernet) #485

P0W3 opened this issue Jan 11, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@P0W3
Copy link

P0W3 commented Jan 11, 2025

Operating system

Windows

Name of the script

Set Cloudflare DNS (Ethernet)

Documentation/References

Using DNS from Cloudflare has significant security benefits, however it may have potential risks. This DNS enhances the user’s security protection with features such as the DNSSEC support, which helps prevent DNS spoofing attacks, DDoS mitigation, which protects against distributed denial-of-service attacks, content filtering, which blocks known malware and spam sites, and botnet protection, which blocks communication with known botnets. The 1.1.1.1 DNS resolver from Cloudflare utilizes privacy by encrypting DNS queries and using query name minimization. However, there are some considerations. While the 1.1.1.1 DNS resolver from Cloudflare enhances privacy, it does not replace VPN and does not protect against all types of attacks. Some users have reported issues with their ISPs blocking 1.1.1.1, potentially affecting its performance. DNS is part of a research project, which makes a privacy concern for users about data usage. The 1.1.1.1 DNS resolver from Cloudflare has additional security features such as free SSL certificates, automatic screening of visitors, and powerful DDoS protection through the users’ global network. So while the 1.1.1.1 DNS resolver from Cloudflare provides superb security features, it is important to understand its limitations and consider it as part of a comprehensive security strategy rather than a complete solution. This script works only with the Ethernet device.

Reference 1: https://www.cloudflare.com/learning/dns/dns-security

Code

:: ----------------------------------------------------------
:: -----------Set Cloudflare DNS (Ethernet)-----------
:: ----------------------------------------------------------
echo --- Set CloudFlare DNS (Ethernet)
:: Set the Cloudflare DNS on the Ethernet device with the primary address "1.1.1.1" and the secondary address "1.0.0.1"
PowerShell -ExecutionPolicy Unrestricted -Command "Set-DNSClientServerAddress -InterfaceAlias 'Ethernet' -ServerAddresses ('1.1.1.1','1.0.0.1')"
:: ----------------------------------------------------------

Revert code

No response

Suggested category

Security Improvements > Improve Network Security > Set Cloudflare DNS (Ethernet)

Recommendation level

Standard

Additional information

Does it really matter if the 1.1.1.1 DNS resolver from Cloudflare helps with privacy? It is probably because of the data usage that creates a privacy concern for users. Also, if the 1.1.1.1 DNS resolver from Cloudflare is a privacy concern, who knows? Maybe a user could provide another DNS address that should not break the Internet connection rules. Or a user could provide another DNS address that relies on privacy over security. Or a user could even provide another DNS address that relies on performance over everything else.

@P0W3 P0W3 added the enhancement New feature or request label Jan 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant