We noticed that our internet connections died after midnight (not sure when). We have a PFsense firewall/gateway that we brought up earlier this week replacing IpFire. Since I connect to PFSense via FF from my office (where the firewall/gateway server is) I had to go there to figure things out [running W11 on a gaming laptop]. So I could query it and find that it didn't have any connection on the "WAN" port. So it didn't have an IP address. This showed that the First problem was our ISP had failed. So rebooted their ONT (Modem for fiber optic connection). That did not clear up the problem. So I force booted PFsense (since I had just started using it for a firewall Gateway on Wed of this week). This was a mistake. Then I noticed that T-Bird was attempting to use a dead outlook account after upgrade to 115.2.0 and we don't know how this figured in. But in the task/msg area of Tbird it was showing it was trying to connect to this dead outlook account. So I restarted T-bird and that is when things went south. So I started using the Windows dos box and did a ping of 8.8.8.8 and that worked. So I tried a tracert of google.com tracert failed because DNS failed resolution. I also couldn't get to PFsense from FF to query it. At this point I got into Tbird and disabled the outlook account and recycled T-Bird. Immediately DNS resolutions started working and streaming devices started up (such as VOIP). FF could then get me connected to PFSense and I could logon and check it out. Not sure how this DNS issue affected things beyond the laptop but it was. The T-bird upgrade was the last thing I did the night before and it had been working until the ISP failed. Not sure how you logic works for talking to Exchange, but there might be a problem, thought you might want to know about this. Regards, Steve Thompson