-
-
Notifications
You must be signed in to change notification settings - Fork 112
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
Create a DNS for just me minus VPN #21
Comments
Yes, this is possible. Do you have a static IP? It is important to do this very carefully, because creating a public DNS resolver is frowned upon, open dns resolvers can be the targets of cache poisoning attacks. |
Yes, I'd want to do this and restrict on the server side to only my IP ranges. |
This is how you would do it. Follow these portions of the guide:
After completing the Pi-Hole Installation step, go to
To ensure everything is properly firewalled:
You can use "your-external-ip" that Google Compute Engine has assigned to you as your DNS server now. You will not be able to use the Private DNS Server option on Android 9, even if you map a hostname to the Google Compute Engine IP address, because your cellular provider will not give you a static IPv4 address on your mobile phone. You can define the DNS server on WiFi networks, however. Feel free to close this issue if this answers your question, happy to elaborate further if needed. |
Brilliant! |
@rajannpatel - First of all thanks for your awesome guide! Superb work! In addition to what is discussed in this issue, I was just wondering if one can possibly setup an OpenVPN server on home router and connect GCP VM with PiHole to it using OpenVPN client & use its IP as DNS server? I have just basic networking knowledge so don't know whether this would be a recommended way to do it, though I would really love to have your inputs on this. |
Is there a way to do the pihole bit, expose DNS over the public internet via DNS+TLS or 443 (think cloudflared) and then let only my address range work with it?
The text was updated successfully, but these errors were encountered: