Saturday, October 13, 2007

TECH : WEB HOSTING | SERVICE FOR UR WEB

Web hosting service

From Wikipedia, the free encyclopedia

(Redirected from Web hosting)

Ten things you may not know about images on Wikipedia

Jump to: navigation, search

Types of Internet hosting service

An example of "rack mounted" servers.

An example of "rack mounted" servers.

A web hosting service is a type of Internet hosting service that allows individuals and organizations to provide their own websites accessible via the World Wide Web. Web hosts are companies that provide space on a server they own for use by their clients as well as providing Internet connectivity, typically in a data center. Webhosts can also provide data center space and connectivity to the Internet for servers they do not own to be located in their data center, called colocation.

Contents

[hide]

Service scope

The scopes of hosting services vary widely. The most basic is webpage and small-scale file hosting, where files can be uploaded via File Transfer Protocol (FTP) or a Web interface. The files are usually delivered to the Web "as is" or with little processing. Many Internet service providers (ISPs) offer this service for free to their subscribers. People can also obtain Web page hosting from other, alternative service providers. Personal web site hosting is typically free, advertisement-sponsored, or cheap. Business web site hosting often has a higher expense.

Single page hosting is generally sufficient only for personal web pages. A complex site calls for a more comprehensive package that provides database support and application development platforms (e.g. PHP, Java, and ASP.NET). These facilities allow the customers to write or install scripts for applications like forums and content management. For e-commerce, SSL is also required.

The host may also provide an interface control panel (e.g. cPanel, Plesk or others) for managing the Web server and installing scripts as well as other services like e-mail. Recently, Web.com holds many patents it claims cover broad methods for website building and web control panels. Hostopia, a large wholesale host, recently purchased a license to use that technology from web.com for 10% of retail revenues[1]. Web.com recently sued Go Daddy as well for similar patent infringement [2].

Some hosts specialize in certain software or services (e.g. e-commerce). They are commonly used by larger companies to outsource network infrastructure to a hosting company. To find a web hosting company, there are searchable directories that can be used. One must be extremely careful when searching for a new company due to the fact that many of the people promoting service providers are actually affiliates and the reviews are biased.

Hosting reliability and uptime

Multiple racks of servers, and how a datacenter commonly looks.

Multiple racks of servers, and how a datacenter commonly looks.

Hosting uptime refers to the percentage of time the host is accessible via the internet. Many providers state that they aim for a 99.9% uptime, but there may be server restarts and planned (or unplanned) maintenance in any hosting environment.

A common claim from the popular hosting providers is '99% or 99.9% server uptime' but this often refers only to a server being powered on and doesn't account for network downtime. Real downtime can potentially be larger than the percentage guaranteed by the provider. Many providers tie uptime, and accessibility, into their own Service Level Agreement, or SLA. SLAs may or may not include refunds, or reduced costs if performance goals are not met. One must be extremely careful when selecting a new company and they should read all terms and conditions carefully. A potential customer should also check out the web hosting company's acceptable use policy (AUP) in order to avoid potential cancellation of services due to activities that are considered a violation.

Types of hosting

A typical server "cage," commonly seen in colocation centres.

A typical server "cage," commonly seen in colocation centres.

Internet hosting services can run Web servers; see Internet hosting services.

