NO DNS after update 2.1.4 –> 2.1.5
-
I too rolled back to 2.1.4 with my 2.1.5 config and everything is working perfectly. Holding off of going back to 2.1.5
-
Went out to this site today and loaded 2.1.4 onto this box and used the config file generated with the 2.1.5 install.
DNS forwarder working as it should.
If I get brave Ill put 2.1.5 back on it and see if I can reproduce the issue.About 3 weeks ago I got brave and reinstalled 2.1.5 back at this site. As before any client attempting to use this box for its DNS would not resolve. I have "log-queries" set on the advanced config of the DNSForwarder setup and can see the queries logged, so I know they are making it to the box. The client machines simply never receive the query answers. They are however able to query public DNS fine when set to. 2.1.4 works 2.1.5 doesn't.
This site has a Statically configured WAN. "Allow DNS server list to be overridden by DHCP/PPP on WAN" unchecked. "Do not use the DNS Forwarder as a DNS server for the firewall**"** Checked.
The same week I upgraded to 2.2 beta (latest 3 weeks ago) and found this same issue was also present on 2.2. This was true of either DNSForwarder or DNSResolver. I tried a new switch and different interfaces (even though they worked with 2.1.4) As I did not want to go back to 2.1.4 I simply turned off both forwarder and resolver and let the DHCP server set the clients up with the DNS from the "General Settings" page.
This last Tuesday 10/28 I entered my choice of DNS onto the DHCP server page so the server would hand out the public DNS and turned DNSForwarder back on. This would let me troubleshoot some more without disrupting the other users.
I then proceeded to do an upgrade to the latest snapshot (built on Tue Oct 28 06:51:08 CDT 2014) and now find that the DNSForwarder is working. No other changes than described above.
Im still a little reluctant to set the clients back to using the firewall for their DNS but looks like something has changed.
Anyone else?
-
You can add me to the list of people with issues on 2.1.5 with the dnsmasq process eating 100% of a cpu thread and spotty dns functionality from clients on lan/vlan10/vlan20 dhcp'd interfaces. I have 2 Soekris net6501 boxes here on 2.1.5 -
I used my spare box to test an upgrade to 2.1.5 awhile back and left it in production with the primary sitting off to the side for a month or so. I then took the primary and put it back into play, ran the upgrade, then imported the backed up config from the backup box. I added 2 vlan interfaces to my lan interface and configured the firewall rules for the new segments and got all of that working as expected. The following morning the issues started up (or I should say users started seeing them).
At this point if there was some kind of fix in 2.2, I suppose its a debate of rolling back to 2.1.4, waiting for a 2.1.6 (if they release one with a patch for this), taking my chances on 2.2BETA in production, or waiting for 2.2 release.
