Isn't that :443 (and not :53) the newish Chrome secure DNS thing? I know it has been problematic for various reasons and this appears to be another..
I'll check some of my orgs to see if I am getting the same, but have not had any trouble tickets or noticed it yet.
- Ex community all-star (⌐⊙_⊙)