Ubuntu resolving on 127.0.0.1 with no dnsmasq

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








up vote
1
down vote

favorite












We are running a Zimbra server on 16.04. today we changed the ip address and location of the server. Most issues have been resolved other than name resolution. The server is listening on 127.0.0.1 but unable to resolve. If we change resolv.conf to 8.8.8.8 we can resolve, However, resolve.conf will get overwritten of course. interfaces is set up correctly with dns-nameservers 8.8.8.8 - not really sure why it is listening on 127.0.0.1?



Trying to understand why resolv.conf is reverting to 127.0.0.1 when dns-nameservers is correctly set? Note, we are not running dnsmasq. Also this is a basic virtual machine install (I dont believe Network Manager is installed)



Appologies if this is a simple question!







share|improve this question





















  • Have you reload the network configuration ? (or just reboot the machine ?)
    – Eraseth
    Jun 11 at 8:35










  • both, but more recently by restarting networking.service
    – skyman
    Jun 11 at 8:51










  • Can you reach the DNS server you try to configure ? (ping)
    – Eraseth
    Jun 11 at 8:58










  • so dns-nameservers is set to 8.8.8.8 - which I can ping yes. I was trying to work out if there was any local DNS server running - but it appears not. netstat shows 127.0.0.1:55 - is this normal?
    – skyman
    Jun 11 at 9:46














up vote
1
down vote

favorite












We are running a Zimbra server on 16.04. today we changed the ip address and location of the server. Most issues have been resolved other than name resolution. The server is listening on 127.0.0.1 but unable to resolve. If we change resolv.conf to 8.8.8.8 we can resolve, However, resolve.conf will get overwritten of course. interfaces is set up correctly with dns-nameservers 8.8.8.8 - not really sure why it is listening on 127.0.0.1?



Trying to understand why resolv.conf is reverting to 127.0.0.1 when dns-nameservers is correctly set? Note, we are not running dnsmasq. Also this is a basic virtual machine install (I dont believe Network Manager is installed)



Appologies if this is a simple question!







share|improve this question





















  • Have you reload the network configuration ? (or just reboot the machine ?)
    – Eraseth
    Jun 11 at 8:35










  • both, but more recently by restarting networking.service
    – skyman
    Jun 11 at 8:51










  • Can you reach the DNS server you try to configure ? (ping)
    – Eraseth
    Jun 11 at 8:58










  • so dns-nameservers is set to 8.8.8.8 - which I can ping yes. I was trying to work out if there was any local DNS server running - but it appears not. netstat shows 127.0.0.1:55 - is this normal?
    – skyman
    Jun 11 at 9:46












up vote
1
down vote

favorite









up vote
1
down vote

favorite











We are running a Zimbra server on 16.04. today we changed the ip address and location of the server. Most issues have been resolved other than name resolution. The server is listening on 127.0.0.1 but unable to resolve. If we change resolv.conf to 8.8.8.8 we can resolve, However, resolve.conf will get overwritten of course. interfaces is set up correctly with dns-nameservers 8.8.8.8 - not really sure why it is listening on 127.0.0.1?



Trying to understand why resolv.conf is reverting to 127.0.0.1 when dns-nameservers is correctly set? Note, we are not running dnsmasq. Also this is a basic virtual machine install (I dont believe Network Manager is installed)



Appologies if this is a simple question!







share|improve this question













We are running a Zimbra server on 16.04. today we changed the ip address and location of the server. Most issues have been resolved other than name resolution. The server is listening on 127.0.0.1 but unable to resolve. If we change resolv.conf to 8.8.8.8 we can resolve, However, resolve.conf will get overwritten of course. interfaces is set up correctly with dns-nameservers 8.8.8.8 - not really sure why it is listening on 127.0.0.1?



Trying to understand why resolv.conf is reverting to 127.0.0.1 when dns-nameservers is correctly set? Note, we are not running dnsmasq. Also this is a basic virtual machine install (I dont believe Network Manager is installed)



Appologies if this is a simple question!









share|improve this question












share|improve this question




share|improve this question








edited Jun 11 at 8:34
























asked Jun 11 at 8:20









skyman

1165




1165











  • Have you reload the network configuration ? (or just reboot the machine ?)
    – Eraseth
    Jun 11 at 8:35










  • both, but more recently by restarting networking.service
    – skyman
    Jun 11 at 8:51










  • Can you reach the DNS server you try to configure ? (ping)
    – Eraseth
    Jun 11 at 8:58










  • so dns-nameservers is set to 8.8.8.8 - which I can ping yes. I was trying to work out if there was any local DNS server running - but it appears not. netstat shows 127.0.0.1:55 - is this normal?
    – skyman
    Jun 11 at 9:46
















  • Have you reload the network configuration ? (or just reboot the machine ?)
    – Eraseth
    Jun 11 at 8:35










  • both, but more recently by restarting networking.service
    – skyman
    Jun 11 at 8:51










  • Can you reach the DNS server you try to configure ? (ping)
    – Eraseth
    Jun 11 at 8:58










  • so dns-nameservers is set to 8.8.8.8 - which I can ping yes. I was trying to work out if there was any local DNS server running - but it appears not. netstat shows 127.0.0.1:55 - is this normal?
    – skyman
    Jun 11 at 9:46















