[BillDemirkapi]

Yes, but at the time I already had an existing domain with a web server I could use. You are correct that I could have setup a separate site for hidusi[.]com and then point the domain directly at my web server's IP, but since I already had a domain/web server configured, it was much easier just to swap the domain in the document.

[kjaftaedi]

Your comments give me the impression this isn't totally clicking just yet.

All that is necessary is to add an entry in your hosts file for hidusi[.]com that points to the IP of your existing server.

That's it. Step completed.

No localhost, no new site, just using what you have already.

In the event you are filtering hostnames on your web server, you would just add hidusi[.]com as another alias.

Please let me know if this is not clear because I believe understanding this concept will help you in the future.

[BillDemirkapi]

I can assure you the answer clicked before my research ever started. Unless I am using web server software that responds with one site for multiple host names, you generally need to configure each host name that might be used with your web server as a different "site" (i.e Apache) / configuration. I could have simply edited my hosts file with hidusi[.]com pointing to my web server and created a separate site configuration to serve the hidusi[.]com domain with the second stage. What I was saying in my last response was that instead of using my hosts and having to create this new site configuration (or modify existing with an alias), I could just swap out the domain in the document and use my web server's current state without any additional modification required. It was simply more convenient to change a single domain rather than update my web server's configuration to support requests for the hidusi[.]com alias. There is no significance to using the original domain for serving the second stage, I think you all are all just overthinking it :)