Hosting services limited to the Web:

  • Free web hosting service: is free, (sometimes) advertisement-supported web hosting, and is often limited when compared to paid hosting.
  • Shared web hosting service: one's Web site is placed on the same server as many other sites, ranging from a few to hundreds or thousands. Typically, all domains may share a common pool of server resources, such as RAM and the CPU. A shared website may be hosted with a reseller.
  • Reseller web hosting: allows clients to become web hosts themselves. Resellers could function, for individual domains, under any combination of these listed types of hosting, depending on who they are affiliated with as a provider. Resellers' accounts may vary tremendously in size: they may have their own virtual dedicated server to a colocated server.
  • Virtual Dedicated Server: slicing up a server into virtual servers. each user feels like they're on their own dedicated server, but they're actually sharing a server with many other users. The users may have root access to their own virtual space.
  • Dedicated hosting service: the user gets his or her own Web server and gains full control over it (root access for Linux/administrator access for Windows); however, the user typically does not own the server. Another type of Dedicated hosting is Self-Managed or Unmanaged. This is usually the least expensive for Dedicated plans. The user has full administrative access to the box, which means the client is responsible for the security and maintenance of his own dedicated box.
  • Managed hosting service: the user gets his or her own Web server but is not allowed full control over it (root access for Linux/administrator access for Windows); however, they are allowed to manage their data via FTP or other remote management tools. The user is disallowed full control so that the provider can guarantee quality of service by not allowing the user to modify the server or potentially create configuration problems. The user typically does not own the server. The server is leased to the client.
  • Colocation web hosting service: similar to the dedicated web hosting service, but the user owns the colo server; the hosting company provides physical space that the server takes up and takes care of the server. This is the most powerful and expensive type of the web hosting service. In most cases, the colocation provider may provide little to no support directly for their client's machine, providing only the electrical, Internet access, and storage facilities for the server. In most cases for colo, the client would have his own administrator visit the data center on site to do any hardware upgrades or changes.
  • Clustered hosting: having multiple servers hosting the same content for better resource utilization.
  • Grid hosting : relatively a new web hosting buzz, this form of distributed hosting is when a server cluster acts like a grid and is composed of multiple nodes. Being highly fault tolerant, this system is breaking new grounds when it comes to the network stability factor.

Some specific types of hosting provided by web host service providers:

Obtaining hosting

Web hosting is often provided as part of a general Internet access plan; there are many free and paid providers offering these services.

A customer needs to evaluate the requirements of the application to choose what kind of hosting to use. Such considerations include database server software, scripting software, and operating system. Most hosting providers provide Linux-based web hosting which offers a wide range of different software. A typical configuration for a Linux server is the LAMP platform: Linux, Apache, MySQL, and PHP/Perl/Python. The webhosting client may want to have other services, such as email for their business domain, databases or multi-media services for streaming media. A customer may also choose Windows for its hosting platform. The customer still can choose from PHP, Perl, and Python but may also use ASP .Net or Classic ASP.

Web hosting packages often include a Web Content Management System, so the end-user doesn't have to worry about the more technical aspects.

One may also search the Internet to find active webhosting message boards that may provide feedback on what type of webhosting company may suit his/her needs.

References

  1. ^ Yahoo! Finance: Hostopia Licenses Web.com's Patents
  2. ^ The Street: Go Daddy Gets Sued

Thursday, October 11, 2007

Sunday, October 7, 2007

MUSIC : IPOD 6th GEN | SOON


IPOD 6th Gen

AUTO : ALL NEW JAZZ | New Fit Coming

Honda new coming... New Jazz 2008










credit : www.autobytel-japan.com

TECH : Domain Name | Name for Your Site

Overview

The most common types of domain names are hostnames that provide more memorable names to stand in for numeric IP addresses. They allow for any service to move to a different location in the topology of the Internet (or an intranet), which would then have a different IP address.

By allowing the use of unique alphabetical addresses instead of numeric ones, domain names allow Internet users to more easily find and communicate with web sites and other server-based services. The flexibility of the domain name system allows multiple IP addresses to be assigned to a single domain name, or multiple domain names to be assigned to a single IP address. This means that one server may have multiple roles (such as hosting multiple independent Web sites), or that one role can be spread among many servers. One IP address can also be assigned to several servers, as used in anycast and hijacked IP space.

Hostnames are restricted to the ASCII letters "a" through "z" (case-insensitive), the digits "0" through "9", and the hyphen, with some other restrictions. Registrars restrict the domains to valid hostnames, since, otherwise, they would be useless. The Internationalized domain name (IDN) system has been developed to bypass the restrictions on character allowances in hostnames, making it easier for users of non-English alphabets to use the Internet. The underscore character is frequently used to ensure that a domain name is not recognized as a hostname, for example with the use of SRV records, although some older systems, such as NetBIOS did allow it. Due to confusion and other reasons, domain names with underscores in them are sometimes used where hostnames are required.

