Samba Internal DNS - Systemd resolve safe to disable?












0















So I had a Ubuntu 16.04 instance running a samba ad dc, I upgraded to 18.04 and when starting samba I was getting the error;




[2018/12/27 11:09:56.483755, 0]
../source4/dsdb/dns/dns_update.c:290(dnsupdate_nameupdate_done)

../source4/dsdb/dns/dns_update.c:290: Failed DNS update - with error
code 110




After some digging and running sudo lsof -i :53 I could see



systemd-r  767 systemd-resolve   12u  IPv4  18656      0t0  UDP 127.0.0.53:domain 
systemd-r 767 systemd-resolve 13u IPv4 18657 0t0 TCP 127.0.0.53:domain (LISTEN)
samba 1594 root 36u IPv6 23058 0t0 TCP *:domain (LISTEN)
samba 1594 root 38u IPv6 23059 0t0 UDP *:domain


Which lead me to disable systemd-resolve using the instructions here, this has fixed all my problems within the network (other domain machines not being able to apt-get update etc) but im worndering is disabling systemd-resolve safe ?



Edit



This is a VM running on vsphere 6.0 its a bridged networked. Netplan folder is empty after the upgrade (which Ive just remembered should have to be set) the old network details /etc/network/interfaces is set to;



source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto ens160
iface ens160 inet static
address 192.168.2.23
netmask 255.255.255.0
gateway 192.168.2.254

dns-nameservers 192.168.2.23
dns-search MYDOMAINNAME.co.uk


I can manually set the resolv.conf (after removing the sym link) to the following and it works



nameserver 192.168.2.23
nameserver 127.0.0.53
search MYDOMAIN.co.uk
DNSStubListener=no









