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 :)
kjaftaedi|4 years ago
In the event you are doing virtual hosts in Apache, you just add a single line:
ServerAlias www.example.com
And your webserver will respond when queried via this hostname.
So, even in the worst case scenario, we are talking about two very basic lines of text to accomplish your goal.
The whole setup should take about 60 seconds.
I am not trying to say that your approach is wrong, but just that there is a much simpler way to go about accomplishing this goal.
As far as "overthinking it".. I think we are going to have to disagree here because I am unable to see how your method of reverse engineering can possibly be simpler than something that takes practically no time or effort.
At any rate, this is not an argument, I just want you to be aware of your options as you continue your research.
I wish you luck as you continue exploring, and thanks for the writeup :)