Examples

The following example illustrates the difference between a URL (Uniform Resource Locator) and a domain name:

URL: http://www.example.net/index.html
Domain name: www.example.net
Registered domain name: example.net

As a general rule, the IP address and the server name are interchangeable. For most Internet services, the server will not have any way to know which was used. However, the explosion of interest in the Web means that there are far more Web sites than servers. To accommodate this, the hypertext transfer protocol (HTTP) specifies that the client tells the server which name is being used. This way, one server with one IP address can provide different sites for different domain names. This feature goes under the name virtual hosting and is commonly used by Web hosts.

For example, as referenced in RFC 2606 (Reserved Top Level DNS Names), the server at IP address 192.0.34.166 handles all of the following sites:

example.com
www.example.com
example.net
www.example.net
example.org
www.example.org

When a request is made, the data corresponding to the hostname requested is served to the user.

Top-level domains

Every domain name ends in a top-level domain (TLD) name, which is always either one of a small list of generic names (three or more characters), or a two-character territory code based on ISO-3166 (there are few exceptions and new codes are integrated case by case). Top-level domains are sometimes also called first-level domains.

Other-level domains

In addition to the top-level domains, there are second-level domain (SLD) names. These are the names directly to the left of .com, .net, and the other top-level domains. As an example, in the domain en.wikipedia.org, "wikipedia" is the second-level domain.

On the next level are third-level domains. These domains are immediately to the left of a second-level domain. In the en.wikipedia.org example, "en" is a third-level domain. There can be fourth and fifth level domains and so on, with virtually no limitation. An example of a working domain with five levels is www.sos.state.oh.us. Each level is separated by a dot or period symbol between them.

Domains of third or higher level are also known as subdomains, though this term technically applies to a domain of any level, since even a top-level domain is a "subdomain" of the "root" domain (a "zeroth-level" domain that is designated by a dot alone).

Traditionally, the second level domain was the name of the company or the name used on the internet. The third level was commonly used to designate a particular host server. Therefore, ftp.wikipedia.org might be an FTP server, www.wikipedia.org would be a World Wide Web Server, and mail.wikipedia.org could be an email server. Modern technology now allows multiple servers to serve a single subdomain, or multiple protocols or domains to be served by a single computer. Therefore, subdomains may or may not have any real purpose.


Official assignment

ICANN (Internet Corporation for Assigned Names and Numbers) has overall responsibility for managing the DNS. It controls the root domain, delegating control over each top-level domain to a domain name registry. For ccTLDs, the domain registry is typically controlled by the government of that country. ICANN has a consultation role in these domain registries but is in no position to regulate the terms and conditions of how a domain name is allocated or who allocates it in each of these country level domain registries. On the other hand, generic top-level domains (gTLDs) are governed directly under ICANN which means all terms and conditions are defined by ICANN with the cooperation of the gTLD registries.

Domain names which are theoretically leased can be considered in the same way as real estate, due to a significant impact on online brand building, advertising, search engine optimization, etc.

A few companies have offered low-cost, below-cost or even free domain registrations, with a variety of models adopted to recoup the costs to the provider. These usually require that domains are hosted on their site in a framework or portal, with advertising wrapped around the user's content, revenue from which allows the provider to recoup the costs. When the DNS was new, domain registrations were free. A domain owner can generally give away or sell infinite subdomains of their domain, e.g. the owner of example.edu could provide domains that are subdomains, such as foo.example.edu and foo.bar.example.edu.

Uses and abuses

