>Since the DNS cache has expired, the browser resolves the DNS again. This time, my server responds with an IP of 127.0.0.1. Sounds like a normal DNS rebind, n

>Since the DNS cache has expired, the browser resolves the DNS again. This time, my server responds with an IP of 127.0.0.1. Sounds like a normal DNS rebind, nothing that is strictly a problem of ethereum. Routers have had the same exact problem for years and it's been partially solved by filtering DNS answers on their side. The easiest solution, of course, would be that browsers consider the origin of any domain pointing to 127.0.0.1 different to localhost itself. Or something in that postcode/general direction.