Maybe I shouldn't have updated DNS during daylight savings hours over here in the UK.. Likely to go away after tomorrow, or is this something else? Daemon.log did complain of timestamp being in the future. Running on bullseye with latest ispconfig. Thanks Steve
Datetime values in MySQL can be in the past or future, so this should not be an issue. Try updating the DNS record again.
Solved, today but I think there's more to it. When the error occurred it was in the GUI, troubleshooting was where I spotted the 'in the future'. After the error in the GUI, I tried and retried but the error persisted, any changes to DNS for any domain or record would simply show a page in the GUI with that error at the top and nothing would be updated. I restarted services but still persisted. Changes I made to the dns were in the hours where DST ook effect. All okay today, but perhaps there is a bug somewhere and if needed I'm willing to to send it you be whatever logs you might need. Thanks dude