Using Google Public DNS Download this page in PDF

   

Configuring your network settings to use Google Public DNS Testing your new settings Diagnosing resolution problems Switching back to your old DNS settings

Configuring your network settings to use Google Public DNS When you use Google Public DNS, you are changing your DNS "switchboard" operator from your ISP to Google Public DNS. In most cases, the IP addresses used by your ISP's domain name servers are automatically set by your ISP via the Dynamic Host Configuration Protocol (DHCP). To use Google Public DNS, you need to explicitly change the DNS settings in your operating system or device to use the Google Public DNS IP addresses. The procedure for changing your DNS settings varies according to operating system and version (Windows, Mac or Linux) or the device (computer, phone, or router). We give general procedures here that might not apply for your OS or device; please consult your vendor documentation for authoritative information. Note: We recommend that only users who are proficient with configuring operating system settings make these changes. Important: Before you start Before you change your DNS settings to use Google Public DNS, be sure to write down the current server addresses or settings on a piece of paper. It is very important that you keep these numbers for backup purposes, in case you need to revert to them at any time. After changing your settings, if you encounter a problem and cannot connect to the Internet, please call our support numbers for troubleshooting instructions. We also recommend that you download this page and print it, in the event that you encounter a problem and need to refer to these instructions. Google Public DNS telephone support
 

877-590-4367 in the U.S. 770-200-1201 outside the U.S.

Select the connection for which you want to configure Google Public DNS. and click Change adapter settings. . 3.4 The Google Public DNS IPv6 addresses are as follows:   2001:4860:4860::8888 2001:4860:4860::8844 You can use either number as your primary or secondary DNS server. we only give one version as an example. or both. Microsoft Windows DNS settings are specified in the TCP/IP Properties window for the selected network connection. If you need specific instructions for your operating system/version. but do not specify one number as both primary and secondary. Go the Control Panel. to be contacted in a priority order. Many systems allow you to specify multiple DNS servers. and click Properties. For example: o To change the settings for an Ethernet connection. Changing your DNS servers settings Because the instructions differ between different versions/releases of each operating system. please consult your vendor's documentation. then Network and Sharing Center. 2. You can specify both numbers.Google Public DNS IP addresses The Google Public DNS IP addresses (IPv4) are as follows:   8. we provide steps to specify only the Google Public DNS servers as the primary and secondary servers. to ensure that your setup will correctly use Google Public DNS in all cases. Click Network and Internet. you may need administrator/root privileges to change these settings.8 8. Note: Depending on your network setup. Example: Changing DNS server settings on Microsoft Windows 7 1. You can configure Google Public DNS addresses for either IPv4 or IPv6 connections.8.8. In the following instructions.4. You may also find answers on our user group. right-click Local Area Connection.8.

From the Apple menu.5 1. click the icon to make changes. Select the DNS tab. select Internet Protocol Version 4 (TCP/IPv4) or Internet Protocol Version 6 (TCP/IPv6) and then click Properties. 2. write them down for future reference. right-click Wireless Network Connection. If the lock icon in the lower left-hand corner of the window is locked.8. and click Advanced.8 and/or 8. and click Advanced. Repeat the procedure for additional network connections you want to change.8.8. For IPv6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844 9. If there are any DNS server IP addresses listed there. Example: Changing DNS server settings on Mac OS 10. Select the Networking tab. 3. Click Advanced and select the DNS tab. and click Properties. 10. o 4.4. Restart the connection you selected in step 3. Click OK. see Testing your new settings below. and remove them from this window. If you are prompted for an administrator password or confirmation. For example: o To change the settings for an Ethernet connection. Mac OS X DNS settings are specified in the Network window. click System Preferences. 11. 4. Replace those addresses with the IP addresses of the Google DNS servers: o o For IPv4: 8. enter your password. then click Network. If there are any IP addresses listed in the Preferred DNS server or Alternate DNS server. write them down for future reference. select Airport. Select Use the following DNS server addresses. To change the settings for a wireless connection. 7.o To change the settings for a wireless connection. Under This connection uses the following items.4. 5. Select the connection for which you want to configure Google Public DNS. 6. select Built-In Ethernet. Test that your setup is working correctly. . 8. and when prompted to authenticate. type the password or provide confirmation.

