Systemd-resolved not getting nameservers from DHCP

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


.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
0
down vote

favorite












I'm running a few ubuntu 18.04 servers in a Windows AD environment. The servers have no problem getting IPs via DHCP, but the DNS settings specified in option-6 are not written to any files.



Originally, I just updated /etc/resolv.conf, but this config wouldn't hold after a reboot. The standard 18.04 image uses NetPlan so we aren't concerned here about NetworkManager. After tracing it back to systemd-resolved and having to hardset the nameservers in the /etc/systemd/resolved.conf things seem to be working.



My question is simply how does one rectify dhcpcd option-6 with systemd-resolved? I don't want to have to hardset these variable on the creation of each server.



Also, dnsmasq doesn't seem to be an issue here, it's caching just fine as /etc/resolv.conf still points to 127.0.0.1 as long as /etc/systemd/resolved.conf has the DNS settings.







share|improve this question

























    up vote
    0
    down vote

    favorite












    I'm running a few ubuntu 18.04 servers in a Windows AD environment. The servers have no problem getting IPs via DHCP, but the DNS settings specified in option-6 are not written to any files.



    Originally, I just updated /etc/resolv.conf, but this config wouldn't hold after a reboot. The standard 18.04 image uses NetPlan so we aren't concerned here about NetworkManager. After tracing it back to systemd-resolved and having to hardset the nameservers in the /etc/systemd/resolved.conf things seem to be working.



    My question is simply how does one rectify dhcpcd option-6 with systemd-resolved? I don't want to have to hardset these variable on the creation of each server.



    Also, dnsmasq doesn't seem to be an issue here, it's caching just fine as /etc/resolv.conf still points to 127.0.0.1 as long as /etc/systemd/resolved.conf has the DNS settings.







    share|improve this question





















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I'm running a few ubuntu 18.04 servers in a Windows AD environment. The servers have no problem getting IPs via DHCP, but the DNS settings specified in option-6 are not written to any files.



      Originally, I just updated /etc/resolv.conf, but this config wouldn't hold after a reboot. The standard 18.04 image uses NetPlan so we aren't concerned here about NetworkManager. After tracing it back to systemd-resolved and having to hardset the nameservers in the /etc/systemd/resolved.conf things seem to be working.



      My question is simply how does one rectify dhcpcd option-6 with systemd-resolved? I don't want to have to hardset these variable on the creation of each server.



      Also, dnsmasq doesn't seem to be an issue here, it's caching just fine as /etc/resolv.conf still points to 127.0.0.1 as long as /etc/systemd/resolved.conf has the DNS settings.







      share|improve this question











      I'm running a few ubuntu 18.04 servers in a Windows AD environment. The servers have no problem getting IPs via DHCP, but the DNS settings specified in option-6 are not written to any files.



      Originally, I just updated /etc/resolv.conf, but this config wouldn't hold after a reboot. The standard 18.04 image uses NetPlan so we aren't concerned here about NetworkManager. After tracing it back to systemd-resolved and having to hardset the nameservers in the /etc/systemd/resolved.conf things seem to be working.



      My question is simply how does one rectify dhcpcd option-6 with systemd-resolved? I don't want to have to hardset these variable on the creation of each server.



      Also, dnsmasq doesn't seem to be an issue here, it's caching just fine as /etc/resolv.conf still points to 127.0.0.1 as long as /etc/systemd/resolved.conf has the DNS settings.









      share|improve this question










      share|improve this question




      share|improve this question









      asked 2 days ago









      ShOC_lost

      1




      1

























          active

          oldest

          votes











          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%2f1062143%2fsystemd-resolved-not-getting-nameservers-from-dhcp%23new-answer', 'question_page');

          );

          Post as a guest



































          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes










           

          draft saved


          draft discarded


























           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1062143%2fsystemd-resolved-not-getting-nameservers-from-dhcp%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