Web site unreachable via IP address

[macmesser]

My web site has been under development on a virtual server. I looked up the new IP for the domain but was unable to access it using the numerical web address, which produced an error page. Using my domain name gets the site. Would the correct conclusion be that the virtual server is set up for multihoming and hosts other domains, so therefore requires domain names?

Thanks for any insights.

 

[theluggage]

Would the correct conclusion be that the virtual server is set up for multihoming and hosts other domains, so therefore requires domain names?

That sounds like the most likely explanation.
Any particular reason why you want to access the site via IP address?

 

[macmesser]

That sounds like the most likely explanation.
Any particular reason why you want to access the site via IP address?

Thanks for reply. I was thinking of changing the DNS records and wanted to confirm the address.

 

[theluggage]

I'm trying to get the IP address of a website that does not respond to pings -- they time out.

Sometimes, pings are blocked by the firewall at the receiving end.

If you want the IP address do a name server lookup. There's a "lookup" facility in the Network Utility App to do this.

Each Web site on the Internet possesses at least one Internet Protocol (IP) address.

...but several websites can share the same IP address. You can register as many domain names as you like that all point to the same address, on the same server. The web server looks at the domain in the URL and decides which site the user wants.

If you try and put the IP address in the URL, you'll get the "default" site, which may be an actual site (but maybe not the one you wanted), a 'your website goes here' page or an error page.

 

[SrWebDeveloper]

Each Web site on the Internet possesses at least one Internet Protocol (IP) address. Knowing a Web site IP address can be useful to determine its physical location, but this address is not automatically shown in Web browsers.

Each web server has an IP. Some sites used name based hosting and share an IP as noted earlier. Others have proxy or load balancers ahead which are the announced IP, but use internal IP's on the actual web servers which can be routable or private. The WAN IP is based on a myriad of network setups and easily identifiable once someone knows the network setup.

So ask the webhost or ISP or "the dude who setup the web server" for the WAN IP or the IP to use to ssh or ftp. They might have a content server that propagates to the production site, or it might be a simple setup with one IP assigned to the server for ssh/ftp, but shared via name based virtual hosting.

And never rely on ping, most admins turns off IMCP for security and other concerns. If a person who knows the IP is not reachable, considering running a traceroute to the web site, it *might* reveal the IP as the last hop, but even this is not 100% reliable.