share|improve this question





























    0















    So I had a Ubuntu 16.04 instance running a samba ad dc, I upgraded to 18.04 and when starting samba I was getting the error;




    [2018/12/27 11:09:56.483755, 0]
    ../source4/dsdb/dns/dns_update.c:290(dnsupdate_nameupdate_done)

    ../source4/dsdb/dns/dns_update.c:290: Failed DNS update - with error
    code 110




    After some digging and running sudo lsof -i :53 I could see



    systemd-r  767 systemd-resolve   12u  IPv4  18656      0t0  UDP 127.0.0.53:domain 
    systemd-r 767 systemd-resolve 13u IPv4 18657 0t0 TCP 127.0.0.53:domain (LISTEN)
    samba 1594 root 36u IPv6 23058 0t0 TCP *:domain (LISTEN)
    samba 1594 root 38u IPv6 23059 0t0 UDP *:domain


    Which lead me to disable systemd-resolve using the instructions here, this has fixed all my problems within the network (other domain machines not being able to apt-get update etc) but im worndering is disabling systemd-resolve safe ?



    Edit



    This is a VM running on vsphere 6.0 its a bridged networked. Netplan folder is empty after the upgrade (which Ive just remembered should have to be set) the old network details /etc/network/interfaces is set to;



    source /etc/network/interfaces.d/*

    # The loopback network interface
    auto lo
    iface lo inet loopback

    # The primary network interface
    auto ens160
    iface ens160 inet static
    address 192.168.2.23
    netmask 255.255.255.0
    gateway 192.168.2.254

    dns-nameservers 192.168.2.23
    dns-search MYDOMAINNAME.co.uk


    I can manually set the resolv.conf (after removing the sym link) to the following and it works



    nameserver 192.168.2.23
    nameserver 127.0.0.53
    search MYDOMAIN.co.uk
    DNSStubListener=no









    share|improve this question



























      0












      0








      0








      So I had a Ubuntu 16.04 instance running a samba ad dc, I upgraded to 18.04 and when starting samba I was getting the error;




      [2018/12/27 11:09:56.483755, 0]
      ../source4/dsdb/dns/dns_update.c:290(dnsupdate_nameupdate_done)

      ../source4/dsdb/dns/dns_update.c:290: Failed DNS update - with error
      code 110




      After some digging and running sudo lsof -i :53 I could see



      systemd-r  767 systemd-resolve   12u  IPv4  18656      0t0  UDP 127.0.0.53:domain 
      systemd-r 767 systemd-resolve 13u IPv4 18657 0t0 TCP 127.0.0.53:domain (LISTEN)
      samba 1594 root 36u IPv6 23058 0t0 TCP *:domain (LISTEN)
      samba 1594 root 38u IPv6 23059 0t0 UDP *:domain


      Which lead me to disable systemd-resolve using the instructions here, this has fixed all my problems within the network (other domain machines not being able to apt-get update etc) but im worndering is disabling systemd-resolve safe ?



      Edit



      This is a VM running on vsphere 6.0 its a bridged networked. Netplan folder is empty after the upgrade (which Ive just remembered should have to be set) the old network details /etc/network/interfaces is set to;



      source /etc/network/interfaces.d/*

      # The loopback network interface
      auto lo
      iface lo inet loopback

      # The primary network interface
      auto ens160
      iface ens160 inet static
      address 192.168.2.23
      netmask 255.255.255.0
      gateway 192.168.2.254

      dns-nameservers 192.168.2.23
      dns-search MYDOMAINNAME.co.uk


      I can manually set the resolv.conf (after removing the sym link) to the following and it works



      nameserver 192.168.2.23
      nameserver 127.0.0.53
      search MYDOMAIN.co.uk
      DNSStubListener=no









      share|improve this question
















      So I had a Ubuntu 16.04 instance running a samba ad dc, I upgraded to 18.04 and when starting samba I was getting the error;




      [2018/12/27 11:09:56.483755, 0]
      ../source4/dsdb/dns/dns_update.c:290(dnsupdate_nameupdate_done)

      ../source4/dsdb/dns/dns_update.c:290: Failed DNS update - with error
      code 110




      After some digging and running sudo lsof -i :53 I could see



      systemd-r  767 systemd-resolve   12u  IPv4  18656      0t0  UDP 127.0.0.53:domain 
      systemd-r 767 systemd-resolve 13u IPv4 18657 0t0 TCP 127.0.0.53:domain (LISTEN)
      samba 1594 root 36u IPv6 23058 0t0 TCP *:domain (LISTEN)
      samba 1594 root 38u IPv6 23059 0t0 UDP *:domain


      Which lead me to disable systemd-resolve using the instructions here, this has fixed all my problems within the network (other domain machines not being able to apt-get update etc) but im worndering is disabling systemd-resolve safe ?



      Edit



      This is a VM running on vsphere 6.0 its a bridged networked. Netplan folder is empty after the upgrade (which Ive just remembered should have to be set) the old network details /etc/network/interfaces is set to;



      source /etc/network/interfaces.d/*

      # The loopback network interface
      auto lo
      iface lo inet loopback

      # The primary network interface
      auto ens160
      iface ens160 inet static
      address 192.168.2.23
      netmask 255.255.255.0
      gateway 192.168.2.254

      dns-nameservers 192.168.2.23
      dns-search MYDOMAINNAME.co.uk


      I can manually set the resolv.conf (after removing the sym link) to the following and it works



      nameserver 192.168.2.23
      nameserver 127.0.0.53
      search MYDOMAIN.co.uk
      DNSStubListener=no






      16.04 networking 18.04 samba dns






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 27 '18 at 14:12







      Dan

















      asked Dec 27 '18 at 11:27









      DanDan

      516316




      516316






















          1 Answer
          1






          active

          oldest

          votes


















          2














          Re-enable systemd-resolve.



          Two possibilities...




          1. Regarding dnsmasq and systemd-resolved...


          Do a ps auxc | grep -i dns and ps auxc | grep -i resolv and look for dnsmasq and systemd-resolved, and if both are running, you need to disable the DNS part of systemd-resolved by editing /etc/systemd/resolved.conf and...



          change:



          #DNSStubListener=yes


          to:



          DNSStubListener=no


          then restart systemd-resolve and dnsmasq, or reboot.





          1. you MAY need to reset the symlink that is /etc/resolv.conf (if dnsmasq is not running)...


          sudo mv /etc/resolv.conf /etc/resolv.conf.OLD # save the old symlink



          sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf # create new symlink



          Update #1:



          Many details of this installation came forward in the comments, and we still don't have a final working solution. Here are some points to recognize...





          DNSStubListener=no does not belong in /etc/resolv.conf. (/etc/resolv.conf should not (normally) be edited directly). It's an edit to /etc/systemd/resolved.conf. DNS= can also be edited there to add DNS server addresses.





          /etc/resolv.conf should be a symlink, linked to one of two possible locations in /run.



          NEW -> /run/systemd/resolve/resolv.conf
          OLD -> ../run/resolvconf/resolv.conf


          and should contain either 127.0.0.53 (or 127.0.0.1 if dnsmasq was running), or DNS nameserver addresses, or your router's address (ex: 192.168.1.1)





          If you're going to use NetworkManager instead of netplan, then /etc/netplan should contain at least one .yaml file containing...



          network:
          version: 2
          renderer: NetworkManager


          followed by...



          sudo netplan --debug generate # generate config files



          sudo netplan apply # apply configuration





          If you're using NetworkManager, then /etc/NetworkManager/NetworkManager.conf should exist... and should look something like...



          [main]
          plugins=ifupdown,keyfile

          [ifupdown]
          managed=false

          [device]
          wifi.scan-rand-mac-address=no




          If dnsmasq AND systemd-resolve are running, then you should do #1 in my answer.



          If dnsmasq is not running, and systemd-resolve is running, then you should do #2 in my answer.









          share|improve this answer


























          • When i run ps auxc | grep -i dns there is no output (pressumeably because I have disabled systemd-resolve, I will try this a minute when a machine has finished its upgrade

            – Dan
            Dec 27 '18 at 12:14











          • That command is looking for dnsmasq. You must not be running it. Re-enable systemd-resolve, and then cat /etc/resolv.conf and you'll probably see 127.0.0.53 indicating that systemd-resolve is managing /etc/resolv.conf. Try item #2 in my answer then.

            – heynnema
            Dec 27 '18 at 12:40













          • /run/systemd/resolve/ doesn't exist but i restored the original resolv.conf adding the line DNSStubListener=no and this appears to have fixed the issue

            – Dan
            Dec 27 '18 at 12:46











          • @Dan That should be /run/systemd/resolve/resolv.conf, It will only be there if systemd-resolve is running. Great news! Please remember to accept my answer. Thanks!

            – heynnema
            Dec 27 '18 at 12:53













          • Just rebooted and tried again, thanks for the help!

            – Dan
            Dec 27 '18 at 12:59











          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',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          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%2f1104863%2fsamba-internal-dns-systemd-resolve-safe-to-disable%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          2














          Re-enable systemd-resolve.



          Two possibilities...




          1. Regarding dnsmasq and systemd-resolved...


          Do a ps auxc | grep -i dns and ps auxc | grep -i resolv and look for dnsmasq and systemd-resolved, and if both are running, you need to disable the DNS part of systemd-resolved by editing /etc/systemd/resolved.conf and...



          change:



          #DNSStubListener=yes


          to:



          DNSStubListener=no


          then restart systemd-resolve and dnsmasq, or reboot.





          1. you MAY need to reset the symlink that is /etc/resolv.conf (if dnsmasq is not running)...


          sudo mv /etc/resolv.conf /etc/resolv.conf.OLD # save the old symlink



          sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf # create new symlink



          Update #1:



          Many details of this installation came forward in the comments, and we still don't have a final working solution. Here are some points to recognize...





          DNSStubListener=no does not belong in /etc/resolv.conf. (/etc/resolv.conf should not (normally) be edited directly). It's an edit to /etc/systemd/resolved.conf. DNS= can also be edited there to add DNS server addresses.





          /etc/resolv.conf should be a symlink, linked to one of two possible locations in /run.



          NEW -> /run/systemd/resolve/resolv.conf
          OLD -> ../run/resolvconf/resolv.conf


          and should contain either 127.0.0.53 (or 127.0.0.1 if dnsmasq was running), or DNS nameserver addresses, or your router's address (ex: 192.168.1.1)





          If you're going to use NetworkManager instead of netplan, then /etc/netplan should contain at least one .yaml file containing...



          network:
          version: 2
          renderer: NetworkManager


          followed by...



          sudo netplan --debug generate # generate config files



          sudo netplan apply # apply configuration





          If you're using NetworkManager, then /etc/NetworkManager/NetworkManager.conf should exist... and should look something like...



          [main]
          plugins=ifupdown,keyfile

          [ifupdown]
          managed=false

          [device]
          wifi.scan-rand-mac-address=no




          If dnsmasq AND systemd-resolve are running, then you should do #1 in my answer.



          If dnsmasq is not running, and systemd-resolve is running, then you should do #2 in my answer.









          share|improve this answer


























          • When i run ps auxc | grep -i dns there is no output (pressumeably because I have disabled systemd-resolve, I will try this a minute when a machine has finished its upgrade

            – Dan
            Dec 27 '18 at 12:14











          • That command is looking for dnsmasq. You must not be running it. Re-enable systemd-resolve, and then cat /etc/resolv.conf and you'll probably see 127.0.0.53 indicating that systemd-resolve is managing /etc/resolv.conf. Try item #2 in my answer then.

            – heynnema
            Dec 27 '18 at 12:40













          • /run/systemd/resolve/ doesn't exist but i restored the original resolv.conf adding the line DNSStubListener=no and this appears to have fixed the issue

            – Dan
            Dec 27 '18 at 12:46











          • @Dan That should be /run/systemd/resolve/resolv.conf, It will only be there if systemd-resolve is running. Great news! Please remember to accept my answer. Thanks!

            – heynnema
            Dec 27 '18 at 12:53













          • Just rebooted and tried again, thanks for the help!

            – Dan
            Dec 27 '18 at 12:59
















          2














          Re-enable systemd-resolve.



          Two possibilities...




          1. Regarding dnsmasq and systemd-resolved...


          Do a ps auxc | grep -i dns and ps auxc | grep -i resolv and look for dnsmasq and systemd-resolved, and if both are running, you need to disable the DNS part of systemd-resolved by editing /etc/systemd/resolved.conf and...



          change:



          #DNSStubListener=yes


          to:



          DNSStubListener=no


          then restart systemd-resolve and dnsmasq, or reboot.





          1. you MAY need to reset the symlink that is /etc/resolv.conf (if dnsmasq is not running)...


          sudo mv /etc/resolv.conf /etc/resolv.conf.OLD # save the old symlink



          sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf # create new symlink



          Update #1:



          Many details of this installation came forward in the comments, and we still don't have a final working solution. Here are some points to recognize...





          DNSStubListener=no does not belong in /etc/resolv.conf. (/etc/resolv.conf should not (normally) be edited directly). It's an edit to /etc/systemd/resolved.conf. DNS= can also be edited there to add DNS server addresses.





          /etc/resolv.conf should be a symlink, linked to one of two possible locations in /run.



          NEW -> /run/systemd/resolve/resolv.conf
          OLD -> ../run/resolvconf/resolv.conf


          and should contain either 127.0.0.53 (or 127.0.0.1 if dnsmasq was running), or DNS nameserver addresses, or your router's address (ex: 192.168.1.1)





          If you're going to use NetworkManager instead of netplan, then /etc/netplan should contain at least one .yaml file containing...



          network:
          version: 2
          renderer: NetworkManager


          followed by...



          sudo netplan --debug generate # generate config files



          sudo netplan apply # apply configuration





          If you're using NetworkManager, then /etc/NetworkManager/NetworkManager.conf should exist... and should look something like...



          [main]
          plugins=ifupdown,keyfile

          [ifupdown]
          managed=false

          [device]
          wifi.scan-rand-mac-address=no




          If dnsmasq AND systemd-resolve are running, then you should do #1 in my answer.



          If dnsmasq is not running, and systemd-resolve is running, then you should do #2 in my answer.









          share|improve this answer


























          • When i run ps auxc | grep -i dns there is no output (pressumeably because I have disabled systemd-resolve, I will try this a minute when a machine has finished its upgrade

            – Dan
            Dec 27 '18 at 12:14











          • That command is looking for dnsmasq. You must not be running it. Re-enable systemd-resolve, and then cat /etc/resolv.conf and you'll probably see 127.0.0.53 indicating that systemd-resolve is managing /etc/resolv.conf. Try item #2 in my answer then.

            – heynnema
            Dec 27 '18 at 12:40













          • /run/systemd/resolve/ doesn't exist but i restored the original resolv.conf adding the line DNSStubListener=no and this appears to have fixed the issue

            – Dan
            Dec 27 '18 at 12:46











          • @Dan That should be /run/systemd/resolve/resolv.conf, It will only be there if systemd-resolve is running. Great news! Please remember to accept my answer. Thanks!

            – heynnema
            Dec 27 '18 at 12:53













          • Just rebooted and tried again, thanks for the help!

            – Dan
            Dec 27 '18 at 12:59














          2












          2








          2







          Re-enable systemd-resolve.



          Two possibilities...




          1. Regarding dnsmasq and systemd-resolved...


          Do a ps auxc | grep -i dns and ps auxc | grep -i resolv and look for dnsmasq and systemd-resolved, and if both are running, you need to disable the DNS part of systemd-resolved by editing /etc/systemd/resolved.conf and...



          change:



          #DNSStubListener=yes


          to:



          DNSStubListener=no


          then restart systemd-resolve and dnsmasq, or reboot.





          1. you MAY need to reset the symlink that is /etc/resolv.conf (if dnsmasq is not running)...


          sudo mv /etc/resolv.conf /etc/resolv.conf.OLD # save the old symlink



          sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf # create new symlink



          Update #1:



          Many details of this installation came forward in the comments, and we still don't have a final working solution. Here are some points to recognize...





          DNSStubListener=no does not belong in /etc/resolv.conf. (/etc/resolv.conf should not (normally) be edited directly). It's an edit to /etc/systemd/resolved.conf. DNS= can also be edited there to add DNS server addresses.





          /etc/resolv.conf should be a symlink, linked to one of two possible locations in /run.



          NEW -> /run/systemd/resolve/resolv.conf
          OLD -> ../run/resolvconf/resolv.conf


          and should contain either 127.0.0.53 (or 127.0.0.1 if dnsmasq was running), or DNS nameserver addresses, or your router's address (ex: 192.168.1.1)





          If you're going to use NetworkManager instead of netplan, then /etc/netplan should contain at least one .yaml file containing...



          network:
          version: 2
          renderer: NetworkManager


          followed by...



          sudo netplan --debug generate # generate config files



          sudo netplan apply # apply configuration





          If you're using NetworkManager, then /etc/NetworkManager/NetworkManager.conf should exist... and should look something like...



          [main]
          plugins=ifupdown,keyfile

          [ifupdown]
          managed=false

          [device]
          wifi.scan-rand-mac-address=no




          If dnsmasq AND systemd-resolve are running, then you should do #1 in my answer.



          If dnsmasq is not running, and systemd-resolve is running, then you should do #2 in my answer.









          share|improve this answer















          Re-enable systemd-resolve.



          Two possibilities...




          1. Regarding dnsmasq and systemd-resolved...


          Do a ps auxc | grep -i dns and ps auxc | grep -i resolv and look for dnsmasq and systemd-resolved, and if both are running, you need to disable the DNS part of systemd-resolved by editing /etc/systemd/resolved.conf and...



          change:



          #DNSStubListener=yes


          to:



          DNSStubListener=no


          then restart systemd-resolve and dnsmasq, or reboot.





          1. you MAY need to reset the symlink that is /etc/resolv.conf (if dnsmasq is not running)...


          sudo mv /etc/resolv.conf /etc/resolv.conf.OLD # save the old symlink



          sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf # create new symlink



          Update #1:



          Many details of this installation came forward in the comments, and we still don't have a final working solution. Here are some points to recognize...





          DNSStubListener=no does not belong in /etc/resolv.conf. (/etc/resolv.conf should not (normally) be edited directly). It's an edit to /etc/systemd/resolved.conf. DNS= can also be edited there to add DNS server addresses.





          /etc/resolv.conf should be a symlink, linked to one of two possible locations in /run.



          NEW -> /run/systemd/resolve/resolv.conf
          OLD -> ../run/resolvconf/resolv.conf


          and should contain either 127.0.0.53 (or 127.0.0.1 if dnsmasq was running), or DNS nameserver addresses, or your router's address (ex: 192.168.1.1)





          If you're going to use NetworkManager instead of netplan, then /etc/netplan should contain at least one .yaml file containing...



          network:
          version: 2
          renderer: NetworkManager


          followed by...



          sudo netplan --debug generate # generate config files



          sudo netplan apply # apply configuration





          If you're using NetworkManager, then /etc/NetworkManager/NetworkManager.conf should exist... and should look something like...



          [main]
          plugins=ifupdown,keyfile

          [ifupdown]
          managed=false

          [device]
          wifi.scan-rand-mac-address=no




          If dnsmasq AND systemd-resolve are running, then you should do #1 in my answer.



          If dnsmasq is not running, and systemd-resolve is running, then you should do #2 in my answer.










          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited 15 mins ago

























          answered Dec 27 '18 at 11:59









          heynnemaheynnema

          18.7k22155




          18.7k22155













          • When i run ps auxc | grep -i dns there is no output (pressumeably because I have disabled systemd-resolve, I will try this a minute when a machine has finished its upgrade

            – Dan
            Dec 27 '18 at 12:14











          • That command is looking for dnsmasq. You must not be running it. Re-enable systemd-resolve, and then cat /etc/resolv.conf and you'll probably see 127.0.0.53 indicating that systemd-resolve is managing /etc/resolv.conf. Try item #2 in my answer then.

            – heynnema
            Dec 27 '18 at 12:40













          • /run/systemd/resolve/ doesn't exist but i restored the original resolv.conf adding the line DNSStubListener=no and this appears to have fixed the issue

            – Dan
            Dec 27 '18 at 12:46











          • @Dan That should be /run/systemd/resolve/resolv.conf, It will only be there if systemd-resolve is running. Great news! Please remember to accept my answer. Thanks!

            – heynnema
            Dec 27 '18 at 12:53













          • Just rebooted and tried again, thanks for the help!

            – Dan
            Dec 27 '18 at 12:59



















          • When i run ps auxc | grep -i dns there is no output (pressumeably because I have disabled systemd-resolve, I will try this a minute when a machine has finished its upgrade

            – Dan
            Dec 27 '18 at 12:14











          • That command is looking for dnsmasq. You must not be running it. Re-enable systemd-resolve, and then cat /etc/resolv.conf and you'll probably see 127.0.0.53 indicating that systemd-resolve is managing /etc/resolv.conf. Try item #2 in my answer then.

            – heynnema
            Dec 27 '18 at 12:40













          • /run/systemd/resolve/ doesn't exist but i restored the original resolv.conf adding the line DNSStubListener=no and this appears to have fixed the issue

            – Dan
            Dec 27 '18 at 12:46











          • @Dan That should be /run/systemd/resolve/resolv.conf, It will only be there if systemd-resolve is running. Great news! Please remember to accept my answer. Thanks!

            – heynnema
            Dec 27 '18 at 12:53













          • Just rebooted and tried again, thanks for the help!

            – Dan
            Dec 27 '18 at 12:59

















          When i run ps auxc | grep -i dns there is no output (pressumeably because I have disabled systemd-resolve, I will try this a minute when a machine has finished its upgrade

          – Dan
          Dec 27 '18 at 12:14





          When i run ps auxc | grep -i dns there is no output (pressumeably because I have disabled systemd-resolve, I will try this a minute when a machine has finished its upgrade

          – Dan
          Dec 27 '18 at 12:14













          That command is looking for dnsmasq. You must not be running it. Re-enable systemd-resolve, and then cat /etc/resolv.conf and you'll probably see 127.0.0.53 indicating that systemd-resolve is managing /etc/resolv.conf. Try item #2 in my answer then.

          – heynnema
          Dec 27 '18 at 12:40







          That command is looking for dnsmasq. You must not be running it. Re-enable systemd-resolve, and then cat /etc/resolv.conf and you'll probably see 127.0.0.53 indicating that systemd-resolve is managing /etc/resolv.conf. Try item #2 in my answer then.

          – heynnema
          Dec 27 '18 at 12:40















          /run/systemd/resolve/ doesn't exist but i restored the original resolv.conf adding the line DNSStubListener=no and this appears to have fixed the issue

          – Dan
          Dec 27 '18 at 12:46





          /run/systemd/resolve/ doesn't exist but i restored the original resolv.conf adding the line DNSStubListener=no and this appears to have fixed the issue

          – Dan
          Dec 27 '18 at 12:46













          @Dan That should be /run/systemd/resolve/resolv.conf, It will only be there if systemd-resolve is running. Great news! Please remember to accept my answer. Thanks!

          – heynnema
          Dec 27 '18 at 12:53







          @Dan That should be /run/systemd/resolve/resolv.conf, It will only be there if systemd-resolve is running. Great news! Please remember to accept my answer. Thanks!

          – heynnema
          Dec 27 '18 at 12:53















          Just rebooted and tried again, thanks for the help!

          – Dan
          Dec 27 '18 at 12:59





          Just rebooted and tried again, thanks for the help!

          – Dan
          Dec 27 '18 at 12:59


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Ask Ubuntu!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1104863%2fsamba-internal-dns-systemd-resolve-safe-to-disable%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          GameSpot

          日野市

          Tu-95轟炸機