IPv4 地址 220.127.116.11 18.104.22.168
- 22.214.171.124 （Resolver1.OpenDNS.com）
- 126.96.36.199 （Resolver2.OpenDNS.com）
- 188.8.131.52 （Resolver3.OpenDNS.com）
- 184.108.40.206 （Resolver4.OpenDNS.com）
- 220.127.116.11 （resolver1-fs.opendns.com）
- 18.104.22.168 （resolver2-fs.opendns.com）
- 2620:0:ccd::2 官网： 点击前往
22.214.171.124 126.96.36.199 官网： 点击前往
188.8.131.52 184.108.40.206 位置：佛罗里达州坦帕市
策略A - 安全 此策略将阻止所有网站托管恶意软件，钓鱼网站和诈骗网站。 220.127.116.11 18.104.22.168
策略B - 安全+色情 除了阻止不安全的网站，这一政策也阻止访问包含色情内容的网站。 22.214.171.124 126.96.36.199
政策Ç - 安全+色情+非家庭友善 这项政策是非常适合有小孩的家庭。阻止不安全的网站和色情网站。 188.8.131.52 184.108.40.206
通过以太网速度在10 Gbps至100 Gbps的相同连接
220.127.116.11 18.104.22.168 官网：点击前往
Comodo Secure DNS
(美国Dynamic Network Services（Dyn）公司是致力于DNS、域名注册、网络流量和品质监测等领域的产品与解决方案提供商)
主用DNS: 22.214.171.124 备用DNS：126.96.36.199 官网： 点击前往
Basic模式（快速）， 首选DNS服务器：188.8.131.52 备用DNS服务器：184.108.40.206
Safe模式（安全）， 首选DNS服务器：220.127.116.11 备用DNS服务器：18.104.22.168，
Family模式（家庭)， 首选DNS服务器：22.214.171.124 备用DNS服务器：126.96.36.199 官方:点击前往
首选DNS服务器：188.8.131.52 备用DNS服务器：184.108.40.206 官网：点击前往(已关）参考
首选DNS服务器：220.127.116.11 备用DNS服务器：18.104.22.168 官网：点击前往
首选DNS服务器：22.214.171.124 备用DNS服务器：126.96.36.199 官网：点击前往
是一个可以帮助你获得更快 App Store 下载
速度的 DNS 服务器
在 London 的主服务器：
188.8.131.52 184.108.40.206 官网：点击前往
DNS 伺服器： 220.127.116.11 18.104.22.168
Providers Primary DNS Secondary DNS Server Location
OpenDNS 22.214.171.124 126.96.36.199 San Antonio, Texas, USA
Level3 188.8.131.52 184.108.40.206 Diamond Bar, California, USA
DNS Advantage 220.127.116.11 18.104.22.168 Sterling, Virginia, USA
Verizon 22.214.171.124 126.96.36.199 Routing to nearest Level3 nodes
SmartViper 188.8.131.52 184.108.40.206 Birminghan, Alabama & Tampa, Florida USA
Google 220.127.116.11 18.104.22.168
DNS.WATCH 22.214.171.124 126.96.36.199
Comodo Secure DNS 188.8.131.52 184.108.40.206
OpenDNS Home 220.127.116.11 18.104.22.168
DNS Advantage 22.214.171.124 126.96.36.199
Norton ConnectSafe 188.8.131.52 184.108.40.206
GreenTeamDNS 220.127.116.11 18.104.22.168
SafeDNS 22.214.171.124 126.96.36.199
OpenNIC 188.8.131.52 184.108.40.206
Dyn 220.127.116.11 18.104.22.168
FreeDNS 22.214.171.124 126.96.36.199
censurfridns.dk 188.8.131.52 184.108.40.206
Hurricane Electric 220.127.116.11
FoeBuD e.V. 18.104.22.168 Deutschland
German Privacy Foundation e.V. 22.214.171.124 Deutschland
German Privacy Foundation e.V. 126.96.36.199 Deutschland
German Privacy Foundation e.V. 188.8.131.52 Deutschland
German Privacy Foundation e.V. 184.108.40.206 Deutschland
Chaos Computer Club Berlin 220.127.116.11 Deutschland
ClaraNet 18.104.22.168 Deutschland
ClaraNet 22.214.171.124 Deutschland
OpenDNS 126.96.36.199 USA
OpenDNS 188.8.131.52 USA
OpenNIC 184.108.40.206 Australien
OpenNIC 220.127.116.11 Australien
OpenNIC 18.104.22.168 Australien
OpenNIC 22.214.171.124 Brasilien
OpenNIC 126.96.36.199 Deutschland
OpenNIC 188.8.131.52 Deutschland
OpenNIC 184.108.40.206 Deutschland
OpenNIC 220.127.116.11 Neuseeland
OpenNIC 18.104.22.168 Frankreich
OpenNIC 22.214.171.124 Tschechien
OpenNIC 126.96.36.199 USA
OpenNIC 188.8.131.52 USA
OpenNIC 184.108.40.206 USA
OpenNIC 220.127.116.11 USA
DNS Advantage 18.104.22.168 USA
DNS Advantage 22.214.171.124 USA
Comodo Secure DNS 126.96.36.199 USA
Comodo Secure DNS 188.8.131.52 USA
PowerNS 184.108.40.206 Deutschland
PowerNS 220.127.116.11 Deutschland
ValiDOM 18.104.22.168 Deutschland
ValiDOM 22.214.171.124 Deutschland
JSC Marketing 126.96.36.199 USA
JSC Marketing 188.8.131.52 USA
Cisco Systems 184.108.40.206 USA
Cisco Systems 220.127.116.11 USA
Cisco Systems 18.104.22.168 USA
Cisco Systems 22.214.171.124 USA
DNSBOX 126.96.36.199 Deutschland
DNSBOX 188.8.131.52 Deutschland
Christoph Hochstätter 184.108.40.206 USA
Christoph Hochstätter 220.127.116.11 Deutschland
privat 18.104.22.168 Deutschland
privat 22.214.171.124 Deutschland
privat (i-root.cesidio.net, cesidio root included) 126.96.36.199 Rußland
privat 188.8.131.52 Deutschland
The Domain Name System (DNS) is a hierarchical distributed naming system for some resource, services, or computers on a private network or the web. It links domain names assigned to all the participating things and various advice. Most conspicuously, it interprets domain names, which people can easily memorize, to the numeric IP addresses required for the goal of apparatus and computer services world-wide. The Domain Name System is a critical part of most Internet services‘ functionality as it’s the primary directory service of the Internet.
The Domain Name System spreads the duty of assigning domain names by designating authorized name servers for every domain name and mapping those names. Authorized name servers are delegated to lead to their domain names that were supported, and could delegate power over sub domains to other name servers. This mechanism supplies distributed and fault tolerant service and was made to prevent the dependence on a principal database that is single.
The Domain Name System additionally defines the technical functionality which will be at its heart. It defines the DNS protocol, a comprehensive specification of data communication exchanges and the data structures used in DNS, within the Internet Protocol Suite. Historically, other directory services preceding DNS are not scalable to big or global directories as they were initially according to text files, conspicuously the HOSTS.TXT resolver. DNS continues to be in extensive use.
The web keeps two principal namespaces, the domain name hierarchy as well as the Internet Protocol (IP) address spaces. The Domain Name System keeps the domain name hierarchy and offers translation services between it as well as the address spaces. Internet name servers and a communication protocol execute the Domain Name System. A DNS name server is a server that stores the DNS records to get a website name; a DNS name server reacts with responses to queries against its database.
The most frequent forms of records saved in the DNS database are those coping with a DNS zone’s ability power (SOA), IP addresses (A and AAAA), SMTP mail exchangers (MX), name servers (NS), pointers for reverse DNS lookups (PTR), and domain name aliases (CNAME). Although not meant to be a general purpose database, DNS can save records for other kinds of data for either automatic machine lookups for things or for human queries like responsible individual (RP) records. To get an entire listing of DNS record types, start to see the set of DNS record types. DNS has additionally seen use in fighting unsolicited e-mail (junk) by employing a realtime blackhole list saved in a DNS database. For general purpose uses or whether for Internet naming, the DNS database is kept in a zone file that was ordered.
An often-used analogy to spell out the Domain Name System is the fact that it functions as the telephone book by interpreting individual-friendly computer hostnames. As an example , the domain name www.example.com translates to the addresses 184.108.40.206 (IPv4) and 2606:2800:220:6d:26bf:1447:1097:aa7 (IPv6). Unlike a phone book, the DNS could be instantly upgraded, enabling the place on the network to alter without changing the end users, who continue to make use of the exact same host name of a service. Users benefit from this when they use significant Uniform Resource Locators (URLs), without needing to understand how the services are really located by the computer and e-mail addresses.
Using a more straightforward, more memorable name in place of the numeric address of a host goes back to the ARPANET age. The Stanford Research Institute (now SRI International) kept a text file named HOSTS.TXT that mapped host names to the numeric addresses of computers on the ARPANET. Host operators got copies of the master file. The rapid growth of the emerging network needed an automated system for keeping the host names and addresses.
The Domain Name System was designed by Paul Mockapetris in 1983 in the University of California, Irvine, and composed the initial execution from UCLA in the request. The Internet Engineering Task Force released the first specifications in RFC 882 and RFC 883 in November 1983, for naming Internet hosts, that have stayed the standard.
In 1984, four UC Berkeley pupils–Douglas Terry, Mark Painter, David Riggle, and Songnian Zhou–wrote the initial Unix name server execution, called the Berkeley Internet Name Domain (BIND) Server. In 1985, Kevin Dunlap of DEC significantly revised the DNS implementation. Mike Karels, Phil Almquist, and Paul Vixie have maintained BIND since then. BIND was ported to the Windows NT platform in the early 1990s. BIND was widely distributed, particularly and is the most commonly used DNS applications online.
In November 1987, RFC 1034 and RFC 1035 superseded the 1983 DNS specifications. Several added Request for Opinions have proposed extensions to the central DNS protocols.
Initially, security concerns are not important design factors for DNS software or some applications for deployment on the Internet that is first, as the network had not been open for involvement from the public. But the growth of the world wide web to the commercial sector altered the conditions for security measures.
Malicious users found and used several susceptibility problems. One problem is DNS cache poisoning, where data is dispersed to caching resolvers under the pretense of being a source server that is important, thus polluting the data store with long expiration times and possibly bogus information (time to live). Later, valid program requests could be redirected to network hosts controlled with malicious purpose.
DNS answers are not signed, leading to many strike possibilities; the Domain Name System Security Extensions (DNSSEC) change DNS to include support for answers that are signed. DNSCurve continues to be suggested instead to DNSSEC. Other extensions, for example TSIG, add support for cryptographic authentication between peers that are trusted and can be used to authorize dynamic update operations or zone transport.
Some domain names can be utilized to attain effects that were spoofing. As an example, paypal.com and paypa1.com are different names, yet users might not be able differentiate them in a graphical user interface according to an individual ’s preferred typeface. In several fonts the numeral 1 as well as the letter l appear even indistinguishable or quite similar. This issue is critical in systems that support internationalized domain names, since many character codes may seem indistinguishable on computer screens that are typical. This susceptibility is sometimes used 
Techniques including forward-confirmed reverse DNS may also be utilized to validate DNS results.
Domain name registration
The privilege to make use of a site name is delegated by domain name registrars which are accredited by the Internet Corporation for Assigned Names and Numbers (ICANN) or other organizations like OpenNIC, which are charged with supervising number systems and the name of the world wide web. As well as ICANN, each top-level domain (TLD) serviced and is kept by an administrative organization, running a registry. There is a registry responsible for keeping the database of names registered within the TLD it manages. The registry releases the advice using the WHOIS protocol a particular service, and receives enrollment information from every domain name registrar authorized to assign names in the accompanying TLD.
ICANN releases the entire list of domain name registrars and TLD registries. Registrant advice related to domain names is kept in a web-based database reachable with the WHOIS service. For most of the more than 290 country code top-level domains (ccTLDs), the domain registries keep the WHOIS (Registrant, name servers, expiration dates, etc.) advice. For example, DENIC, Germany NIC, holds the DE domain name data. Since about 2001, most gTLD (Generic top-level domain) registries have embraced this so called thick registry strategy, i.e. keeping the WHOIS data in essential registries instead of registrar databases.
For NET domain names and COM, there is a thin registry version used. The domain registry (e.g., VeriSign) holds essential WHOIS data (i.e., registrar and name servers, etc.) You can discover the detailed WHOIS (registrant, name servers, expiry dates, etc.) at the registrars.
Some domain name registries, frequently called network information centres (NIC), additionally function to end users as registrars. The leading generic top-level domain registries, for example for the domains COM, NET, ORG, INFORMATION, make use of a registry-registrar model comprising many domain name registrars. In this approach to control, the registry simply handles the domain name database as well as the relationship with all the registrars. The registrants (users) are customers in certain situations through added levels of resellers.