Have you reload the network configuration ? (or just reboot the machine ?)
– Eraseth
Jun 11 at 8:35




Have you reload the network configuration ? (or just reboot the machine ?)
– Eraseth
Jun 11 at 8:35












both, but more recently by restarting networking.service
– skyman
Jun 11 at 8:51




both, but more recently by restarting networking.service
– skyman
Jun 11 at 8:51












Can you reach the DNS server you try to configure ? (ping)
– Eraseth
Jun 11 at 8:58




Can you reach the DNS server you try to configure ? (ping)
– Eraseth
Jun 11 at 8:58












so dns-nameservers is set to 8.8.8.8 - which I can ping yes. I was trying to work out if there was any local DNS server running - but it appears not. netstat shows 127.0.0.1:55 - is this normal?
– skyman
Jun 11 at 9:46




so dns-nameservers is set to 8.8.8.8 - which I can ping yes. I was trying to work out if there was any local DNS server running - but it appears not. netstat shows 127.0.0.1:55 - is this normal?
– skyman
Jun 11 at 9:46










1 Answer
1






active

oldest

votes

















up vote
1
down vote



accepted










The solution was as follows:



Zimbra does run a DNS cache which must be configured to reference an appropriate DNS server.



to check current DNS



zmprov getServer `zmhostname` | grep DNSMasterIP


to remove old DNS



zmprov ms `zmhostname` -zimbraDNSMasterIP 192.168.1.45


to add new DNS



zmprov ms `zmhostname` +zimbraDNSMasterIP 8.8.8.8


Zimbra's dnscache listens on 127.0.0.1 - we had the intenal reference DNS set to an old internal dns server rather than an external one.



dnscache will override resolve.conf in Ubuntu resetting it to 127.0.0.1






share|improve this answer





















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "89"
    ;
    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: true,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    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%2faskubuntu.com%2fquestions%2f1045533%2fubuntu-resolving-on-127-0-0-1-with-no-dnsmasq%23new-answer', 'question_page');

    );

    Post as a guest






























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    1
    down vote



    accepted










    The solution was as follows:



    Zimbra does run a DNS cache which must be configured to reference an appropriate DNS server.



    to check current DNS



    zmprov getServer `zmhostname` | grep DNSMasterIP


    to remove old DNS



    zmprov ms `zmhostname` -zimbraDNSMasterIP 192.168.1.45


    to add new DNS



    zmprov ms `zmhostname` +zimbraDNSMasterIP 8.8.8.8


    Zimbra's dnscache listens on 127.0.0.1 - we had the intenal reference DNS set to an old internal dns server rather than an external one.



    dnscache will override resolve.conf in Ubuntu resetting it to 127.0.0.1






    share|improve this answer

























      up vote
      1
      down vote



      accepted










      The solution was as follows:



      Zimbra does run a DNS cache which must be configured to reference an appropriate DNS server.



      to check current DNS



      zmprov getServer `zmhostname` | grep DNSMasterIP


      to remove old DNS



      zmprov ms `zmhostname` -zimbraDNSMasterIP 192.168.1.45


      to add new DNS



      zmprov ms `zmhostname` +zimbraDNSMasterIP 8.8.8.8


      Zimbra's dnscache listens on 127.0.0.1 - we had the intenal reference DNS set to an old internal dns server rather than an external one.



      dnscache will override resolve.conf in Ubuntu resetting it to 127.0.0.1






      share|improve this answer























        up vote
        1
        down vote



        accepted







        up vote
        1
        down vote



        accepted






        The solution was as follows:



        Zimbra does run a DNS cache which must be configured to reference an appropriate DNS server.



        to check current DNS



        zmprov getServer `zmhostname` | grep DNSMasterIP


        to remove old DNS



        zmprov ms `zmhostname` -zimbraDNSMasterIP 192.168.1.45


        to add new DNS



        zmprov ms `zmhostname` +zimbraDNSMasterIP 8.8.8.8


        Zimbra's dnscache listens on 127.0.0.1 - we had the intenal reference DNS set to an old internal dns server rather than an external one.



        dnscache will override resolve.conf in Ubuntu resetting it to 127.0.0.1






        share|improve this answer













        The solution was as follows:



        Zimbra does run a DNS cache which must be configured to reference an appropriate DNS server.



        to check current DNS



        zmprov getServer `zmhostname` | grep DNSMasterIP


        to remove old DNS



        zmprov ms `zmhostname` -zimbraDNSMasterIP 192.168.1.45


        to add new DNS



        zmprov ms `zmhostname` +zimbraDNSMasterIP 8.8.8.8


        Zimbra's dnscache listens on 127.0.0.1 - we had the intenal reference DNS set to an old internal dns server rather than an external one.



        dnscache will override resolve.conf in Ubuntu resetting it to 127.0.0.1







        share|improve this answer













        share|improve this answer



        share|improve this answer











        answered Jun 12 at 0:37









        skyman

        1165




        1165






















             

            draft saved


            draft discarded


























             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1045533%2fubuntu-resolving-on-127-0-0-1-with-no-dnsmasq%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            pylint3 and pip3 broken

            Missing snmpget and snmpwalk

            How to enroll fingerprints to Ubuntu 17.10 with VFS491