Go to start Control Panel Network Connections Right-click Local Area Connection Properties Double-click internet Protocol type in the following Preferred DNS: 4.2.2.1 Alternative DNS: 4.2.2.2
above are not functioning anymore Here a list of the ones by OpenNIC (which resolve any other Domain, too), including their Country-Code of the Server location: AU 58.6.115.42
AU 58.6.115.43
AU 119.31.230.42
BR 200.252.98.162
DE 217.79.186.148
FR 82.229.244.191
US 216.87.84.211
US 2002:d857:54d2:2:20e:2eff:fe63:d4a9
US 2001:470:1f07:38b::1
US 66.244.95.20
US 2001:470:1f10:c6::2
There are in total 13 main Public-Root Servers.
The prefered DNS server for the site is the server which sends the dns zone updates to all the other servers in the site. The primary DNS zone is created on the server and it has the authority to send changes in zone to other servers
top level
DNS servers
DNS Servers
.
Using reliable DNS servers is crucial to online success, for a regular website owner the most important of them are the name servers which are responsible for the online solution and with a static DNS you can rely on it instead of a random DNS server.
DomainDNSZones
If a DNS server cannot find the answer to the DNS Query in its own database it will first query the forwarders (if there are any configured) and then ask the root server. root servers (by default) are the master DNS servers of the Internet.
In you're using Windows, open a terminal window (Start > Run > "cmd") Then type: "ipconfig /all" The DNS servers will be among the information listed. If you're asking about what a good DNS server to use, go with 8.8.8.8, that's Google's free public DNS server.
There are mail servers, FTP servers, Web servers, DNS servers, DHCP Servers, those are the most common types
DNS records are stored in DNS servers, which are part of a distributed network that manages domain name resolution. These servers can be authoritative, containing the definitive records for a domain, or caching, temporarily storing records retrieved from authoritative servers. When a user queries a domain, the DNS resolver checks its cache first and, if not found, queries the appropriate authoritative DNS server to fetch the records.