Hi all experts!

What is difference between Ip based server and Namebase Server in (Linux)?

You'd need to explain in what context you saw those terms.

IP is the Internet Protocol address that the system has.

Name is the hostname/uname that a host has.

If you know the IP of a server it is faster to get to it via IP than by name. However, unless you only have a couple of servers to keep track of you typically want to use some form of name lookup as names are easier to remember than IPs (for most people).

So if you have a server with IP 192.0.1.0 and a name of ralph and you want to reach it by the name ralph from another server or device then you'd need to set up some form of name resolution. Built into UNIX/Linux is /etc/hosts where you equate the name with the IP. That works fine for individual systems but as you get more and more you don't want to update the /etc/hosts on every system. (Also if you have Windows or other devices they may not have a hosts file or not have it in the same location as UNIX/Linux). At that point you need to look at something like DNS or NIS so you have a central location for defining the lookups that you can have all of your devices interrogate for the name.

Almost all web servers nowadays host multiple web sites, or handle content for different domains. A name-based server serves several sites from the same IP address, and uses the site-name to determine what content to make available. IP-based servers map a different physical IP address for each site (although almost always to the same physical network card, or course).

In fact a server can take a mixed approach to this: serving some based n name, and some based on IP.

A common reason for using IP based serving is where you are using security certificates to verify the authenticity of your website (SSL technology - the https layer, used in e-commerce sites and so on). The certificate has to verify that the data you are looking at came from a machine that can be identified by it IP address and from a domain that matches the certificate, with the certificate itself having been issued by a known and respected certificating authority.

It's when this process falls over that your browser's anti-phishing layer kicks in and it starts complaining about mismatched certificates or unrecognised certifying bodies.

1 members found this post helpful.

i need more info in simple way please!

Those are very simple explanations, especially if you've got a RHCT. Have you actually tried to look this up online?? And MensaWater asked you a question:
which you STILL haven't answered. If you won't provide details or answer questions, there's not much we can do for you.

0 members found this post helpful.