8. 7. Repeat the procedure for additional network connections you want to change. 7. 5. Repeat the procedure for additional network connections you want to change.conf.8. For IPv6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844 6. separated by a space: o o For IPv4: 8. type the password or provide confirmation. 8. or add. see Testing your new settings below.8.8. the Google IP addresses at the top of the list: o o For IPv4: 8. select the IPv4 Settings or IPv6 Settings tab. your DNS settings are specified in /etc/resolv. 4. select the Wired tab. Click Apply and OK. enter the Google Public DNS IP addresses. It is usually called eth0. Click Apply to save the change. then select the appropriate wireless network.8. For IPv6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844 6. Click + to replace any listed addresses with.8.8 and/or 8. Test that your setup is working correctly. In the System menu. o 3. If the selected method is Automatic (DHCP). Test that your setup is working correctly.5. then select your network interface in the list.4.4. open the dropdown and select Automatic (DHCP) addresses only instead. Select the connection for which you want to configure Google Public DNS. To change the settings for a wireless connection. and in the window that appears. If you are prompted for a password or confirmation. Click Edit. Example: Changing DNS server settings on a Debian server .4. Example: Changing DNS server settings on Ubuntu 1. DNS settings are configured through Network Manager. If your distribution doesn't use Network Manager.4. 2. In the DNS servers field. select the Wireless tab. then click Network Connections. see Testing your new settings below. Linux In most modern Linux distributions.8. If the method is set to something else. For example: o To change the settings for an Ethernet connection. do not change it. click Preferences.8 and/or 8.

.conf: sudo vi /etc/resolv. 2001:4860:4860::8844.8. 4.4 For IPv6: nameserver 2001:4860:4860::8888 nameserver 2001:4860:4860::8844 4.conf 2.8 nameserver 8. Save and exit.8. Example: Configuring DHCP client sofware on a Debian server 1.8.conf: sudo cp /etc/resolv. 8. if you are using DHCP client software that overwrites the settings in /etc/resolv. 5.conf: sudo vi /etc/dhcp3/dhclient.conf 3. the following lines: For IPv4: nameserver 8.conf. 3. or add.8.4.4. Back up /etc/resolv. write down the IP addresses for future reference. the following line: For IPv4: prepend domain-name-servers 8. Restart any Internet clients you are using. Edit /etc/dhcp3/dhclient. or add.8. If there is a line containing domain-name-servers.auto 2. Additionally. Replace the nameserver lines with.4.conf. you will need to set up the client accordingly by editing the client's configuration file.8. For IPv6: prepend domain-name-servers 2001:4860:4860::8888. Edit /etc/resolv. write down the IP addresses for future reference. Test that your setup is working correctly.conf /etc/resolv. 6. If any nameserver lines appear. Replace that line with.8.1. see Testing your new settings below.

as every mobile device uses a different user interface for configuring DNS server settings. 3. For more information. you will not be able to configure it to use Google Public DNS. If there are IP addresses specified in the fields for the primary and seconday DNS servers. see Testing your new settings below. For more information. Replace those addresses with the Google IP addresses: o o For IPv4: 8. you can configure each of the computers connected to the router. Routers Every router uses a different user interface for configuring DNS server settings. Restart any Internet clients you are using. To change your settings on a router: 1. as described above. write them down for future reference. However. Test that your setup is working correctly. see Testing your new settings below. if you are using such a device.5. 8. 2. 2.8. 6.8. In your browser. To change your settings on a mobile device: 1. 7.4. we provide only a generic procedure below. Save and exit. Instead. Find the screen in which DNS server settings are specified. Go to the screen in which wi-fi settings are specified. 4. Mobile or other devices DNS servers are typically specified under advanced wi-fi settings. For IPv6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844 6. 5. Restart your browser.4. Find the screen in which DNS server settings are specified. enter the IP address to access the router's administration console. please consult your router documentation. Save and exit.8 and/or 8.8. 7. we provide only a generic procedure below. Note: Some ISPs hard-code their DNS servers into the equipment they provide. When prompted. . Test that your setup is working correctly. please consult your mobile provider's documentation. enter the password to access network settings.

type in a hostname. please copy and paste the results of the commands in your email.8 and/or 8. bookmark the page. and want to verify whether the problem is with Google Public DNS. Test that your setup is working correctly. such as http://www.8.mit.4. see Testing your new settings below. go to step 3. 2. contact your ISP or network administrator for assistance. For IPv6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844 5. If these tests do not work. This information is vital to help us to identify the cause of the problem.62. Diagnosing resolution problems If you are encountering problems when resolving particular names.3.8. If both of these tests work. check the steps above to make sure you have configured everything correctly.4. 6. 4.google.eecs. Replace those addresses with the Google IP addresses: o o For IPv4: 8. 3. If you want to report a problem to the Google Public DNS user group. then there is a problem with your network settings. type in a fixed IP address. Testing your new settings To test that the Google DNS resolver is working: 1. You can use http://18. If it resolves correctly. Step 1: Verify that your client can communicate with the Google Public DNS servers IPv4 Open a command prompt. and try accessing the page from the bookmark. everything is working correctly. From your browser.0. then there is a problem with your DNS configuration. and run the following command: On Windows: . write them down for future reference. go to step 2.8.96/ (which points to the website http://www. please try running the following diagnostic procedures.edu/) as the URL*. bookmark the page. If there are IP addresses specified in the fields for the primary and seconday DNS servers. and try accessing the page from the bookmark. From your browser. Roll back the DNS changes you made and run the tests again. If this works correctly. If the tests still do not work. * Google thanks MIT for granting permission to use this URL for the purposes of testing web connectivity.com. If not. Save and exit. If these tests work (but step 1 fails).

