We are upgrading to 2016 and migrating some web applications from 2010 to 2016 using Database attach, with no 3rd party tool but just using Powershell commands. In 2010 we have 2 web applications, with several site collections in them which we decided to configure as Host Named site collections(HNSC) for capacity management reasons. So basically we are demoting 2 web apps as Host named site collections. The problem is, with HNSC's AAM (Alternate Access Mappings) is not available, and without AAM I don't know how to manage the minimal service interruption during the go-live. Does anyone know a way to redirect HNSC's ?
For example, www.my2010.com is current web app address and root site address. I am implementing this root site as HNSC in 2016.
Will it work, if I create HNSC as www.my2010.com then do the DNS switch from old 2010 server to new 2016 servers?