How can I use netplan for DNS domains?












1















I am wondering if I actually need dnsmasq or Bind to apply the following simple DNS server rule:



Forward DNS lookups for *.mydomain.com to 10.0.0.2;



Forward DNS lookups for anything else to 8.8.8.8 or 8.8.4.4



Or can I do that in a /etc/netplan/*.yaml file using the nameserver field somehow?










share|improve this question



























    1















    I am wondering if I actually need dnsmasq or Bind to apply the following simple DNS server rule:



    Forward DNS lookups for *.mydomain.com to 10.0.0.2;



    Forward DNS lookups for anything else to 8.8.8.8 or 8.8.4.4



    Or can I do that in a /etc/netplan/*.yaml file using the nameserver field somehow?










    share|improve this question

























      1












      1








      1


      1






      I am wondering if I actually need dnsmasq or Bind to apply the following simple DNS server rule:



      Forward DNS lookups for *.mydomain.com to 10.0.0.2;



      Forward DNS lookups for anything else to 8.8.8.8 or 8.8.4.4



      Or can I do that in a /etc/netplan/*.yaml file using the nameserver field somehow?










      share|improve this question














      I am wondering if I actually need dnsmasq or Bind to apply the following simple DNS server rule:



      Forward DNS lookups for *.mydomain.com to 10.0.0.2;



      Forward DNS lookups for anything else to 8.8.8.8 or 8.8.4.4



      Or can I do that in a /etc/netplan/*.yaml file using the nameserver field somehow?







      dns netplan dnsmasq






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 6 at 20:02









      JSStuballJSStuball

      1234




      1234






















          1 Answer
          1






          active

          oldest

          votes


















          1














          It is possible to configure systemd-resolved to do this, but not through netplan. E.g. systemd-resolve -i ens2 --set-dns=10.0.0.2 --set-domain=~mydomain.com



          You should also be able to configure this statically with a .network file; see systemd.network(5) for information.






          share|improve this answer
























          • I tried creating a foo.network file in /etc/systemd/network and populating it simply with [Network]nDNS=10.0.0.2nDomains=mydomain.com but it didn't work.

            – JSStuball
            Feb 8 at 4:29











          • You may need to make sure you apply a [Match] rule as well, and you also need to make sure the filename you use lexically sorts before 99-default.link, otherwise /lib/systemd/network/99-default.link will take precedence. To be honest I have not used .network files like this myself however, so I only know the generalities of how it's supposed to work.

            – slangasek
            Feb 8 at 19:39











          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%2f1116194%2fhow-can-i-use-netplan-for-dns-domains%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









          1














          It is possible to configure systemd-resolved to do this, but not through netplan. E.g. systemd-resolve -i ens2 --set-dns=10.0.0.2 --set-domain=~mydomain.com



          You should also be able to configure this statically with a .network file; see systemd.network(5) for information.






          share|improve this answer
























          • I tried creating a foo.network file in /etc/systemd/network and populating it simply with [Network]nDNS=10.0.0.2nDomains=mydomain.com but it didn't work.

            – JSStuball
            Feb 8 at 4:29











          • You may need to make sure you apply a [Match] rule as well, and you also need to make sure the filename you use lexically sorts before 99-default.link, otherwise /lib/systemd/network/99-default.link will take precedence. To be honest I have not used .network files like this myself however, so I only know the generalities of how it's supposed to work.

            – slangasek
            Feb 8 at 19:39
















          1














          It is possible to configure systemd-resolved to do this, but not through netplan. E.g. systemd-resolve -i ens2 --set-dns=10.0.0.2 --set-domain=~mydomain.com



          You should also be able to configure this statically with a .network file; see systemd.network(5) for information.






          share|improve this answer
























          • I tried creating a foo.network file in /etc/systemd/network and populating it simply with [Network]nDNS=10.0.0.2nDomains=mydomain.com but it didn't work.

            – JSStuball
            Feb 8 at 4:29











          • You may need to make sure you apply a [Match] rule as well, and you also need to make sure the filename you use lexically sorts before 99-default.link, otherwise /lib/systemd/network/99-default.link will take precedence. To be honest I have not used .network files like this myself however, so I only know the generalities of how it's supposed to work.

            – slangasek
            Feb 8 at 19:39














          1












          1








          1







          It is possible to configure systemd-resolved to do this, but not through netplan. E.g. systemd-resolve -i ens2 --set-dns=10.0.0.2 --set-domain=~mydomain.com



          You should also be able to configure this statically with a .network file; see systemd.network(5) for information.






          share|improve this answer













          It is possible to configure systemd-resolved to do this, but not through netplan. E.g. systemd-resolve -i ens2 --set-dns=10.0.0.2 --set-domain=~mydomain.com



          You should also be able to configure this statically with a .network file; see systemd.network(5) for information.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 7 at 19:08









          slangasekslangasek

          2,56811419




          2,56811419













          • I tried creating a foo.network file in /etc/systemd/network and populating it simply with [Network]nDNS=10.0.0.2nDomains=mydomain.com but it didn't work.

            – JSStuball
            Feb 8 at 4:29











          • You may need to make sure you apply a [Match] rule as well, and you also need to make sure the filename you use lexically sorts before 99-default.link, otherwise /lib/systemd/network/99-default.link will take precedence. To be honest I have not used .network files like this myself however, so I only know the generalities of how it's supposed to work.

            – slangasek
            Feb 8 at 19:39



















          • I tried creating a foo.network file in /etc/systemd/network and populating it simply with [Network]nDNS=10.0.0.2nDomains=mydomain.com but it didn't work.

            – JSStuball
            Feb 8 at 4:29











          • You may need to make sure you apply a [Match] rule as well, and you also need to make sure the filename you use lexically sorts before 99-default.link, otherwise /lib/systemd/network/99-default.link will take precedence. To be honest I have not used .network files like this myself however, so I only know the generalities of how it's supposed to work.

            – slangasek
            Feb 8 at 19:39

















          I tried creating a foo.network file in /etc/systemd/network and populating it simply with [Network]nDNS=10.0.0.2nDomains=mydomain.com but it didn't work.

          – JSStuball
          Feb 8 at 4:29





          I tried creating a foo.network file in /etc/systemd/network and populating it simply with [Network]nDNS=10.0.0.2nDomains=mydomain.com but it didn't work.

          – JSStuball
          Feb 8 at 4:29













          You may need to make sure you apply a [Match] rule as well, and you also need to make sure the filename you use lexically sorts before 99-default.link, otherwise /lib/systemd/network/99-default.link will take precedence. To be honest I have not used .network files like this myself however, so I only know the generalities of how it's supposed to work.

          – slangasek
          Feb 8 at 19:39





          You may need to make sure you apply a [Match] rule as well, and you also need to make sure the filename you use lexically sorts before 99-default.link, otherwise /lib/systemd/network/99-default.link will take precedence. To be honest I have not used .network files like this myself however, so I only know the generalities of how it's supposed to work.

          – slangasek
          Feb 8 at 19:39


















          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%2f1116194%2fhow-can-i-use-netplan-for-dns-domains%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

          flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

          Mangá

           ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