Ubuntu DNS not using DNS from WiFi

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite
1












I had set my router's DNS address to CloudFlare's 1.1.1.1 and 1.0.0.1. When I boot on linux it doesn't show those DNS' only 127.0.0.1. Cloudflare's DNS shows on Android and Windows 10, but not Ubuntu 16.04.







share|improve this question





















  • What are you using to configure the network? NetworkManager, /etc/network/interfaces, or other, and is it static or DHCP?
    – multithr3at3d
    May 3 at 3:53










  • It's DHCP and I didn't configure the network on ubuntu. I'm just wondering why it didn't change to cloudflare on my laptop since I change the DNS for my router.
    – Slightly Higher Average User
    May 3 at 4:18














up vote
0
down vote

favorite
1












I had set my router's DNS address to CloudFlare's 1.1.1.1 and 1.0.0.1. When I boot on linux it doesn't show those DNS' only 127.0.0.1. Cloudflare's DNS shows on Android and Windows 10, but not Ubuntu 16.04.







share|improve this question





















  • What are you using to configure the network? NetworkManager, /etc/network/interfaces, or other, and is it static or DHCP?
    – multithr3at3d
    May 3 at 3:53










  • It's DHCP and I didn't configure the network on ubuntu. I'm just wondering why it didn't change to cloudflare on my laptop since I change the DNS for my router.
    – Slightly Higher Average User
    May 3 at 4:18












up vote
0
down vote

favorite
1









up vote
0
down vote

favorite
1






1





I had set my router's DNS address to CloudFlare's 1.1.1.1 and 1.0.0.1. When I boot on linux it doesn't show those DNS' only 127.0.0.1. Cloudflare's DNS shows on Android and Windows 10, but not Ubuntu 16.04.







share|improve this question













I had set my router's DNS address to CloudFlare's 1.1.1.1 and 1.0.0.1. When I boot on linux it doesn't show those DNS' only 127.0.0.1. Cloudflare's DNS shows on Android and Windows 10, but not Ubuntu 16.04.









share|improve this question












share|improve this question




share|improve this question








edited May 3 at 6:27









Romeo Ninov

4,35811625




4,35811625









asked May 3 at 3:06









Slightly Higher Average User

42




42











  • What are you using to configure the network? NetworkManager, /etc/network/interfaces, or other, and is it static or DHCP?
    – multithr3at3d
    May 3 at 3:53










  • It's DHCP and I didn't configure the network on ubuntu. I'm just wondering why it didn't change to cloudflare on my laptop since I change the DNS for my router.
    – Slightly Higher Average User
    May 3 at 4:18
















  • What are you using to configure the network? NetworkManager, /etc/network/interfaces, or other, and is it static or DHCP?
    – multithr3at3d
    May 3 at 3:53










  • It's DHCP and I didn't configure the network on ubuntu. I'm just wondering why it didn't change to cloudflare on my laptop since I change the DNS for my router.
    – Slightly Higher Average User
    May 3 at 4:18















What are you using to configure the network? NetworkManager, /etc/network/interfaces, or other, and is it static or DHCP?
– multithr3at3d
May 3 at 3:53




What are you using to configure the network? NetworkManager, /etc/network/interfaces, or other, and is it static or DHCP?
– multithr3at3d
May 3 at 3:53












It's DHCP and I didn't configure the network on ubuntu. I'm just wondering why it didn't change to cloudflare on my laptop since I change the DNS for my router.
– Slightly Higher Average User
May 3 at 4:18




It's DHCP and I didn't configure the network on ubuntu. I'm just wondering why it didn't change to cloudflare on my laptop since I change the DNS for my router.
– Slightly Higher Average User
May 3 at 4:18










2 Answers
2






active

oldest

votes

















up vote
2
down vote













Ubuntu may have pre-installed caching DNS resolver like dnsmasq or systemd-resolver .you can check if there any local DNS resolver listening to the port 53 using below command



netstat -plntu


this will show all the programs listening on all the ports TCP and UDP. if there is any then you have to stop that service or configure 1.1.1.1 as upstream DNS of your caching DNS server






share|improve this answer





















  • lsof -i UDP:53 (or lsof -i UDP:domain) is a bit more concise ...
    – 0xC0000022L
    May 3 at 9:52











  • OK, I disabled dnsmasq. And did cat /etc/reolv.dnsmasq. it now shows cloudflares DNS addresses. Am I good? Also is it OK if I uninstall dnsmasq?
    – Slightly Higher Average User
    May 3 at 10:47











  • You can simply disable the dnsmasq if you want. And check the the file /etc/resolv.conf too. /etc/resolv.dnsmasq is only for dnsmasq itself
    – charith
    May 4 at 2:57


















