2 ms·

For what it's worth, the two names resolve to the same IP address for me. My recommendation for developers who might have this issue on their own site is to se

For what it's worth, the two names resolve to the same IP address for me. My recommendation for developers who might have this issue on their own site is to set up a redirection script at all the non-canonical names. The redirection script should redirect to the canonical name and include the full path and query string if they exist. I also take that opportunity to log the traffic so I can report on which names are generating traffic. That can help when you are deciding wether to allow names to lapse.

larrys 15y ago
The issue for me is that it required me to login again with a password because a web browser treats domain.com and domain.org as two different sites. So it didn't have my password stored. That is what brought it to my attention. And it's obviously the correct behavior from a security perspective regardless of whether it redirects to the same ip or not (you are correct though).