that controls the domain is handsonhistory. Within that (Submit web site)
that controls the domain is handsonhistory. Within that domain is a subdomain called crafts. The last name (baskets) refers to a particular computer within that second-level domain. From other hosts in the second-level domain, the host can be referred to simply as baskets. From the Internet, you would refer to it as baskets.crafts.handsonhistory.com. Hostnames and IP addresses In the early days of the Internet, every known host computer name and address was collected into a file called HOSTS.TXT and distributed throughout the Internet. This quickly became cumbersome because of the size of the list and the constant changes being made to it. The solution was to distribute the responsibility for resolving hostnames and addresses to many DNS servers throughout the Internet. To make the domain names friendly, the names contain no network addresses, routes, or other information needed to deliver messages. Instead, each computer must rely on some method to translate domain names and hostnames into IP addresses. The DNS server is the primary method of resolving the names to addresses. If you request a service from a computer using a fully qualified domain name (including all domains and subdomains), it will go to the DNS server to resolve that name into an IP address. If you have a private LAN or other network, you can keep your own list of hostnames and IP addresses. For the computers you work with all the time, it s easier to type baskets than baskets.crafts.handsonhistory.com. There are a couple of ways (besides DNS) that your computer can resolve the IP address for computers for which you give only the hostname: Check the /etc/hosts file. In your computer s /etc/hosts file, you can place the names and IP addresses for the computers on your local network. In this way, your computer doesn t need to query the DNS server to get the address (which may not be there anyway if you are on a private network). Check specified domains. You can specify that if the hostname requested doesn t include a fully qualified domain name and the hostname is not in your /etc/hosts file, then your computer should check certain specified domain names. On your Red Hat Linux system, the decisions on how to try to resolve hostnames to IP addresses are taken from the /etc/resolv.conf file. That file specifies your local domain, an alternative list of domains, and the location of one or more DNS servers. Here is an example of an /etc/resolv.conf file: domain crafts.handsonhistory.com search crafts.handsonhistory.com handsonhistory.com nameserver 10.0.0.10 nameserver 10.0.0.12 In this example, the local domain is crafts.handsonhistory.com. If you try to contact a host by giving only its hostname (with no domain name), your computer can check in both crafts.handsonhistory.com and handsonhistory.com domains to find the host. If you give the fully qualified domain name, it can contact the name servers (first 10.0.0.10 and then 10.0.0.12) to resolve the address. (You can specify up to three name servers that your computer will query in order until the address is resolved.) Tip Your resolver knows to check your /etc/hosts file first because of the contents of the /etc/host.conf and /etc/nsswitch files. You can change that behavior by modifying those files. See the resolv.conf man page for further information.
Go visit our java server pages services for a reliable, lowcost webhost to satisfy all your needs.