Read the article that everyone's commenting on.
Subscribe to the RSS Feed for comments on this article.
Why not just use http://www.example.com/ .net or .org instead of purchasing somerandomservice?
I'm a control freak. (Also own http://reallybigbookstore.com too.)
27-Aug-2009
Posted by: Daniel Ullman at August 26, 2009 9:23 AM
Thanks for this article. It does explain several things that very well related to the IP address and the site name. I did download Dr TCP referenced in the related article listed, to tinker with the MTU settings, but unfortunately that did not help for this particular site. It seems like they must have something wrong on their end. Thanks again.
Posted by: Wayne Urton at August 26, 2009 4:22 PM
Thanks for this article.but i have quastion, what is the information that i need if i want to visit a website using the ip address?
Posted by: Majdi at August 29, 2009 1:08 AM
When I am trying to go to google.COM from my computer in the Netherlands I am redirected to google.NL. But using the IP address 74.125.127.100 brings me to google.COM. Sometimes the search results are a bit different so I have two bookmarks for Google.
Posted by: Henk at September 1, 2009 12:25 PM
@Henk: if you need to consistently access google.com try using (once is enough) www.google.com/ncr -it will remember that you want the .com site and won't redirect you to the localized page.
Posted by: Cornel at September 4, 2009 1:08 AM
So what is the solution rather than being forced to type the entire hostname? Certainly there are some more numbers to direct to the requested page, right? I am guessing that it would be a "/" and extension provided by the webserver, and we would need that information to get it exactly right? But if that is so, isn't there a way to trace where we are actually going when we DO reach the page we first requested?
Posted by: Jerry at February 9, 2010 2:42 PM
Read the article that everyone's commenting on.
Subscribe to the RSS Feed for comments on this article.
Comments
Read the article that everyone's commenting on.
Subscribe to the RSS Feed for comments on this article.
Why not just use http://www.example.com/ .net or .org instead of purchasing somerandomservice?
27-Aug-2009
Posted by: Daniel Ullman at August 26, 2009 9:23 AM
Thanks for this article. It does explain several things that very well related to the IP address and the site name. I did download Dr TCP referenced in the related article listed, to tinker with the MTU settings, but unfortunately that did not help for this particular site. It seems like they must have something wrong on their end. Thanks again.
Posted by: Wayne Urton at August 26, 2009 4:22 PMThanks for this article.but i have quastion, what is the information that i need if i want to visit a website using the ip address?
Posted by: Majdi at August 29, 2009 1:08 AMWhen I am trying to go to google.COM from my computer in the Netherlands I am redirected to google.NL. But using the IP address 74.125.127.100 brings me to google.COM. Sometimes the search results are a bit different so I have two bookmarks for Google.
Posted by: Henk at September 1, 2009 12:25 PM@Henk: if you need to consistently access google.com try using (once is enough) www.google.com/ncr -it will remember that you want the .com site and won't redirect you to the localized page.
Posted by: Cornel at September 4, 2009 1:08 AMSo what is the solution rather than being forced to type the entire hostname? Certainly there are some more numbers to direct to the requested page, right? I am guessing that it would be a "/" and extension provided by the webserver, and we would need that information to get it exactly right? But if that is so, isn't there a way to trace where we are actually going when we DO reach the page we first requested?
Posted by: Jerry at February 9, 2010 2:42 PMTo post a comment on "Why doesn't accessing a site by its IP address work?", please return to that article's main page.