up vote
0
down vote













If /etc/resolv.conf has nameserver set to 127.0.0.1, that probably means you have a local caching DNS resolver or even a local name server installed.



Typically, the DHCP-specified name servers would then be used as targets for DNS query forwarding in cases where the local cache/server does not have the answer. You might find them in /etc/resolv.dnsmasq, /run/named/named.forwarders or similar configuration file that is specific to the cache/server.



Basically, the majority of programs will read /etc/resolv.conf. It points the programs to use the local cache/server, which will have its own DHCP-managed configuration file. The local cache/server will then use the servers specified by DHCP as the upstream DNS source.






share|improve this answer





















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );








     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f441439%2fubuntu-dns-not-using-dns-from-wifi%23new-answer', 'question_page');

    );

    Post as a guest






























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    2
    down vote













    Ubuntu may have pre-installed caching DNS resolver like dnsmasq or systemd-resolver .you can check if there any local DNS resolver listening to the port 53 using below command



    netstat -plntu


    this will show all the programs listening on all the ports TCP and UDP. if there is any then you have to stop that service or configure 1.1.1.1 as upstream DNS of your caching DNS server






    share|improve this answer





















    • lsof -i UDP:53 (or lsof -i UDP:domain) is a bit more concise ...
      – 0xC0000022L
      May 3 at 9:52











    • OK, I disabled dnsmasq. And did cat /etc/reolv.dnsmasq. it now shows cloudflares DNS addresses. Am I good? Also is it OK if I uninstall dnsmasq?
      – Slightly Higher Average User
      May 3 at 10:47











    • You can simply disable the dnsmasq if you want. And check the the file /etc/resolv.conf too. /etc/resolv.dnsmasq is only for dnsmasq itself
      – charith
      May 4 at 2:57















    up vote
    2
    down vote













    Ubuntu may have pre-installed caching DNS resolver like dnsmasq or systemd-resolver .you can check if there any local DNS resolver listening to the port 53 using below command



    netstat -plntu


    this will show all the programs listening on all the ports TCP and UDP. if there is any then you have to stop that service or configure 1.1.1.1 as upstream DNS of your caching DNS server






    share|improve this answer





















    • lsof -i UDP:53 (or lsof -i UDP:domain) is a bit more concise ...
      – 0xC0000022L
      May 3 at 9:52











    • OK, I disabled dnsmasq. And did cat /etc/reolv.dnsmasq. it now shows cloudflares DNS addresses. Am I good? Also is it OK if I uninstall dnsmasq?
      – Slightly Higher Average User
      May 3 at 10:47











    • You can simply disable the dnsmasq if you want. And check the the file /etc/resolv.conf too. /etc/resolv.dnsmasq is only for dnsmasq itself
      – charith
      May 4 at 2:57













    up vote
    2
    down vote










    up vote
    2
    down vote









    Ubuntu may have pre-installed caching DNS resolver like dnsmasq or systemd-resolver .you can check if there any local DNS resolver listening to the port 53 using below command



    netstat -plntu


    this will show all the programs listening on all the ports TCP and UDP. if there is any then you have to stop that service or configure 1.1.1.1 as upstream DNS of your caching DNS server






    share|improve this answer













    Ubuntu may have pre-installed caching DNS resolver like dnsmasq or systemd-resolver .you can check if there any local DNS resolver listening to the port 53 using below command



    netstat -plntu


    this will show all the programs listening on all the ports TCP and UDP. if there is any then you have to stop that service or configure 1.1.1.1 as upstream DNS of your caching DNS server







    share|improve this answer













    share|improve this answer



    share|improve this answer











    answered May 3 at 5:03









    charith

    14910




    14910











    • lsof -i UDP:53 (or lsof -i UDP:domain) is a bit more concise ...
      – 0xC0000022L
      May 3 at 9:52











    • OK, I disabled dnsmasq. And did cat /etc/reolv.dnsmasq. it now shows cloudflares DNS addresses. Am I good? Also is it OK if I uninstall dnsmasq?
      – Slightly Higher Average User
      May 3 at 10:47











    • You can simply disable the dnsmasq if you want. And check the the file /etc/resolv.conf too. /etc/resolv.dnsmasq is only for dnsmasq itself
      – charith
      May 4 at 2:57

















    • lsof -i UDP:53 (or lsof -i UDP:domain) is a bit more concise ...
      – 0xC0000022L
      May 3 at 9:52











    • OK, I disabled dnsmasq. And did cat /etc/reolv.dnsmasq. it now shows cloudflares DNS addresses. Am I good? Also is it OK if I uninstall dnsmasq?
      – Slightly Higher Average User
      May 3 at 10:47











    • You can simply disable the dnsmasq if you want. And check the the file /etc/resolv.conf too. /etc/resolv.dnsmasq is only for dnsmasq itself
      – charith
      May 4 at 2:57
















    lsof -i UDP:53 (or lsof -i UDP:domain) is a bit more concise ...
    – 0xC0000022L
    May 3 at 9:52





    lsof -i UDP:53 (or lsof -i UDP:domain) is a bit more concise ...
    – 0xC0000022L
    May 3 at 9:52













    OK, I disabled dnsmasq. And did cat /etc/reolv.dnsmasq. it now shows cloudflares DNS addresses. Am I good? Also is it OK if I uninstall dnsmasq?
    – Slightly Higher Average User
    May 3 at 10:47





    OK, I disabled dnsmasq. And did cat /etc/reolv.dnsmasq. it now shows cloudflares DNS addresses. Am I good? Also is it OK if I uninstall dnsmasq?
    – Slightly Higher Average User
    May 3 at 10:47













    You can simply disable the dnsmasq if you want. And check the the file /etc/resolv.conf too. /etc/resolv.dnsmasq is only for dnsmasq itself
    – charith
    May 4 at 2:57





    You can simply disable the dnsmasq if you want. And check the the file /etc/resolv.conf too. /etc/resolv.dnsmasq is only for dnsmasq itself
    – charith
    May 4 at 2:57













    up vote
    0
    down vote













    If /etc/resolv.conf has nameserver set to 127.0.0.1, that probably means you have a local caching DNS resolver or even a local name server installed.



    Typically, the DHCP-specified name servers would then be used as targets for DNS query forwarding in cases where the local cache/server does not have the answer. You might find them in /etc/resolv.dnsmasq, /run/named/named.forwarders or similar configuration file that is specific to the cache/server.



    Basically, the majority of programs will read /etc/resolv.conf. It points the programs to use the local cache/server, which will have its own DHCP-managed configuration file. The local cache/server will then use the servers specified by DHCP as the upstream DNS source.






    share|improve this answer

























      up vote
      0
      down vote













      If /etc/resolv.conf has nameserver set to 127.0.0.1, that probably means you have a local caching DNS resolver or even a local name server installed.



      Typically, the DHCP-specified name servers would then be used as targets for DNS query forwarding in cases where the local cache/server does not have the answer. You might find them in /etc/resolv.dnsmasq, /run/named/named.forwarders or similar configuration file that is specific to the cache/server.



      Basically, the majority of programs will read /etc/resolv.conf. It points the programs to use the local cache/server, which will have its own DHCP-managed configuration file. The local cache/server will then use the servers specified by DHCP as the upstream DNS source.






      share|improve this answer























        up vote
        0
        down vote










        up vote
        0
        down vote









        If /etc/resolv.conf has nameserver set to 127.0.0.1, that probably means you have a local caching DNS resolver or even a local name server installed.



        Typically, the DHCP-specified name servers would then be used as targets for DNS query forwarding in cases where the local cache/server does not have the answer. You might find them in /etc/resolv.dnsmasq, /run/named/named.forwarders or similar configuration file that is specific to the cache/server.



        Basically, the majority of programs will read /etc/resolv.conf. It points the programs to use the local cache/server, which will have its own DHCP-managed configuration file. The local cache/server will then use the servers specified by DHCP as the upstream DNS source.






        share|improve this answer













        If /etc/resolv.conf has nameserver set to 127.0.0.1, that probably means you have a local caching DNS resolver or even a local name server installed.



        Typically, the DHCP-specified name servers would then be used as targets for DNS query forwarding in cases where the local cache/server does not have the answer. You might find them in /etc/resolv.dnsmasq, /run/named/named.forwarders or similar configuration file that is specific to the cache/server.



        Basically, the majority of programs will read /etc/resolv.conf. It points the programs to use the local cache/server, which will have its own DHCP-managed configuration file. The local cache/server will then use the servers specified by DHCP as the upstream DNS source.







        share|improve this answer













        share|improve this answer



        share|improve this answer











        answered May 3 at 9:37









        telcoM

        10.2k11032




        10.2k11032






















             

            draft saved


            draft discarded


























             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f441439%2fubuntu-dns-not-using-dns-from-wifi%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?