Thursday, November 5, 2015
DNS Server
Domain Name System (DNS) is a distributed hierarchical naming system for computers, services, or any resource that is connected to the Internet or private networks. It associates various information with domain names assigned to each of the participating entities. Most importantly, translates domain names meant for humans to numeric identifiers associated with networking equipment for the purpose of finding and handling these devices worldwide.
A DNS server is any computer registered to join the Domain Name System. A DNS server running special purpose software, features a public IP address, and contains a database of network names and addresses to other Internet hosts.
DNS Root Servers DNS servers communicate with each other using private network protocols. All DNS servers arranged in a hierarchy. At the peak level of the hierarchy, so-called root servers store the complete database of Internet domain names and their corresponding IP addresses. Internet employs 13 root servers that have become somewhat famous for their special role. Maintained by various independent institutions, the server is aptly named A, B, C and so on up to M. Ten of these servers are in the United States, one in Japan, one in London, England and one in Stockholm, Sweden.
DNS Server Hierarchy DNS is a distributed system, which means that only 13 root servers contain a complete database of domain names and IP addresses. All other DNS servers are installed at a lower level of the hierarchy and only maintain a certain piece of the overall database. Most of the lower level DNS servers that are owned by businesses or Internet Service Provider (ISP). For example, Google maintains a variety of DNS servers around the world who manage google.com, google.co.uk, and other domains. Your ISP also maintains a DNS server as part of the setup of your Internet connection. Control network architecture based on client / server. Your Web browser function as a DNS client (also called DNS resolver) and issues a request to your Internet provider's DNS server when navigating between Web sites. When the DNS server receives the request does not exist in its database (such as geographical distance or Web sites rarely visited), to temporarily change the DNS server to the client. Server automatically passes the request to another DNS server or up to the next higher level in the hierarchy of control is required. Finally, the request arrives at a server that has a suitable name and IP address in its database (all the way to the root if necessary), and responses to flow back through the chain of DNS servers for your clients.
DNS Root Servers DNS servers communicate with each other using private network protocols. All DNS servers arranged in a hierarchy. At the peak level of the hierarchy, so-called root servers store the complete database of Internet domain names and their corresponding IP addresses. Internet employs 13 root servers that have become somewhat famous for their special role. Maintained by various independent institutions, the server is aptly named A, B, C and so on up to M. Ten of these servers are in the United States, one in Japan, one in London, England and one in Stockholm, Sweden.
DNS Server Hierarchy DNS is a distributed system, which means that only 13 root servers contain a complete database of domain names and IP addresses. All other DNS servers are installed at a lower level of the hierarchy and only maintain a certain piece of the overall database. Most of the lower level DNS servers that are owned by businesses or Internet Service Provider (ISP). For example, Google maintains a variety of DNS servers around the world who manage google.com, google.co.uk, and other domains. Your ISP also maintains a DNS server as part of the setup of your Internet connection. Control network architecture based on client / server. Your Web browser function as a DNS client (also called DNS resolver) and issues a request to your Internet provider's DNS server when navigating between Web sites. When the DNS server receives the request does not exist in its database (such as geographical distance or Web sites rarely visited), to temporarily change the DNS server to the client. Server automatically passes the request to another DNS server or up to the next higher level in the hierarchy of control is required. Finally, the request arrives at a server that has a suitable name and IP address in its database (all the way to the root if necessary), and responses to flow back through the chain of DNS servers for your clients.
DNS Server and Home Network Computers on your home network to find a DNS server via the internet connection setup properties. Providers give their subscribers a public IP address (es) of the primary and backup DNS servers. You can find the current IP address of the configuration of your DNS servers via several methods: • on a home network router configuration screen • the connection properties of TCP / IP screen in the Windows Control Panel (if configured via that method) • from the command ipconfig or similar utility lines
Here Name of Open DNS Server
DNS Open DNS
- 208.67.222.222
- 208.67.220.220
DNS ScrubIt
- 67.138.54.100
- 207.225.209.66
DNS DNSadvantage
- 156.154.70.1
- 156.154.71.1
DNS vnsc-pri.sys.gtei.net
- 4.2.2.1
- 4.2.2.2
- 4.2.2.3
- 4.2.2.4
- 4.2.2.5
- 4.2.2.6
Verizon (Reston, VA, US)
- 151.197.0.38
- 151.197.0.39
- 151.202.0.84
- 151.202.0.85
- 151.202.0.85
- 151.203.0.84
- 151.203.0.85
- 199.45.32.37
- 199.45.32.38
- 199.45.32.40
- 199.45.32.43
GTE (Irving, TX, US)
- 192.76.85.133
- 206.124.64.1
One Connect IP (Albuquerque, NM, US)
- 67.138.54.100
OpenDNS (San Francisco, CA, US)
- 208.67.222.222
- 208.67.220.220
Exetel (Sydney, AU)
- 220.233.167.31
VRx Network Services (New York, NY, US)
- 199.166.31.3
SpeakEasy (Seattle, WA, US)
- 66.93.87.2
- 216.231.41.2
- 216.254.95.2
- 64.81.45.2
- 64.81.111.2
- 64.81.127.2
- 64.81.79.2
- 64.81.159.2
- 66.92.64.2
- 66.92.224.2
- 66.92.159.2
- 64.81.79.2
- 64.81.159.2
- 64.81.127.2
- 64.81.45.2
- 216.27.175.2
Sprintlink (Overland Park, KS, US)
- 199.2.252.10
- 204.97.212.10
- 204.117.214.10
Cisco (San Jose, CA, US)
- 64.102.255.44
- 128.107.241.185
Some of DNS server above can not be used to access a specific FTP and Web sites are blocked by the DNS server.
