Azure PostgreSQL Lesson Learned#1:Fix Cannot Execute in a Read-Only Transaction After HA Failover
We encountered a support case involving Azure Database for PostgreSQL Flexible Server where the database returned a read-only error after a High Availability (HA) failover. This blog explains the root cause, resolution steps, and best practices to prevent similar issues. The issue occurred when the application attempted write operations immediately after an HA failover. The failover caused the primary role to switch, but the client continued connecting to the old primary (now standby), which is in read-only mode.Lesson Learned #495: Monitoring DNS Resolution with PowerShell of Azure SQL Server
Today, I worked on a service request where the DNS was providing an incorrect IP address randomly. In this article, I would like to share a PowerShell script that checks the DNS resolution every 5 seconds to help identify the issue.
Strange DNS problem on Server 2022
I installed a new Server 2022 DC on my network as the only DC. It serves DNS for our network and for a few weeks all has been working fine. However, lately I have been having a problem using Outlook to access my secondary email address at comcast.net. For long periods the attempt to download email fails. I did some checking and found that when I do a nslookup on imap.comcast.net I get this: Non-authoritative answer: Name: imap.comcast.net (note, there are no IP addresses) If I do the same but specify Google's DNS server (8.8.8.8) I get: Non-authoritative answer: Name: imap.ge.xfinity.com Addresses: 2001:558:fc0a:3:f816:3eff:fea5:2243 2001:558:fc0a:3:f816:3eff:fe95:679f 2001:558:fc0a:3:f816:3eff:fe0c:7c51 2001:558:fc0a:3:f816:3eff:fe51:b939 2001:558:fc0a:3:f816:3eff:fee8:1979 2001:558:fc0a:3:f816:3eff:fe6b:52a6 2001:558:fc0a:3:f816:3eff:fe5d:49ac 2001:558:fc0a:3:f816:3eff:fe84:7ff1 2001:558:fc0a:3:f816:3eff:fef5:7c75 2001:558:fc0a:3:f816:3eff:fe8d:2a36 2001:558:fc0a:3:f816:3eff:fe57:df5e 2001:558:fc11:9:f816:3eff:fee9:ffd6 2001:558:fc11:9:f816:3eff:fedd:4bc5 2001:558:fc11:9:f816:3eff:fe40:d128 2001:558:fc11:9:f816:3eff:fec1:ef59 2001:558:fc11:9:f816:3eff:fe48:d86d 96.118.18.255 96.118.18.251 96.118.18.249 96.118.18.240 96.118.18.254 96.118.17.101 96.118.17.82 96.118.18.242 96.118.19.1 96.118.19.5 96.118.18.230 96.118.17.194 96.118.18.11 96.118.19.0 96.116.224.191 96.116.224.174 Aliases: imap.comcast.netStep-by-Step: How to Configure a Private Endpoint to Secure Azure Static Web Apps
Learn how to secure your web apps with Azure Static Web Apps by configuring a private endpoint. This feature, also known as private link, allows developers to link network isolated backends for added security and seamless routing. This step-by-step guide explains the benefits and process of setting up a private endpoint in Azure Static Web Apps. Don't leave your web apps vulnerable, ensure their safety with a private endpoint.