As domain names became attractive to marketers, rather than just the technical audience for which they were originally intended, they began to be used in manners that in many cases did not fit in their intended structure. As originally planned, the structure of domain names followed a strict hierarchy in which the top level domain indicated the type of organization (commercial, governmental, etc.), and addresses would be nested down to third, fourth, or further levels to express complex structures, where, for instance, branches, departments, and subsidiaries of a parent organization would have addresses which were subdomains of the parent domain. Also, hostnames were intended to correspond to actual physical machines on the network, generally with only one name per machine.

However, once the World Wide Web became popular, site operators frequently wished to have memorable addresses, regardless of whether they fit properly in the structure; thus, since the .com domain was the most popular and memorable, even noncommercial sites would often get addresses under it, and sites of all sorts wished to have second-level domain registrations even if they were parts of a larger entity where a logical subdomain would have made sense (e.g., abcnews.com instead of news.abc.com). A Web site found at http://www.example.org/ will often be advertised without the "http://", and in most cases can be reached by just entering "example.org" into a Web browser. In the case of a .com, the Web site can sometimes be reached by just entering "example" (depending on browser versions and configuration settings, which vary in how they interpret incomplete addresses).

The popularity of domain names also led to uses which were regarded as abusive by established companies with trademark rights; this was known as cybersquatting, in which somebody took a name that resembled a trademark in order to profit from traffic to that address. To combat this, various laws and policies were enacted to allow abusive registrations to be forcibly transferred, but these were sometimes themselves abused by overzealous companies committing reverse domain hijacking against domain users who had legitimate grounds to hold their names, such as their being generic words as well as trademarks in a particular context, or their use in the context of fan or protest sites with free speech rights of their own.

Laws that specifically address domain name conflicts include the Anticybersquatting Consumer Protection Act in the United States and the Trademarks Act, 1999, in India. Alternatively, domain registrants are bound by contract under the UDRP to comply with mandatory arbitration proceedings should someone challenge their ownership of the domain name.

Generic domain names — problems arising out of unregulated name selection

Within a particular top-level domain, parties are generally free to select an unallocated domain name as their own on a first come, first served basis, resulting in Harris's lament, all the good ones are taken. For generic or commonly used names, this may sometimes lead to the use of a domain name which is inaccurate or misleading. This problem can be seen with regard to the ownership or control of domain names for a generic product or service.

By way of illustration, there has been tremendous growth in the number and size of literary festivals around the world in recent years. In this context, currently a generic domain name such as literary.org is available to the first literary festival organisation which is able to obtain registration, even if the festival in question is very young or obscure. Some critics would argue that there is greater amenity in reserving such domain names for the use of, for example, a regional or umbrella grouping of festivals. Related issues may also arise in relation to non-commercial domain names.

Unconventional domain names

Due to the rarity of one-word dot-com domain names, many unconventional domain names, domain hacks, have been gaining popularity. They make use of the top-level domain as an integral part of the Web site's title. Two popular domain hack Web sites are del.icio.us and blo.gs, which spell out "delicious" and "blogs", respectively.

