DNAME in forward zones - issues with Microsoft Edge browser
g.clinch at lancaster.ac.uk
Wed Dec 23 11:11:31 UTC 2015
We use a DNAME record on lancaster.ac.uk and are seeing cases where
Microsoft's new Edge web browser is unable to display pages from web
servers reached via a DNAME in certain circumstances.
If you have deployed a DNAME record in a forward zone and would be
willing to help us explore the problems, please contact me off-list.
Infrastructure Systems Developer,
Lancaster University, UK
 The circumstances appear to be a bag of confusion - on the Windows
client, the gateway & DNS resolver addresses need to be the same
(standard home-router setup), the network needs to be marked as 'Private
Network' ('Find devices and content' turned on - probably a standard
home setup?), and it only breaks for Edge (IE is fine).
More information about the bind-users