So here is my domain mapping. I am using nginx for the server, so the htaccess of the network setup doesn’t really apply anyway. One thing I noticed about other posts regarding this plugin was if the site url’s didn’t match exactly… would it make a difference if the admin url and front end url aren’t the same? Live sites are like yoursite.com. You log in at yoursite.com/wp-admin. But then you end up at yoursite.mysite.com/wp-admin once you are logged in. I do this so I can have better control of the dashboard experience. I could switch it so that it was yoursite.com/wp-admin, though, if that would make a difference.
Administration mapping
You can allow your members to access the administration area of your site through the domain they enter, you can also restrict it to the Mapped domain or the original domain (your website url):
original domain
Login mapping
How should your members access the login page of their website, this can be through the domain they enter, or restrict it to either the Mapped domain or the original domain (your website url):
mapped domain
Cross-domain autologin
Would you like for your members to be logged into all sites within your network regardless of domain name:
No
Verify domain’s DNS settings
Would you like to verify domain’s DNS settings before they will be mapped by your members:
No
Force http/https (Only for original domain)
Would you like to force https in login and admin pages:
No
Would you like to force http/https in front-end pages:
No