Unconventional domain names are also used to create unconventional email addresses. Non-working examples that spell 'James' are j@m.es and j@mes.com, which use the domain names m.es (of Spain's .es) and mes.com, respectively.

Commercial resale of domain names

An economic effect of the widespread usage of domain names has been the resale market (after-market) for generic domain names that has sprung up in the last decade. Certain domains, especially those related to business, gambling, pornography, and other commercially lucrative fields of digital world trade have become very much in demand to corporations and entrepreneurs due to their importance in attracting clients.

The most expensive public sale of an Internet domain name to date, according to DNJournal, is porn.com which was sold in 2007 for $9.5 million cash.

There are disputes about the high values of domain names claimed and the actual cash prices of many sales such Business.com. Another high-priced domain name, sex.com, was stolen from its rightful owner by means of a forged transfer instruction via fax. During the height of the dot-com era, the domain was earning millions of dollars per month in advertising revenue from the large influx of visitors that arrived daily. The sex.com sale may have never been final as the domain is still with the previous owner. Also, that sale was not just a domain but an income stream, a web site, a domain name with customers and advertisers, etc. Two long-running U.S. lawsuits resulted, one against the thief and one against the domain registrar VeriSign [1]. In one of the cases, Kremen v. Network Solutions, the court found in favor of the plaintiff, leading to an unprecedented ruling that classified domain names as property, granting them the same legal protections. In 1999, Microsoft traded the name Bob.com with internet entrepreneur Bob Kerstein for the name Windows2000.com which was the name of their new operating system. [2]

One of the reasons for the value of domain names is that even without advertising or marketing, they attract clients seeking services and products who simply type in the generic name. This is know as Direct Navigation or Type-in Traffic. Furthermore, generic domain names such as movies.com (now owned by Disney) or Books.com (now owned by Barnes & Noble) are extremely easy for potential customers to remember, increasing the probability that they become repeat customers or regular clients. In the case of Movies.com, Disney has built a stand-alone portal featuring branded content. More and more large brands are beginning to employ a more comprehensive domain strategy featuring a portfolio of thousands of domains, rather than just one or two.

Although the current domain market is nowhere as strong as it was during the dot-com heyday, it remains strong and is currently experiencing solid growth again. [3] Annually tens of millions of dollars change hands due to the resale of domains. Large numbers of registered domain names lapse and are deleted each year. On average 25,000 domain names drop (are deleted) every day.

It is very important to remember that a domain (name, address) must be valued separately from the website (content, revenue) that it is used for. The high prices have usually been paid for the revenue that was generated from the website at the domain's address (url.). The intrinsic value of a domain is the registration fee. There is no such a thing as a current market value for a domain, it just takes what somebody pays. The Fair Market Value of a domain can be anything from the registration fee: The lowest known past selling price, the highest known past selling, price, the most recent selling price, or just any past selling price and any of these (or any sum resp. division etc.) is usually added to the current or expected revenue from the web content (advertising, sales, etc.). Domain (name + ext.) should not be mixed with website (content + revenue). The estimation by appraisers are always the addition of what they would like that a domain is worth together with the effective/expected/desired revenue from the web content. Some people put value on the length of the SLD (name) and other people prefer description capability, but the shorter a SLD is, the less descriptive it can be. Also, if short is crucial, then the TLD (extension) should be short too. It is less realistic to get a domain like LL.travel or LL.mobi than a domain travel.LL or mobi.LL. This illustrates the relativity of domain value estimation. It can be safely put that the revenue af a web (content) can be easily stated, but that the value of a domain (SLD.TLD aka name.ext) is a matter of opinions and preferences. In the end, however, any sale depend of the estimates by the domain seller and the domain buyer.

People who buy and sell domain names are known as domainers. People who sell value estimation services are known as appraisers.

According to Guinness World Records and MSNBC, the most expensive domain name sales on record as of 2004 were: Business.com for $7.5 million in December 1999, AsSeenOnTv.com for $5.1 million in January 2000, Altavista.com for $3.3 million in August 1998, Wine.com for $2.9 million in September 1999, CreditCards.com for $2.75 million in July 2004, and Autos.com for $2.2 million in December 1999.

Domain name confusion

Intercapping is often used to clarify a domain name. However, DNS is case-insensitive, and some names may be misinterpreted when converted to lowercase. For example: Who Represents, a database of artists and agents, chose whorepresents.com; a therapists' network thought therapistfinder.com looked good; and another website operating as of August 2007, is penisland.net a website for Pen Island, a site that claims to be an online pen vendor, but exists primarily as a joke, as it has no products for sale. Other examples include cummingfirst.com, website of the Cumming First United Church in Cumming, GA and powergenitalia.com, a website for an Italian Power Generator company. In such situations, the proper wording can be clarified by use of hyphens. For instance, Experts Exchange, the programmers' site, for a long time used expertsexchange.com, but ultimately changed the name to experts-exchange.com.

Leo Stoller threatened to sue the owners of StealThisEmail.com on the basis that, when read as stealthisemail.com, it infringed on claimed trademark rights to the word "stealth".



Saturday, October 6, 2007

TECH : Domain name System | The History




Domain Name System

On the Internet, the Domain Name System
(DNS) associates various sorts of information with so-called domain names; most importantly, it serves as the "phone book" for the Internet by translating human-readable computer hostnames, e.g. en.wikipedia.org, into the IP addresses, e.g. 66.230.200.100, that networking equipment needs for delivering information. It also stores other information such as the list of mail exchange servers that accept email for a given domain. In providing a worldwide keyword-based redirection service, the Domain Name System is an essential component of contemporary Internet use.

Uses

The most basic use of DNS is to translate hostnames to IP addresses. It is in very simple terms like a phone book. For example, if you want to know the internet address of en.wikipedia.org, the Domain Name System can be used to tell you it is 145.97.39.155. DNS also has other important uses.

Preeminently, DNS makes it possible to assign Internet destinations to the human organization or concern they represent, independently of the physical routing hierarchy represented by the numerical IP address. Because of this, hyperlinks and Internet contact information can remain the same, whatever the current IP routing arrangements may be, and can take a human-readable form (such as "wikipedia.org") which is rather easier to remember than an IP address (such as 66.230.200.100). People take advantage of this when they recite meaningful URLs and e-mail addresses without caring how the machine will actually locate them.

The Domain Name System (DNS) distributes the responsibility for assigning domain names and mapping them to IP networks by allowing an authoritative server for each domain to keep track of its own changes, avoiding the need for a central registrar to be continually consulted and updated.

History

The practice of using a name as a more human-legible abstraction of a machine's numerical address on the network predates even TCP/IP, and goes all the way to the ARPAnet era. Back then however, a different system was used, as DNS was only invented in 1983, shortly after TCP/IP was deployed. With the older system, each computer on the network retrieved a file called HOSTS.TXT from a computer at SRI (now SRI International). The HOSTS.TXT file mapped numerical addresses to names. A hosts file still exists on most modern operating systems, either by default or through configuration, and allows users to specify an IP address (eg. 192.0.34.166) to use for a hostname (eg. www.example.net) without checking DNS. As of 2006, the hosts file serves primarily for troubleshooting DNS errors or for mapping local addresses to more organic names. Systems based on a hosts file have inherent limitations, because of the obvious requirement that every time a given computer's address changed, every computer that seeks to communicate with it would need an update to its hosts file.

The growth of networking called for a more scalable system: one that recorded a change in a host's address in one place only. Other hosts would learn about the change dynamically through a notification system, thus completing a globally accessible network of all hosts' names and their associated IP Addresses.

At the request of Jon Postel, Paul Mockapetris invented the Domain Name System in 1983 and wrote the first implementation. The original specifications appear in RFC 882 and 883. In November 1987, the publication of RFC 1034 and RFC 1035 updated the DNS specification[1]RFC 882 and RFC 883 obsolete. Several more-recent RFCs have proposed various extensions to the core DNS protocols. and made

In 1984, four Berkeley students — Douglas Terry, Mark Painter, David Riggle and Songnian Zhou — wrote the first UNIX implementation, which was maintained by Ralph Campbell thereafter. In 1985, Kevin Dunlap of DEC significantly re-wrote the DNS implementation and renamed it BINDPaul Vixie have maintained BIND since then. BIND was ported to the Windows NT (Berkeley Internet Name Domain, previously: Berkeley Internet Name Daemon). Mike Karels, Phil Almquist and platform in the early 1990s.

Due to BIND's long history of security issues and exploits, several alternative nameserver/resolver programs have been written and distributed in recent years.


How DNS works in theory

The domain name space consists of a tree of domain names. Each node or leaf in the tree has one or more resource records, which hold information associated with the domain name. The tree sub-divides into zones. A zone consists of a collection of connected

nodes authoritatively served by an authoritative DNS nameserver. (Note that a single nameserver can host several zones.)

When a system administrator wants to let another administrator control a part of the domain name space within his or her zone of authority, he or she can del

egate control to the other administrator. This splits a part of the old zone off into a new zone, which comes under the authority of the second administrator's nameservers. The old zone becomes no longer authoritative for what goes under the authority of the new zone.

A resolver looks up the information associated with nodes. A resolver knows how to communicate with name servers by sending DNS requests, and heeding DNS responses. Resolving usually entails iterating through several name servers to find the needed information.

Some resolvers function simplistically and can only communicate with a single name server. These simple resolvers rely on a recursing name server to perform the work of finding information for them.


Parts of a domain name

A domain name usually consists of two or more parts (technically labels), separated by dots. For example wikipedia.org.

  • The rightmost label conveys the top-level domain (for example, the address en.wikipedia.org has the top-level domain org).
  • Each label to the left specifies a subdivision or subdomain of the domain above it. Note that "subdomain" expresses relative dependence, not absolute dependence: for example, wikipedia.org comprises a subdomain of the org domain, and en.wikipedia.org comprises a subdomain of the domain wikipedia.org. In theory, this subdivision can go down to 127 levels deep, and each label can contain up to 63 characters, as long as the whole domain name does not exceed a total length of 255 characters. But in practice some domain registries have shorter limits than that.
  • A hostname refers to a domain name that has one or more associated IP addresses. For example, the en.wikipedia.org and wikipedia.org domains are both hostnames, but the org domain is not.

The Domain Name System consists of a hierarchical set of DNS servers. Each domain or subdomain has one or more authoritative DNS servers that publish information about that domain and the name servers of any domains "beneath" it. The hierarchy of authoritative DNS servers matches the hierarchy of domains. At the top of the hierarchy stand

the root nameservers: the servers to query when looking up (resolving) a top-level domain name (TLD).

Iterative and recursive queries:

  • An Iterative query is one where the DNS server may provide a partial answer to the query (or give an error). DNS servers must support non-recursive queries.
  • A recursive query is one where the DNS server will fully answer the query (or give an error). DNS servers are not required to support recursive queries an d both the resolver (or another DNS acting recursively on behalf of another resolver) negotiate use of recursive service using bits in the query headers.

Address resolution mechanism

(This description deliberately uses the fictional .example TLD in accordan ce with the DNS guidelines themselves.)

In theory a full host name may have several name segments, (e.g ahost.ofasubnet.ofabiggernet.inadomain.example). In practice, in the experience of the majority of public users of Internet services, full host names will frequently consist of just three segments (ahost.inadomain.example, and most often www.inadomain.example).

For querying purposes, software interprets the name segment by segment, from rig

ht to left, using an iterative search procedure. At each step along the way, the program queries a corresponding DNS server to provide a pointer to the next server which it should consult.


As originally envisaged, the process was as simple as:

  1. the local system is pre-configured with the known addresses of the root servers in a file of root hints, which need to be updated periodically by the local administrator from a reliable source to be kept up to date with the changes which occur over time.
  2. query one of the root servers to find the server authoritative for the next level down (so in the case of our simple hostname, a root server would be asked for the address of a server with detailed knowledge of the example top level domain).
  3. querying this second server for the address of a DNS server with detailed knowledge of the second-level domain (inadomain.example in our example).
  4. repeating the previous step to progress down the name, until the final step which would, rather than generating the address of the next DNS server, return the final address sought.

The diagram illustrates this process for the real host www.wikipedia.org.

The mechanism in this simple form has a difficulty: it places a huge operating burden on the root servers, with each and every search for an address starting by querying one of them. Being as critical as they are to the overall function of the system such heavy use would create an insurmountable bottleneck for trillions of queries placed every day. The section DNS in practice describes how this is addressed.


Circular dependencies and glue records

Name servers in delegations appear listed by name, rather than by IP address. This means that a resolving name server must issue another DNS request to find out the IP address of the server to which it has been referred. Since this can introduce a circular dependency if the nameserver referred to is under the domain that it is authoritative of, it is occasionally necessary for the nameserver providing the delegation to also provide the IP address of the next nameserver. This record is called a glue record.

For example, assume that the sub-domain en.wikipedia.org contains further sub-domains (such as something.en.wikipedia.org) and that the authoritative nameserver for these lives at ns1.something.en.wikipedia.org. A computer trying to resolve something.en.wikipedia.org will thus first have to resolve ns1.something.en.wikipedia.org. Since ns1 is also under the something.en.wikipedia.org subdomain, resolving something.en.wikipedia.org requires resolving ns1.something.en.wikipedia.org which is exactly the circular dependency mentioned above. The dependency is broken by the glue record in the nameserver of en.wikipedia.org that provides the IP address of ns1.something.en.wikipedia.org directly to the requestor, enabling it to bootstrap the process by figuring out where ns1.something.en.wikipedia.org is located.

In practice

When an application (such as a web browser) tries to find the IP address of a domain name, it doesn't necessarily follow all of the steps outlined in the Theory section above. We will first look at the concept of caching, and then outline the operation of DNS in "the real world."

Caching and time to live

Because of the huge volume of requests generated by a system like DNS, the designers wished to provide a mechanism to reduce the load on individual DNS servers. To this end, the DNS resolution process allows for caching (i.e. the local recording and subsequent consultation of the results of a DNS query) for a given period of time after a successful answer. How long a resolver caches a DNS response (i.e. how long a DNS response remains valid) is determined by a value called the time to live (TTL). The TTL is set by the administrator of the DNS server handing out the response. The period of validity may vary from just seconds to days or even weeks.

Caching time

As a noteworthy consequence of this distributed and caching architecture, changes to DNS do not always take effect immediately and globally. This is best explained with an example: If an administrator has set a TTL of 6 hours for the host www.wikipedia.org, and then changes the IP address to which www.wikipedia.org resolves at 12:01pm, the administrator must consider that a person who cached a response with the old IP address at 12:00pm will not consult the DNS server again until 6:00pm. The period between 12:01pm and 6:00pm in this example is called caching time, which is best defined as a period of time that begins when you make a change to a DNS record and ends after the maximum amount of time specified by the TTL expires. This essentially leads to an important logistical consideration when making changes to DNS: not everyone is necessarily seeing the same thing you're seeing. RFC 1537 helps to convey basic rules for how to set the TTL.

Note that the term "propagation", although very widely used in this context, does not describe the effects of caching well. Specifically, it implies that [1] when you make a DNS change, it somehow spreads to all other DNS servers (instead, other DNS servers check in with yours as needed), and [2] that you do not have control over the amount of time the record is cached (you control the TTL values for all DNS records in your domain, except your NS records and any authoritative DNS servers that use your domain name).

Some resolvers may override TTL values, as the protocol supports caching for up to 68 years or no caching at all. Negative caching (the non-existence of records) is determined by name servers authoritative for a zone which MUST include the SOA record when reporting no data of the requested type exists. The MINIMUM field of the SOA record and the TTL of the SOA itself is used to establish the TTL for the negative answer. RFC 2308

Many people incorrectly refer to a mysterious 48 hour or 72 hour propagation time when you make a DNS change. When one changes the NS records for one's domain or the IP addresses for hostnames of authoritative DNS servers using one's domain (if any), there can be a lengthy period of time before all DNS servers use the new information. This is because those records are handled by the zone parent DNS servers (for example, the .com DNS servers if your domain is example.com), which typically cache those records for 48 hours. However, those DNS changes will be immediately available for any DNS servers that do not have them cached. And any DNS changes on your domain other than the NS records and authoritative DNS server names can be nearly instantaneous, if you choose for them to be (by lowering the TTL once or twice ahead of time, and waiting until the old TTL expires before making the change).



AUTO : ALL NEW DEMIO | City Car # 2


Zoom Zoom ...


Zoom...Zoom... in 2008

Link :
www.demio.mazda.co.jp