2.0 beta 1 embedded - DNS not working
-
Hi,
I just installed a new embedded appliance (an older neoware thin client). I'm running the mar 4 build of embedded. I imported the config from my temporary box (an old desktop), set the interfaces and was up and running. Almost.
I cannot get DNS to work on this box. I have set the servers in the General Setup page. For now, I have dnsmasq disabled as it cannot resolve queries and thus breaks internet browsing for my dhcp clients.
Pfsense itself also cannot resolve queries, whether or not dnsmasq is enabled. If I do a test query from the web interface, I get "no record found" even though it lists my dns servers and the query times below. If I log into the console and open a shell, I can only resolve queries by specifying the server. "dig google.com" times out with "no servers could be reached", but "dig@4.2.2.1 google.com" works fine. If dnsmasq is running, I get a message that the query was rejected by the server, which says to me that dnsmasq is listening but is unable to resolve queries.
I'm fine for the short term, but little things like dynamic dns don't work because the firewall can't find dyndns.org, etc.
Any ideas where to look? I don't know much about FreeBSD but my guess is that pfsense is trying to query the wrong address even though the servers are specified.
thanks,
matt
-
apologies if I'm "teaching granny to suck eggs", but have you tried creating the config from scratch to see if its something that didn't work correctly with the backup/restore process ?
Cheers
Arne
-
apologies if I'm "teaching granny to suck eggs", but have you tried creating the config from scratch to see if its something that didn't work correctly with the backup/restore process ?
Cheers
Arne
Not yet, I was hoping it wouldn't come to that as I have a good bit of time put into the current config. I suppose I could just save individual sections of it…
Also, you've taught me a new euphemism. I really appreciate that.
-M -
Ok, so I started from factory defaults and built a basic config… still nothing, exact same behavior.
-
I updated to today's build (actually just re-wrote my DOM) and all seems well.
Thanks,
Matt