@dma_pf said in DNS Not Working With Phone As Peer:
@bingo600 @GenericStudent
Thanks to both of you for all of your help. I spent several hours this morning working on this issue and finally got it resolved. It was a combination of 3 different issues that resolved it.
Before I get to the solution I want to clarify that the setup I have is using a dedicated assigned interface with a gateway assigned to it for the remote access tunnel. Like this:
496c0552-b686-48e8-a473-ed95c64c0ead-image.png
181b3442-cdf2-4a90-b875-77cbdcbb8e3a-image.png
I found that first issue I had was the NAT Rule I posted above was not needed:
a5d6906c-2253-4acc-9819-437e134e3175-image.png
The second issue I had was the NAT Rule I posted above was also not needed:
d47715d8-e06f-4300-bef7-254f91def188-image.png
The reason it is not needed is because the 10.0.9.0 network is already know to pfsense through the assignment of that network to the wireguard interface and gateway. If there was no local pfsense interface assigned to that wireguard tunnel then the NAT rule would have been required.
The third issue was exactly what @bingo600 pointed out. I did need to create a rule to allow the 10.0.9.0 network to assess the DNS resolver like this:
62e2c01a-58db-42f3-b0a0-7414fceaa19d-image.png
I am very perplexed as to why that allow rule had to be created. The setting I posted above, d707a8d1-46f5-481e-8b49-caf358dfdbb1-image.png
should have allowed the DNS queries as the 10.0.9.0 network is a local pfsense network. The pfsense cleary indicates that by selecting "All" there should not need an allow rule. Per the pfsense documentation:
ab33f227-2fc2-4c90-a98e-9f56e85c129e-image.png
5ac51888-b59e-4150-8021-6bd37b34c152-image.png
I'm obviously misunderstanding something about why that access rule is required. If you can help me understand that better I'd greatly appreciate it.
Thank you guys for all of your help. I've been trying to figure this issue out for several weeks and your input got me pointed in the right direction to get it resolved. 😀
Thank you so much for this post. I was experiencing exactly the same issue and you helped to fix it!