WOW… What at turd!
-
To add insult to injury, no mention in notes of deleted /etc/rc.restore_full_backup functionality!
-
The tgz is still there and can be restored manually if you want, but it shouldn't be hard to figure out why your DNS isn't working. I added a note to the change list that the feature was removed (it wasn't ever a guaranteed reliable way to downgrade). DNS obviously works for everyone else given we've been pushing 500-900 Mbps of auto update traffic and no one else has had DNS stop working.
Using dnsmasq or Unbound? Check system logs for messages about whichever one you're running.
-
Please give me a link to a 2.2.4 iso. I've already wasted 2 hours messing with this without luck. I just want to go back to 2.2.4.
I'll reinstall from scratch.
-
Are you using the DNS Forwarder (DNSMasq) or Unbound? Any errors in the system log or resolver.log? Maybe post a screenshot of the DNS Settings … No one can really help with just "lost dns resolution..."
-
Something that probably could have been fixed in minutes if you'd actually answered my questions.
Old downloads are where they always are. https://files.pfsense.org/mirror/downloads/old/
-
Upgraded to 2.3. lost dns resolution… can't restore full backup.
Way to go guys... not!
Wow… What a turd post.
There are ways to handle issues a bit better then your post.
-
Yes, agreed. Still, down for three hours now and no light in sight…. What would be a better name for such a problematic release?
-
Perhaps since you're incapable of troubleshooting if you'd answer the questions of those who are capable you'd get somewhere.
-
Based on today's posts I'm not alone. In the past one could expect to upgrade to a final release without too much need to debug, and if not satisfied could easily revert. Doesn't seem to be the case this time around.
-
Reinstall the version you came from and upload the config you saved before upgrading. Takes about 5 minutes.
-
I just updated to the release and it was as simple as click click.. If you had a problem, why don't you just download an ISO be it current or older and install clean… That you have been down for 3 hours, and all you have done is complain..
-
bit of a douchy post. no technical info, just trolling
you obviously have no intention on getting it fixed
-
I see exactly 0 other posts with broken DNS. Outside of hardware-specific issues, of which there haven't been many, I don't see any others with a complete failure.
We were serving as much as 1 update per second at peak earlier, and still 250-500 Mbps sustained now, about 20 updates every minute are happening right now. This is the highest rate of upgrades of any release we've ever done, and very few significant problem reports.
Obviously you have something wrong. But if you're unwilling to do any troubleshooting, we can't help.
-
Sure, "re-install the version I came from, and restore the config". My first thought. Can't seem to locate 2.2.4 ISO in the archives though.
-
-
Yes, agreed. Still, down for three hours now and no light in sight…. What would be a better name for such a problematic release?
maybe its a problematic user, not release?!? :o
-
Clearly some layer 8 issues for sure here..
-
This guy seems to be trolling you guys, i would just ignore him. He didnt even try and troubleshoot the issue.
Personally, I did come to the forums to see the horror stories as i never trust any pfsense release in the first month or so, double on huge branch releases!
But this was just crap. its barely a problem. so boo! i give it a 1/10 in terms of interesting issues.
-
7 out of 7 upgrades with no problems. Zilch. Nada.
-
Ok, here's some details:
Fresh install for 2.3 the restore config backup (fairly complex config with three 2 VLANS and trafic shaping)
Using unbound: No dsn resolution at all!
Using dnsmask: Partially working, can browse web sites that support IPV6. IPV4 sites, not all! (very strange).Nothing notable in system logs.
Fresh install for 2.2.4 the restore same config backup.
All is well using unbound. Have not tried dnsmask… I'm done
