IT Contractors - Simplified example of how DNS works

Applications Support Specialist

- Applications Support Specialist (New Zealand, Wellington - Wellington CBD)

Applications Support Specialist (ERP) Our client a leading utilities company is after someone who can support and maintain an ERP system. JDE system...
Business Analyst

- Business Analyst (New Zealand, Wellington - Wellington CBD)

Business Analyst - Financial Markets - 3 months 3 month contract Competitive rates Knowledge of financial markets We are looking for a seasoned Business...
Infrastructure Suport Engineer

- Infrastructure Suport Engineer (New Zealand, Wellington - Wellington CBD)

Infrastructure Suport Engineer - contract Our client is looking for an experienced Infrastructure Engineer to provide BAU support in a predominantly Microsoft environment....

Simplified example of how DNS works

Simplified example of how DNS works

Here is just a brief and simpliefied example of how DNS works

Client enters a domain name (www.domainname.com) into his browser

The browser contacts the Client's ISP for the IP address of the domain name

The ISP first tries to answer by itself using "cached" data.

If the answer is found it is returned. Since the ISP isn't in charge of the DNS, and is just acting as a "dns relay", the answer is marked "non-authoritative"

If the answer isn't found, or it's too old (past the TTL), then the ISP DNS contacts the nameservers for the domain directly for the answer.

If the nameservers are not known, the ISP's looks for the information at the 'root servers', or 'registry servers'. For com/net/org, these start with a.gtld-servers.net.

NOTE: The 'whois' information is never used for DNS, and is often misleading and inaccurate

< Prev		Next >

[ Back ]