Thanks to Ken, and all and for an update there appears to have been a 'change' somewhere (despite the holiday!) and the address appears to be working again. As per Ken's para 2, I suspect there had been a DNS whoopsie at the host and hopefully we are sorted.