DNS Resolver not working after config restore
-
@doxymoron well not every router will respond to pings but it looks like you connection dies at 74.125.50.194. Which apparently has no PTR record so not sure what that is.
Ping 8.8.8.8 continuously, do you have packet loss?
-
@steveits No, it's solid.
-
@doxymoron Long shot but does it work if you reset to defaults? Can always restore again after.
-
@steveits I just completely installed 2.6 from scratch. I'm unable to resolve anything. Something isn't right...could there be some issue at the ISP level where they are blocking pfsense as a DNS resolver? I don't get what's going on.
-
@doxymoron Can you “nslookup netgate.com 8.8.8.8” from your PC?
-
@steveits Yes that works. But when I try to nslookup using pfsense, gives me DNS request timed out.
-
@doxymoron if you enable forwarding in the Resolver settings does it work?
I mean, I suppose it’s conceivable the ISP is blocking third party DNS but I would think they’d block Google before the root servers. Awfully uncommon though. Not sure I’ve heard of blocking DNS at the ISP level.
-
@steveits So enabling forwarding worked on the fresh install. I have restored my config and made the same settings. It still did not resolve. I found this thread:
https://forum.netgate.com/topic/87141/can-t-access-internet-fresh-install/20
Which suggests doing this:
Go to Interface - WAN - Uncheck Block private networks.
I did this and now DNS Resolver is working. Interestingly, I went back and checked that box again, and it still continues to work. I really don't know why or how though...
-
@doxymoron Hmm that adds a rule to prevent incoming connections on the interface.
-
@steveits I wonder if somehow unchecking that box reset something that was in my config causing it not to work correctly? Not sure...