Blocking access to public Pi-Hole in AWS EC2

Help
22

So I've deployed a temproary fix by doing this:

  1. Allow DNS from My Public IPv4
  2. Allow DNS from My Public IPv6 Routed range from HE

So far it seems to be working but I'm monitoring the situation and will post back my findings.
Since my network depends a lot on the IPv6 Connectivity, It is crucial for me to make it work with IPv4 & v6.

1 Like
23

I understand how important that is for it to work for you. I think you could use the AWS API to update your IPv6 address programmatically, assuming that address is dynamic, or you have a few of them. I have some minor experience with IPv6, but I see where the issue is coming from. I will look into the Hurricane Electric IPv6 Broker.

24

Address isn't dynamic, the tunnel broker allocates /64 IPv6 block and I had to whitelist the whole subnet block. I managed to do that properly this time and situation seems stable for last 24 hours.

However, the IPv6 lease expires 3 Days so I'll just revisit the situation after 3 days if that makes a difference. (And flush dns makes no difference since it uses the device Mac address to assign IPv6 and the allocated address is always the same)

26

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.