I have an APE HA pair across subnets on their own DNS zone (Active/Standby). When a failover occurs (manual or forced), the Standby transitions to Active, but once it becomes active the engine doesn’t function properly (polling/data collection effectively breaks). Although i can see pcap logs that suggest the newly active APE is polling correctly.
In the Web Console under **Settings → Polling Engines**, the IP address still appears to reference the previous Active member’s IP after failover, which makes me suspect name resolution/routing is not “swinging” cleanly.
The MPE cannot directly reach/query the DNS infrastructure involved with the APE HA virtual hostname updates (and/or the APE site DNS isn’t reachable from MPE).- So I’m wondering if the HA DNS update mechanism is failing or never occurring, leaving clients/components pointing at the old Active IP.
There is functionality for this to work with external scripts which I have to set the DNS virtual hostname to align to the current active APE's ip address, but even with this in place, the dbo.Engines table does not auto update the IP address once the hostname flips to the Standby server hostname, the IP address remains as the old active IP.
There is communication open between the pollers and database servers as required by solarwinds port documentation, i have ran several connection tests and that is not the issue.
