gsmith wrote:Actually, it's not so strange.
I find it strange as well. Before the request is routed to the local Apache (127.0.0.1 or similar), there must be a DNS translation from a.b.movie to 127.0.0.1 or similar. If i enter "ping a.b.movie" in a shell, i receive an answer from 127.0.53.53 - what or who is responsible for that behaviour? I dont know very much about DNS, but this really looks strange.
P.S.: I played around a little bit and found out, that "movie" is a known hostname on my PC (running Ubuntu). Therefore http://a.b.movie
can be resolved as a subdomain for "movie". If you try the same thing with an invalid hostname, for example "a.b.mofie", it cannot be resolved and the browser returns with a "ERR_NAME_NOT_RESOLVED" message. Interesting - why is "movie" assigned to 127.0.53.53??
P.P.S.: Googled around a little bit and going deeper: https://www.robtex.org/en/advisory/dns/movie/*/
(So actually - it is strange, isn't it?!). I did not know that. Did you?