Free Public DNS Servers
Scroll down for instructions.
Cable & Wireless:
141.1.1.1
Chaos Computer Club:
213.73.91.35
Christoph Hochstätter:
209.59.210.167
85.214.117.11
Cisco (San Jose, CA, US):
171.70.168.183
171.69.2.133
128.107.241.185
64.102.255.44
192.135.250.69
ClaraNet:
212.82.225.7
212.82.226.212
ClearCloud:
74.118.212.1
74.118.212.2
Comodo (Auto blocking phishing, malware and spyware web sites):
8.26.56.26
8.20.247.20
DNS Advantage:
156.154.70.1
156.154.71.1
DNSReactor:
204.45.18.18
204.45.18.26
DNSResolvers:
64.68.200.200
205.210.42.205
DynDNS:
216.146.35.35
216.146.36.36
easyDNS:
205.210.42.205
64.68.200.200
Exetel (Sydney, AU):
220.233.167.31
FoeBuD e.V.:
85.214.73.63
German Privacy Foundation:
87.118.100.175 (Ports: 53, 110)
94.75.228.29 (Ports: 53, 110, DNSSEC)
87.118.104.203 (Ports: 53, 110,DNSSEC)
62.141.58.13 (Ports: 53, 110, HTTPS-DNS, DNSSEC)
87.118.109.2 (Ports: 53, 110, DNSSEC)
GreenTeam (UK):
81.218.119.11
209.88.198.133
Google:
8.8.8.8
8.8.4.4
GTE (Irving, TX, US):
192.76.85.133
206.124.64.1
Hurricane Electric:
74.82.42.42
2001:470:20::2
JSC Marketing:
216.129.251.13
66.109.128.213
Level 3 Communications :
4.2.2.1
4.2.2.2
4.2.2.3
4.2.2.4
4.2.2.5
4.2.2.6
209.244.0.3
209.244.0.4
Norton:
198.153.192.1
198.153.194.1
Norton ConnectSafe 1 (Auto blocking malware, phishing & scams web sites):
198.153.192.40
198.153.194.40
Norton ConnectSafe 2(Auto blocking malware, phishing, pornographic & scams web sites):
198.153.192.50
198.153.194.50
Norton ConnectSafe 3 (Auto blocking malware, phishing, pornographic, non-family friendly & scams web sites):
198.153.192.60
198.153.194.60
One Connect IP (Albuquerque, NM, US):
67.138.54.100
OpenDNS (San Francisco, CA, US):
58.6.115.42 (Queensland, Australia)
202.83.95.227 (Queensland, Australia)
119.31.230.42 (Victoria, Australia)
217.79.186.148 (Germany)
27.110.120.30 (New Zealand)
89.16.173.11 (United Kingdom)
216.87.84.211 (Colorado, United States)
2001:470:8388:10:0:100:53:20 (Colorado, United States)
69.164.208.50 (New Jersey, United States)
69.164.211.225 (New Jersey, United States)
64.0.55.201 (New York, United States)
66.244.95.20 (Indiana, United States)
2001:470:1f10:c6::2 (Indiana, United States)
72.14.189.120 (Texas, United States)
2001:470:1f0f:48e::2 new (Texas, United States)
69.164.196.21 (Texas, United States)
OpenNIC:
76.74.205.228 (CA)
198.100.146.51 (QC, CA)
198.71.82.42 (IL, US)
192.157.239.23 (FL, US)
202.83.95.227 (au)
119.31.230.42 (au)
178.63.26.173 (de)
217.79.186.148 (de)
27.110.120.30 (nz)
89.16.173.11 (uk)
69.164.208.50 (us)
216.87.84.211(us)
2001:470:8388:10:0:100:53:20 (us) (IPv6)
2001:470:1f10:c6::2 (us) (IPv6)
ORSC:
199.166.24.253
199.166.27.253
199.166.28.10
199.166.29.3
199.166.31.3
195.117.6.25
204.57.55.100
PowerNS:
194.145.226.26
77.220.232.44
Public Root:
199.5.157.131 (Chicago)
208.71.35.137 (Des Moines)
209.97.202.107 (Canada)
80.252.121.2 (UK)
46.244.10.98 (Australia)
46.244.10.116 (Singapore)
46.244.10.5 (The Netherlands)
79.172.201.120 (Hungary)
46.244.10.70 (France)
122.183.133.220 (India)
82.146.40.113 (Russian)
200.37.61.62 (Peru)
128.65.160.37 (Iran)
puntCAT(Spain):
109.69.8.51
2a00:1508:0:4::9
SafeDNS:
195.46.39.39
195.46.39.40
Securly (Auto blocking adult oriented pages and web sites):
184.169.143.224
184.169.161.155
ScrubIT (Auto blocking pornographic and malicious web sites):
67.138.54.100
207.225.209.66
SmartViper:
208.76.50.50
208.76.51.51
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
66.92.159.2
66.93.87.2
Sprintlink (Overland Park, KS, US):
199.2.252.10
204.97.212.10
204.117.214.10
ValiDOM:
78.46.89.147
88.198.75.145
Verizon (Reston, VA, US):
4.2.2.1
4.2.2.2
4.2.2.3
4.2.2.4
4.2.2.5
4.2.2.6
Visizone:
74.50.55.161
74.50.55.162
VRx Network Services (New York, NY, US):
199.166.31.3
How to Change DNS Server Settings on Microsoft Windows
The DNS settings on a computer running the Microsoft Windows operating system (OS) are configured in the TCP/IP properties window for the computer. The following example to change DNS server settings is based on the steps required to change the settings on Microsoft Windows 7 OS. They may differ slightly based on the specific version of Windows installed on the computer.
Step 1 - Select the “Start” menu button and click the “Control Panel” icon.
Step 2 - Select the “Network and Internet,” “Network and Sharing Center,” and “Change Adapter” menu options.
Step 3 - Choose the network connection to configure to use the public DNS server. For an Ethernet connection you would right click the “Local Area Connection” menu button and then choose the “Properties” menu option. For a wireless connection, right click the “Wireless Network Connection” and choose the “Properties menu choice. Then, enter a password if prompted or confirm that you want to modify the setting.
Step 4 - Choose the “Networking” menu tab. Then select the “Internet Protocol Version 4 (TCP/IPv4) or Internet Protocol Version 6 (TCP/IPv6) menu option followed by clicking the “Properties” menu button.
Step 5 - Select the “Advanced’ menu option and then click the “DNS” menu tab. Note any DNS server IP addresses listed on this screen for future reference and clear from the window. Click the “Ok” menu button.
Step 6 - Chose the “Use the Following DNS Server Addresses” menu options. If you see any addresses listed here write them down. Then, enter the public DNS server addresses in the appropriate window. If you intend on using the Google Public DNS server your entries would be:
IPv4: 8.8.8.8 and/or 8.8.4.4.
IPv6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844
Step 7 - Restart the network connection selected earlier for configuration. Then, repeat the steps for any additional network connections that require reconfiguration.
How to Change DNS Server Settings on Mac OS X
On Mac OS X the DNS server settings and set and changed in the “Network” window of the operating system. This example uses the specific instructions required for Mac OS X 10.5 and may slightly vary based on the specific version of the OS installed on your computer.
Step 1 - Select “System Preferences” followed by the “Network” menu options from the “Apple” menu.
Step 2 - If there is a lock icon located in the lower corner of the window preventing step 1 from being completed, then click the icon and enter the administrator password for the computer.
Step 3 - Choose the network connection to configure to use a public DNS server. For an Ethernet connection, choose the “Built-in-Ethernet” menu option followed by the “Advanced” menu choice. For a wireless connection, choose the “Airport” followed by clicking “Advanced.”
Step 4 - Choose the “DNS” menu tab. Then, select the “+” symbol to replace any of the listed addresses. Ensure legacy DNS servers are written down or otherwise recorded in the event you need to use them in the future. To change the DNS server settings to the Google servers enter the following addresses:
For IPv4: 8.8.8.8 and/or 8.8.4.4.
For IPv6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844
Step 5 - Choose the “Apply” and “Ok” menu buttons to finish configuring the DNS server setup for your Mac computer. Repeat the instructions for an additional network connection on the same computer.
How to Change DNS Server Settings on Linux
In the majority of Linux distributions, the DNS settings are configured or set by using the Network Manager. This example uses settings required on Ubuntu and the steps may be different based on the Linux build or version that you have installed on your computer.
Step 1 - From the computer’s “System” menu, choose the “Preferences” and “Network Connections” menu options.
Step 2 - Choose the network connection that you want to change to use a public DNS server. For an Ethernet connection, you would select the “Wired” menu tab and then choose the network interface from the resulting list which is normally called “eh0.” For a wireless connection, choose the “Wireless” menu tab and select the appropriate wireless network.
Step 3 - Choose the “Edit” menu button and then choose the “IPv4” or “IPv6” settings menu tab. If you see that the current method being used is “Automatic (DHCP),” then open the dropdown and choose the “Automatic (DHCP) addresses only” menu option. If set to another option, do not change the selection.
Step 4 - In the DNS servers field, enter the desired public DNS server IP addresses separated by a space. To configure the computer to use the Google public DNS servers enter:
IPv4: 8.8.8.8 and/or 8.8.4.4.
IPv6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844
Step 5 - Choose the “Apply” menu button to save the changes. Some builds of Linux will then as you to enter a password to confirm the changes. Repeat the same procedure for any additional connections that you want to change.
How to Change DNS Server Settings on Mobile Devices
On a mobile device, the DNS server configuration will normally be saved under the advanced wireless or WiFi settings. The following procedure is generic in nature and will likely require slightly different steps based on the brand of the device being changed.
Step 1 - Open the WiFi settings screen or menu. Locate the menu option or screen where DNS settings are listed.
Step 2 - Note any IP addresses listed for the primary and secondary DNS servers in the event you need to change the settings in the future to the original ones.
Step 3 - Change the DNS server addresses with the desired public servers. To change to use the public Google DNS servers, enter the following addresses:
IPv4: 8.8.8.8 and/or 8.8.4.4.
IPv6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844
Sep 4 - Choose the “Save” and “Exit” menu options to complete changing the DNS server settings on your mobile device.
How Do You Test Public DNS Server Changes?
Step 1 - Launch the web browser on the computer or mobile device that has public DNS servers entered.
Step 2 - Enter a well-known website such as www.tech-faq.com or www.google.com.
Step 3 - If the page loads properly, bookmark it in your browser.
Step 4 - Access the page from the bookmark. If the well-known site loads from each test, then the changes to the public DNS server have worked appropriately.
Step 5 - If the webpage fails to load from either test enter a fixed IP address. A well-known one that can be used is: http://18.62.0.96/ which should resolve to MIT. If this works, bookmark the page and try again. If the IP address entry fails, you likely entered the DNS changes incorrectly and need to try again.
Step 6 - If neither of the IP address tests works, then enter the old DNS servers and run the tests again. If they fail, then there is a problem with the computer’s network connection that may require ISP or network administrator assistance. If the computer works normally after reverting to the old DNS settings, then there is likely an issue with the public DNS server that you have tried to use.
How Do You Troubleshoot DNS Server Errors?
In the event you are encountering errors or issues after changing to a public DNS server there are some troubleshooting steps that you can take to verify if the error is with the DNS server. Once you run each of the commands, save the results in a text document so that you can send them to the appropriate help desk or message board that supports the server (if there is one).
Step 1 - Confirm that your computer can establish communications with the public DNS server. On a Windows computer, open the DOS command prompt by selecting the “Start” menu button and entering “CMD” in the search text field.
Step 2 - enter “tracert -d serveraddress” followed by pressing the enter key. ON a MAC OS X computer, open the terminal and enter “/usr/sbin/traceroute -n -w 2 -q 2 -m 30 serveraddress . On Linux, sudo traceroute -n -w 2 -q 2 -m 30 serveraddress.
If you do not see the DNS server IP address as the final hop on the return trace or there are a lot of timeouts, then there may be a network connectivity issue preventing contact with the public DNS server.
Step 3 - Confirm that the public DNS server can resolve the hostname. On Windows, enter the following command at the command prompt:
Nslookup -debug hostname DNSserverAddress
Mac OS X and Linux:
Dig @DNSserverAddress hostname
If you see a section with an A record listed for the hostname on the output, then the DNS server can resolved the name and you should confirm the DNS settings on your computer again. If you do not see an answer for the hostname, then proceed to the next step.
Step 4 - Confirm that another public DNS server can resolve the hostname that you have selected. Enter the following commands at the command prompt on Windows. The servers used are from Level 3 and Open DNS (Last 2).
nslookup hostname 4.2.2.1
nslookup hostname 4.2.2.2
nslookup hostname 208.67.222.222
nslookup hostname 208.67.220.220
If you get a successful result, then there is likely an issue with the first public DNS servers that you tested. If you do not get a successful result, then there is probably an issue with the servers being tested and should be tried again after waiting for a bit.
Step 5 - Change your computer’s DNS settings to the original servers that were being used if you have no success in changing the settings to a public DNS server. Based on your operating system, you may need to manually enter these addresses again and restart the computer or device.