8. where hostname is the name that you were having difficulty resolving: On Windows: .8 If the last line of the output does not list 8.8. IPv6 Open a command prompt. If IPv4 works for you. Try configuring Google Public DNS for IPv4 to diagnose whether the problem is due to IPv6 connectivity on your network.8. If the last line of the output does list 2001:4860:4860::8888 as the final hop. or if there are significant timeouts. you may want to revert your IPv6 configuration and use Google Public DNS with IPv4 exclusively.8. and run the following command: On Windows: tracert -d 2001:4860:4860::8888 On Mac OS X: /usr/sbin/traceroute -n -w 2 -q 2 -m 30 2001:4860:4860::8888 On Linux: sudo traceroute -n -w 2 -q 2 -m 30 2001:4860:4860::8888 If the last line of the output does not list 2001:4860:4860::8888 as the final hop. or if there are significant timeouts.8. there may be a network problem preventing you from contacting our servers.8. please include the output of the command in any communication with the Google Public DNS team. Step 2: Verify that Google Public DNS can resolve the selected hostname IPv4 At the command prompt. run the following command.8 as the final hop.8. Otherwise.8.8. continue to step 2.tracert -d 8. Please include the output of the command in any communication with the Google Public DNS team.8 On Mac OS X: /usr/sbin/traceroute -n -w 2 -q 2 -m 30 8. continue to step 2.8 On Linux: sudo traceroute -n -w 2 -q 2 -m 30 8.8.8 as the final hop. If the last line of the output does list 8. there may be a network problem preventing you from contacting our servers.

dig @2001:4860:4860::8888 hostname AAAA If the output shows an answer section with an AAAA record for the hostname. please include the output of the command in any communication with the Google Public DNS team. where hostname is the name that you were having difficulty resolving*. but the host and/or its nameserver are not configured to return IPv6 results. Check your settings to make sure your system is correctly configured to use Google Public DNS. IPv6 Windows At the command prompt. If the output for ipv6. continue to step 3. run the following command. then Google Public DNS is able to resolve the name. Check your settings to make sure your system is correctly configured to use Google Public DNS. If you are still unable to solve the problem. On Mac and Linux At the command prompt. then Google Public DNS is able to resolve the name. nslookup -debug -type=AAAA hostname 2001:4860:4860::8888 If the output shows an answer section with an AAAA record for the hostname.8. or another host for which you are certain IPv6 records exist. you can use the hostname ipv6. If you are still unable to solve the problem. Check your settings to make sure your system is correctly configured to use Google Public DNS.8.8 On Mac and Linux: dig @8. continue to step 3. then Google Public DNS is able to resolve the name.com as a generic test. then Google Public DNS is able to resolve the name.google. please include the output of the command in any communication with the Google Public DNS team. run the following command. If the output shows an answer section with an A (IPv4) record for the hostname. If the output does not show an answer for the hostname.8.google.nslookup -debug hostname 8. does not show an answer.com. . If you are still unable to solve the problem.8 hostname If the output shows an answer section with an A record for the hostname.8. If you want to verify that you are correctly receiving AAAA records. where hostname is the name that you were having difficulty resolving*. please include the output of the command in any communication with the Google Public DNS team.

If it does not. If you want to verify that you are correctly receiving AAAA records. Please see the Google over IPv6 page for more information about whether your system qualifies.2.If the output does not show an AAAA record for the hostname.2 nslookup hostname 208.67.) If you are not able to get a successful result.google. to switch back to your old settings.google. If necessary. This may be a temporary problem on the server's side that will likely resolve itself eventually. in the window in which you specified the Google IP addresses.2. there may be a problem with Google Public DNS.com.1 nslookup hostname 4. use the procedures above to specify the old IP addresses. this may be because the the host and/or its nameserver are not configured to return IPv6 results.2. does not show an answer. and/or delete the Google IP addresses. If you need to manually specify any addresses. If the output for ipv6. you should contact the owner of the server. . Wait some time and try running the tests again. Please include the output of this command and the one from step 2 in any communication with the Google Public DNS team. or another host for which you are certain IPv6 records exist. Switching back to your old DNS settings If you had not previously configured any customized DNS servers. The last two commands test OpenDNS' DNS servers. This will revert your settings to using your ISP's default servers.com as a generic test. run any one of the following commands.222 nslookup hostname 208. this means that there is most likely a problem with the server you are trying to contact.67.220 (The first two commands test Level 3's DNS servers. *Note: Google properties will not return AAAA records for all users. Step 3: Verify that another open resolver can resolve the selected hostname At the command prompt.220. restart your system. you can use the hostname ipv6.222. where hostname is the name that you were having difficulty resolving: nslookup hostname 4. select the option to enable obtaining DNS server addresses automatically.2. continue to step 3. If you do get a successful result.

Code Home .한국어 .Privacy Policy .Site Directory Google Code offered in: English .中文 (繁體) .©2011 Google .Español .Site Terms of Service .Pусский .日本語 .中文(简体) .Português .