Hi Mark, thank you for sharing this info.
I have the same issue here, but I cannnot control the DNS environment as this is a corporate customer.
What I've found is that changing the identity in the application pool in the IIS from the default "ApplicationPoolIdentity" to a domain account "DOMAIN\account" solves the problem.
That also made me think about DNS or validation issues in the AD, because some servers work fine and some others do not.
I'll try to find out more details about the DNS servers and I'll post my findings here, as I'm also working with support on this and we could not find a solution for this
Thanks
Santi