-
Notifications
You must be signed in to change notification settings - Fork 361
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
DNS setup "Setting up a VPC with site-to-site VPN in Hetzner Cloud" #639
Comments
I am having the same issue |
@zoro16 thanks for jumping in. I thought I was the only one lol |
@thetredev It turns out the Firewall Rule for LAN was blocking UDP connections, make sure the rule looks some thing like the following and try again. Edit: note that my setup is a bit different than whats in the blog |
@zoro16 awesome thank you!! That makes sense. I'm currently running a dedicated server so I don't need this specific setup anymore, but it's good to know. Leaving this issue open just in case someone stumbles upon it and struggles to find a solution. |
Problem
In that article - https://community.hetzner.com/tutorials/vpc-with-wireguard-pfsense - under Next Steps, the following is listed:
Question
How can we do that? Could you please provide a tutorial on how to make pfSense or any router OS the default nameserver for our VPC machines inside Hetzner cloud? I'm struggling to get it working myself.
Example setup on my end
Private network:
10.0.0.0/24
pfSense:
10.0.0.2
with LAN getting10.0.0.2
and gateway10.0.0.1
via DHCPClient (Debian):
10.0.0.3
can ping10.0.0.2
butnslookup google.com 10.0.0.2
results in:The text was updated successfully, but these errors were encountered: