DNS Forwarder in the last snapshots
-
Hello,
it looks like that in the last 3-4 snapshots (now I am running 2.1-RC1 (i386) - Built on Sat Aug 17 21:32:46 EDT 2013), pfSense is unable to work on the DNS server got from a PPP connection.The only way to make the DNS forwarder work is to manually add the DNS in the "General Setup" page, even if in the PPP log I can see the entries SECDNS and PRIDNS.
After I manually add the DNS in the "General Setup" page I can correctly see the entries in the "System / Resolver" log:
using nameserver 213.205.32.70#53
using nameserver 213.205.36.70#53then everything works.
Does this happens to anyone else?
Thanks,
Michele -
Yes, I'm seeing the same thing. It worked ok up through the 8/10/13 snapshot, but stopped working on the last two that I loaded, currently on
2.1-RC1 (amd64) built on Sat Aug 17 06:10:01 EDT 2013 FreeBSD 8.3-RELEASE-p9I can see the PRIDNS and SECDNS in the ppp log, but they no longer get assigned as DNS servers unless I manually add them on the general setup page. I do have the "Allow DNS server list to be overridden by DHCP/PPP on WAN" option selected. I have a single pppoe WAN interface and one LAN interface.
I'm new to pfsense, just started using it a couple of weeks ago at home and must say I'm impressed.
Bill
-
Could you maybe try to narrow it down to which specific snapshot broke that for you?
-
Seems I remember some chatter a while back about "improving" DNS. I very long thread to which I commented "I'm afraid".
Is it new and improved now or was that for another future build?
-
Specifics will help, not half-forgotten memories that may be irrelevant. If you have a link to the thread, post it. No recent commits mention DNS.
-
Here is the half remembered thread and I've no idea at all if its relevant since I wouldn't have been the changer of things in pfsense… Just seeing someone mention "broken DNS" made me wonder if its relevant.
http://forum.pfsense.org/index.php/topic,64934.msg352411.html#msg352411
(half remembered is an accurate description)
-
That wouldn't be relevant to PPP DNS.
This really isn't relevant to the DNS forwarder in general. If your PPP-assigned DNS servers aren't making it into your DNS settings (/etc/resolv.conf) then it's more likely a problem with the PPP linkup script.
-
Could you maybe try to narrow it down to which specific snapshot broke that for you?
In my case I let the system update via the web interface to the latest snapshot on the evening of 8/15/13 and when the system restarted the DNS servers were not assigned from the pppoe connection. The system was on the 8/10 snapshot prior to this and I hadn't seen the problem with that version, or any earlier versions. I did not install any of the snapshots between the 10th and 15th unfortunately. Let me know if there's any further info that might be helpful, I'm not sure if there's a record stored anywhere of the exact versions installed and when.
Bill
-
Seeing the same thing over here, for me it was 8/15 and 8/16 Snapshot.
I have not checked snapshot after 16th cus I put in DNS server manually and that fixed it. -
@val:
Seeing the same thing over here, for me it was 8/15 and 8/16 Snapshot.
I have not checked snapshot after 16th as put in DNS server manually.So 8/15 was OK and 8/16 broke it? Or did 8/15 break it (and if so, what snap were you on before 8/15?)
-
Hello,
unfortunately I can't help on this because I was in vacation for a week, then when I updated I found out this problem… :SMichele
-
15th snapshot starts to break it, before that I was on 14th snapshots.
my connection is using pppoe a vdsl2
for me DNS starts to break on this snapshot
pfSense-2.1-RC1-amd64-20130815-0311 -
If you look in /var/etc/ - do you have any "nameserver_*" files there? (Where * = your interface name)
-
This may have been caused by https://github.com/pfsense/pfsense/commit/1702a838194d2f4ffaa99359f888a42b0832472a which was accidentally put on 2.1 when it was meant for master (2.2) only, it will be gone from the next snapshot so try it again once that shows up later tonight.
-
If you look in /var/etc/ - do you have any "nameserver_*" files there? (Where * = your interface name)
there is, anything else you need?
-
This may have been caused by https://github.com/pfsense/pfsense/commit/1702a838194d2f4ffaa99359f888a42b0832472a which was accidentally put on 2.1 when it was meant for master (2.2) only, it will be gone from the next snapshot so try it again once that shows up later tonight.
Righto, thank you jimp
Val
-
This may have been caused by https://github.com/pfsense/pfsense/commit/1702a838194d2f4ffaa99359f888a42b0832472a which was accidentally put on 2.1 when it was meant for master (2.2) only, it will be gone from the next snapshot so try it again once that shows up later tonight.
Jim,
I think you were right, just updated to 2.1-RC1 (amd64) built on Mon Aug 19 16:16:39 EDT 2013 and it seems to be fixed. My nameserver_pppoe0 was empty before the update and now contains the DNS servers. I removed them from the System: General Setup screen and it's working again.
thanks,
Bill -
This may have been caused by https://github.com/pfsense/pfsense/commit/1702a838194d2f4ffaa99359f888a42b0832472a which was accidentally put on 2.1 when it was meant for master (2.2) only, it will be gone from the next snapshot so try it again once that shows up later tonight.
Jim,
I think you were right, just updated to 2.1-RC1 (amd64) built on Mon Aug 19 16:16:39 EDT 2013 and it seems to be fixed. My nameserver_pppoe0 was empty before the update and now contains the DNS servers. I removed them from the System: General Setup screen and it's working again.
thanks,
BillThx for the heads up, I am just doing the update now.
-
Hello,
I confirm, on the very last snapshot (built on Mon Aug 19 16:16:08 EDT 2013) the DNSes got from the PPP connection are successfully used, the file /var/etc/nameserver_pppoe0 contains the DNS, and everything works great again…Thanks a lot Jim!!
Michele
