yaser_
asked on
how to find a computer on the internet
how a particular site/machine is traced on the internet
Certainly it involves the resolution of domain name to ip address but i require more clarification on
1.where does the domain name is resolved i.e. on which DNS server.
2.how does it traces path to the machine that contains a particular resource that is to be accessed.
thanx
Certainly it involves the resolution of domain name to ip address but i require more clarification on
1.where does the domain name is resolved i.e. on which DNS server.
2.how does it traces path to the machine that contains a particular resource that is to be accessed.
thanx
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
hi
i hav some clarification on the same question
consider a case i have DNS mapped to a particular ip (ie i have registered with a web hoster) and i need to change the DNS to some other IP (ie., i intend to have my own server ) is that i should configure my webserver alone with that DNS or how is it to be done(how will the primary dns server know that i have mapped my DNS to a new ip)
and what would happen if i have the same DNS with 2 ips (will the visitor who is located near the server will be able access the particular ip)
thanks
shiva
i hav some clarification on the same question
consider a case i have DNS mapped to a particular ip (ie i have registered with a web hoster) and i need to change the DNS to some other IP (ie., i intend to have my own server ) is that i should configure my webserver alone with that DNS or how is it to be done(how will the primary dns server know that i have mapped my DNS to a new ip)
and what would happen if i have the same DNS with 2 ips (will the visitor who is located near the server will be able access the particular ip)
thanks
shiva
yaser_:
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.
No comment has been added lately, so it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area that this question is:
Accept packratt_jk's comment as answer.
Please leave any comments here within the next seven days.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
troopern
EE Cleanup Volunteer
I will leave a recommendation in the Cleanup topic area that this question is:
Accept packratt_jk's comment as answer.
Please leave any comments here within the next seven days.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
troopern
EE Cleanup Volunteer
DNS works roughly like this... A client machine requests resolution (e.g. www.redhat.com) from their ISP's dns servers - if there is a valid (non-expired) entry in their cache from a prior similar request then that's returned. If not, the dns server will attempt to locate a definitive nameserver for the domain and query that. It works from right to left. So if its a .com address the ISP dns queries the .com root server for the NS of the domain, e.g. redhat.com . Then with that info it queries the primary nameserver, e.g. ns1.redhat.com for actual resolution of the original query. That info will then be cached and updated based on info in the query packet.
The rest is just IP routing. Your ISP's routers must either know the route (next hop) to the subnet on which the target ip address lives (216.148.218.195) or will simply send to a default route hoping that the router concerned may have a path. Routers communicate paths between themselves using protocols such as RIP. This is a whole science in its own right and the above is just a very brief summary.
Rgds