Why is /run/systemd/resolved.conf.d/isc-dhcp-v4-eno1.conf wrong?











up vote
0
down vote

favorite












Yesterday i updated Ubuntu 18.10, but after poweroff/poweron the DNS was wrong, so that routing worked, e. g. ping 8.8.8.8, but not name resolving.
So i overwrote the resolving files, e. g. /etc/resolv.conf, but that was not enough. I also had to overwrite /run/systemd/resolved.conf.d/isc-dhcp-v4-eno1.conf, because the file had



DNS=192.168.0.1



which ist wrong because that is the default gateway, not a DNS server!
Today, and without rebooting, the problem was back again; the process, dhclient -1 eno1, wrote the wrong value for the DNS server into /run/systemd/resolved.conf.d/isc-dhcp-v4-eno1.conf !
So as a workaround i am using:



# Workaround for the Bug that DHCP (dhclient -1 eno1) tries to use the Default-GW as a DNS server, under Ubuntu 18.10 and since 2018-11-18:
cp /root/bin/isc-dhcp-v4-eno1.conf /run/systemd/resolved.conf.d/isc-dhcp-v4-eno1.conf
systemctl restart systemd-resolved.service


in a Bash script which is called every half hour via /etc/crontab.
Is the a better solution for this Bug?



With Windows 8.1 the name resolving still works without problems.










share|improve this question


























    up vote
    0
    down vote

    favorite












    Yesterday i updated Ubuntu 18.10, but after poweroff/poweron the DNS was wrong, so that routing worked, e. g. ping 8.8.8.8, but not name resolving.
    So i overwrote the resolving files, e. g. /etc/resolv.conf, but that was not enough. I also had to overwrite /run/systemd/resolved.conf.d/isc-dhcp-v4-eno1.conf, because the file had



    DNS=192.168.0.1



    which ist wrong because that is the default gateway, not a DNS server!
    Today, and without rebooting, the problem was back again; the process, dhclient -1 eno1, wrote the wrong value for the DNS server into /run/systemd/resolved.conf.d/isc-dhcp-v4-eno1.conf !
    So as a workaround i am using:



    # Workaround for the Bug that DHCP (dhclient -1 eno1) tries to use the Default-GW as a DNS server, under Ubuntu 18.10 and since 2018-11-18:
    cp /root/bin/isc-dhcp-v4-eno1.conf /run/systemd/resolved.conf.d/isc-dhcp-v4-eno1.conf
    systemctl restart systemd-resolved.service


    in a Bash script which is called every half hour via /etc/crontab.
    Is the a better solution for this Bug?



    With Windows 8.1 the name resolving still works without problems.










    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      Yesterday i updated Ubuntu 18.10, but after poweroff/poweron the DNS was wrong, so that routing worked, e. g. ping 8.8.8.8, but not name resolving.
      So i overwrote the resolving files, e. g. /etc/resolv.conf, but that was not enough. I also had to overwrite /run/systemd/resolved.conf.d/isc-dhcp-v4-eno1.conf, because the file had



      DNS=192.168.0.1



      which ist wrong because that is the default gateway, not a DNS server!
      Today, and without rebooting, the problem was back again; the process, dhclient -1 eno1, wrote the wrong value for the DNS server into /run/systemd/resolved.conf.d/isc-dhcp-v4-eno1.conf !
      So as a workaround i am using:



      # Workaround for the Bug that DHCP (dhclient -1 eno1) tries to use the Default-GW as a DNS server, under Ubuntu 18.10 and since 2018-11-18:
      cp /root/bin/isc-dhcp-v4-eno1.conf /run/systemd/resolved.conf.d/isc-dhcp-v4-eno1.conf
      systemctl restart systemd-resolved.service


      in a Bash script which is called every half hour via /etc/crontab.
      Is the a better solution for this Bug?



      With Windows 8.1 the name resolving still works without problems.










      share|improve this question













      Yesterday i updated Ubuntu 18.10, but after poweroff/poweron the DNS was wrong, so that routing worked, e. g. ping 8.8.8.8, but not name resolving.
      So i overwrote the resolving files, e. g. /etc/resolv.conf, but that was not enough. I also had to overwrite /run/systemd/resolved.conf.d/isc-dhcp-v4-eno1.conf, because the file had



      DNS=192.168.0.1



      which ist wrong because that is the default gateway, not a DNS server!
      Today, and without rebooting, the problem was back again; the process, dhclient -1 eno1, wrote the wrong value for the DNS server into /run/systemd/resolved.conf.d/isc-dhcp-v4-eno1.conf !
      So as a workaround i am using:



      # Workaround for the Bug that DHCP (dhclient -1 eno1) tries to use the Default-GW as a DNS server, under Ubuntu 18.10 and since 2018-11-18:
      cp /root/bin/isc-dhcp-v4-eno1.conf /run/systemd/resolved.conf.d/isc-dhcp-v4-eno1.conf
      systemctl restart systemd-resolved.service


      in a Bash script which is called every half hour via /etc/crontab.
      Is the a better solution for this Bug?



      With Windows 8.1 the name resolving still works without problems.







      dns dhclient






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 19 at 17:14









      Rolf

      393




      393



























          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: 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%2f1094277%2fwhy-is-run-systemd-resolved-conf-d-isc-dhcp-v4-eno1-conf-wrong%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          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%2f1094277%2fwhy-is-run-systemd-resolved-conf-d-isc-dhcp-v4-eno1-conf-wrong%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

          Ellipse (mathématiques)

          Quarter-circle Tiles

          Mont Emei