About a month ago I posted about my pfSense box that cannot resolve DNS and cannot loopback to WAN IPs (which I suspect is DNS related). A brand new box with a fresh install and the old config uploaded had the same problems, so I thought it was a config prob. It's not. Over the holidays, I reset our pfSense box to factory defaults. I didn't do anything except setup the interfaces, and pfSense still couldn't resolve DNS. So I booted the Live CD, setup interfaces (running off the CD), and it couldn't resolve DNS either. So I'm thinking it's not the config since neither a factory default or even the Live CD could resolve DNS. Our WAN's static IPs, gateway, and DNS are all the same as they were months ago when this was working for us. Hardware on old pfSense box never changed. Our internal servers use the exact same DNS as pfSense, and they're able to resolve. No problems with WAN, inbound/outbound access, VPN, etc.. Everything works except pfSense itself. Can't ping domains because it can't resolve DNS, but pinging IPs work fine. Can't download packages because it can't resolve pfSense.com. Can't sync time because it can't resolve pool.ntp.org. I've got to get this working but I'm not even sure where the problem is. How do I troubleshoot DNS inside pfSense? --Bennett
________________________________ From: Bennett Lee [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 28, 2006 10:50 PM To: [email protected] Subject: [pfSense Support] Loopback and DNS lookup fail I have a pfSense box that cannot loopback to internal addresses via WAN IPs and cannot resolve DNS (and hence cannot contact pfsense.com to download packages). Note that only pfSense itself cannot resolve DNS--our internal servers can resolve DNS using the same external name servers as pfSense. We're running 1.0.1, but this hasn't worked for us on this box since RC3 or so (I think). I have 2 other pfSense boxes and both those work fine. I couldn't figure out why this one can't loopback or resolve DNS, so I built a new pfSense box with all new hardware, installed from CD, then loaded the old config with new interface IDs. Same problem. Thus, I assume there's a problem with my config. However, I've been over and over the config and compared it to the 2 working boxes and to old config backups we have. I can't find any significant differences. I even removed all the features and rules that I could, thinking maybe I was overlooking something. Still can't get it to work. The only thing I can think to do now is to rebuild and start the setup from scratch, manually re-entering our entire config and checking after every change to see if it still works. Can anyone offer any solutions or troubleshooting advice before I'm forced to shutdown our offices for a few hours? --Bennett
