I want my Raspberry Pi to use OpenDNS to resolve domain names. How can I modify this setting?
If you are using Debian on Raspberry Pi, then you need to edit
then add the server IP of the openDNS
nameserver 22.214.171.124 nameserver 126.96.36.199
Btw, if you have any concern about speed of the DNS you may want to take a look at this post
I did this, but it's still not using OpenDNS. Jul 10, 2013 at 5:53
4you restarted your board and are using Debian-server, right? If it is the case, please try to add
nameserver 188.8.131.52``andnameserver 184.108.40.206` to
/etc/network/interfacesthen restart your board or do
/etc/init.d/networking restart. If it is still not working, please paste output of
dig google.com– AngsJul 10, 2013 at 6:07
Should the IPs be in both
/etc/network/interfaces? Jul 10, 2013 at 15:36
1The /etc/resolv.conf entry is created from the /etc/network/interfaces config. Note: this works only if you're using static network configuration. If you're using dynamic settings, then you'll need to change the settings provided by the DHCP server.– joatJul 13, 2013 at 13:58
I just wanted to mention that today out of the blue, my Pi3 device couldn't see mirrordetector.raspbian.org. I added the OpenDNS addresses and it works fine. (I had Google's in there...) Jan 14, 2017 at 21:33
I've found that in the latest version of Raspbian (stretch I think?) you now need to edit the last line of
/etc/dhcpcd.conf. There should be a line that starts with
static domain_name_servers= - there you can customise it with a list of space-separated DNS servers, like this:
static domain_name_servers=220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199
DNS Servers Featured: Cloudflare, OpenDNS, and Google
Edit: As @DavidOliver points out, you may need to restart dhcpcd too:
sudo systemctl restart dhcpcd.service.
4This was the only solution that worked for me. I am using raspbian for the raspberry pi– Tono NamMay 24, 2018 at 15:37
1This one was the one that worked for me on Raspbian - From the other answers in this question, edits directory to resolv.conf got overwritten on reboot and the network/interfaces edits were ignored– dlrustOct 29, 2018 at 23:24
1This should be the correct answer for latest (Raspbian Stretch or Debian Stretch), the accepted answer in 2013 and the higher vote so far of modifying
etc/resolv.confare simply no longer correct.– hcheungApr 3, 2019 at 6:06
2Seemed like a restart of the service was necessary:
sudo systemctl restart dhcpcd.serviceAug 7, 2019 at 21:47
1@TomasZubiri It's actually changed quite a bit over the years. The method Described in my answer is most up-to-date version. Answers that suggest to edit
/etc/resolv.confare outdated because that file is now automatically populated with the current DNS resolution settings, and is auto-updated by NetworkManager/systemd/whatever. Mar 16, 2020 at 15:24
/etc/resolv.conf since that file is generated automatically. Instead edit
/etc/network/interfaces and add the following to the end:
dns-nameservers 188.8.131.52 184.108.40.206
5resolv.conf is just overwritten by the resolvconf tool. If this tool is not installed the first answer will work. But your solution will work anyway, that's why it should be marked as the right solution.– BenDec 7, 2016 at 18:18
this worked for me on raspian stretch lite, thanks! Sep 13, 2017 at 1:28
didn't work. startbeamrainbowlabs' solution worked!– lodeAug 13, 2019 at 22:16
I have found the answer from another website and this is the best. I used the very last part of the article as Raspbian comes with dchpcd already installed and i still want an automatic ip address not a static ip address. Running from a Raspberry Pi3 multiboot [berryboot] with Raspbian - Pixel type
sudo nano /etc/resolv.conf.head
in your terminal. You will have a blank slate to work with. Next copy and paste the following code:
#OpenDns Servers nameserver 220.127.116.11 nameserver 18.104.22.168
click on cntrl + x to exit out and select y for the following options to save. restart your Raspberry Pi with
To make sure you are using OpenDNS go to the following website: OpenDns welcome page
Could you add a link to the original forum source you found this answer on? Apr 18, 2017 at 19:36
I have found the exact link [old article from 2013 but works!] I have updated my answer to reflect the link Apr 18, 2017 at 20:07
Sweet. Context almost always makes a question better. Apr 18, 2017 at 20:11
I hope this has helped you. By the way the bootloader i use for my Raspberry PI3 is berryboot [berryterminal.com/doku.php/berryboot] and i love it! I have Raspbian-Pixel, Kali Linux2.0, OSMC, and RetroPie v3.6 running on a 16GB sd card without having to change sd cards. You can get the images for berryboot here: [berryboot.alexgoldcheidt.com/images/] In fact I'm using Raspbian and chromium to answer you. Apr 18, 2017 at 20:19
This worked for me. I really don't understand why setting up networks is becoming more and more complex and intransparent over time.... THanks for your help!– TaratorMay 4, 2017 at 6:17
The openDNS servers worked for me thanks. During a Udemy learning session I had run into a problem after ditching my wifi sharing arrangement with my Mac, and setting up ethernet hub with the PI on a different home network. The problem with my previous IP sharing arrangement with WiFi.
When I originally setup the PI with the sharing arrangement the text Inside the resolve file was:
which was entered automatically by the minibian OS, NOT ME!
This IP became the default DNS server, with the MacMini seamlessly providing the real DNS in the background.
SO NEED TO EDIT(vim) WITH
nameserver 22.214.171.124 nameserver 126.96.36.199
Then I could ping google.com Thank goodness for forums!
1What does this do and how will it help? Read over "Why do I need 50 reputation to comment" to ensure you understand how you can start commenting. Sep 4, 2017 at 2:27
The instructions here are incomplete. Which file needs editing? Where is it located? Are there any other steps one must complete before your solution solves the issue, and how can one verify the issue is solved? Feb 4, 2021 at 15:51
Add this line into file /etc/dhcp/dhclient.conf:
option domain-name-servers 192.168.1.8, 188.8.131.52, 184.108.40.206
Then it will work.
4The first IP address is a random private address. The other two are the IP addresses of Google servers - not OpenDNS. Sep 1, 2015 at 9:39
/etc/resolv.confisn't really the right way going about this anymore: You need to edit
/etc/dhcpcd.confinstead. See my answer below.