Win a copy of Head First Android this week in the Android forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Jesse Silverman
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • Al Hobbs
  • salvin francis

Re : where is name resolution part

 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hai
when we put some url in web client it has to do name resolution where it takes plce.. Is it in web client(ex. IE or netscape)
 
Sheriff
Posts: 6920
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
If you mean how does your browser know where to look for a particular site, the answer is a protocol called DNS.
In a typical URL like http://www.javaranch.com/index.html
the process goes as follows:
1. your browser strips off the protocol information and local file details, leaving just the machine name (www.javaranch.com)
2. your browser requests a connection to that machine from your local tcp/ip stack.
3. the tcp/ip stack first checks to see if it knows the IP address of that machine already. If it does, it gives it back to the browser.
4. if the stack doesn't know the address already it locates the IP address of its primary DNS server and asks that machine using the DNS protocol. If that machine knows, it returns the IP address, if not, it forwards it to it's primary DNS server and so on. If the name exists, it should eventually be found, and the IP address will be returned to the browser.
5. Once the browser has an IP address for the destination machine, it can open a socket and make HTTP requests etc.
From the above I hope you can see that if the local machine doesn't know many IP addresses, it can be quite a lot of network traffic to find out about a named host machine. This is what is happening when your browser status line says something like "looking up host". For performance reasons, most machines cache the results of DNS lookups, to resuce the amount of times they have to go through the whole DNS process.
 
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic