Can DHCP and DNS both use .local on the same LAN?












0















My local LAN machines are assigned IP addresses from a Fortigate 60D DHCP server.

The DHCP uses .local as its domain name.
I now started a DNS server, also running off the Fortigate 60D.



I'm reluctant to set the DNS domain name to also be .local, as it seems to me that this may cause clashes.



Am I being paranoid, or is my apprehension justified?










share|improve this question


















  • 3





    In my practice DHCP and DNS are always in the same domain

    – Gert Jan Kraaijeveld
    Jan 21 at 19:59






  • 2





    That depends on the Fortigate management software, if you can set it to return your DNS server's IP address with the DHCP return answer. This might require giving it a static IP address. The Fortigate manuals I can find on the Internet don't have the necessary info.

    – harrymc
    Jan 21 at 20:37


















0















My local LAN machines are assigned IP addresses from a Fortigate 60D DHCP server.

The DHCP uses .local as its domain name.
I now started a DNS server, also running off the Fortigate 60D.



I'm reluctant to set the DNS domain name to also be .local, as it seems to me that this may cause clashes.



Am I being paranoid, or is my apprehension justified?










share|improve this question


















  • 3





    In my practice DHCP and DNS are always in the same domain

    – Gert Jan Kraaijeveld
    Jan 21 at 19:59






  • 2





    That depends on the Fortigate management software, if you can set it to return your DNS server's IP address with the DHCP return answer. This might require giving it a static IP address. The Fortigate manuals I can find on the Internet don't have the necessary info.

    – harrymc
    Jan 21 at 20:37
















0












0








0








My local LAN machines are assigned IP addresses from a Fortigate 60D DHCP server.

The DHCP uses .local as its domain name.
I now started a DNS server, also running off the Fortigate 60D.



I'm reluctant to set the DNS domain name to also be .local, as it seems to me that this may cause clashes.



Am I being paranoid, or is my apprehension justified?










share|improve this question














My local LAN machines are assigned IP addresses from a Fortigate 60D DHCP server.

The DHCP uses .local as its domain name.
I now started a DNS server, also running off the Fortigate 60D.



I'm reluctant to set the DNS domain name to also be .local, as it seems to me that this may cause clashes.



Am I being paranoid, or is my apprehension justified?







networking dns ip dhcp fortigate






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 21 at 19:54









boardriderboardrider

2902719




2902719








  • 3





    In my practice DHCP and DNS are always in the same domain

    – Gert Jan Kraaijeveld
    Jan 21 at 19:59






  • 2





    That depends on the Fortigate management software, if you can set it to return your DNS server's IP address with the DHCP return answer. This might require giving it a static IP address. The Fortigate manuals I can find on the Internet don't have the necessary info.

    – harrymc
    Jan 21 at 20:37
















  • 3





    In my practice DHCP and DNS are always in the same domain

    – Gert Jan Kraaijeveld
    Jan 21 at 19:59






  • 2





    That depends on the Fortigate management software, if you can set it to return your DNS server's IP address with the DHCP return answer. This might require giving it a static IP address. The Fortigate manuals I can find on the Internet don't have the necessary info.

    – harrymc
    Jan 21 at 20:37










3




3





In my practice DHCP and DNS are always in the same domain

– Gert Jan Kraaijeveld
Jan 21 at 19:59





In my practice DHCP and DNS are always in the same domain

– Gert Jan Kraaijeveld
Jan 21 at 19:59




2




2





That depends on the Fortigate management software, if you can set it to return your DNS server's IP address with the DHCP return answer. This might require giving it a static IP address. The Fortigate manuals I can find on the Internet don't have the necessary info.

– harrymc
Jan 21 at 20:37







That depends on the Fortigate management software, if you can set it to return your DNS server's IP address with the DHCP return answer. This might require giving it a static IP address. The Fortigate manuals I can find on the Internet don't have the necessary info.

– harrymc
Jan 21 at 20:37












1 Answer
1






active

oldest

votes


















1














There is no problem with DNS and DHCP using the same domain name. But the name .local is special; it is reserved for mDNS and you should not configure a DNS server to use the .localTLD. From RFC6762:




This document specifies that the DNS top-level domain .local." is a
special domain with special semantics, namely that any fully qualified
name ending in ".local." is link-local, and names within this domain
are meaningful only on the link where they originate.







share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    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%2fsuperuser.com%2fquestions%2f1396753%2fcan-dhcp-and-dns-both-use-local-on-the-same-lan%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














    There is no problem with DNS and DHCP using the same domain name. But the name .local is special; it is reserved for mDNS and you should not configure a DNS server to use the .localTLD. From RFC6762:




    This document specifies that the DNS top-level domain .local." is a
    special domain with special semantics, namely that any fully qualified
    name ending in ".local." is link-local, and names within this domain
    are meaningful only on the link where they originate.







    share|improve this answer




























      1














      There is no problem with DNS and DHCP using the same domain name. But the name .local is special; it is reserved for mDNS and you should not configure a DNS server to use the .localTLD. From RFC6762:




      This document specifies that the DNS top-level domain .local." is a
      special domain with special semantics, namely that any fully qualified
      name ending in ".local." is link-local, and names within this domain
      are meaningful only on the link where they originate.







      share|improve this answer


























        1












        1








        1







        There is no problem with DNS and DHCP using the same domain name. But the name .local is special; it is reserved for mDNS and you should not configure a DNS server to use the .localTLD. From RFC6762:




        This document specifies that the DNS top-level domain .local." is a
        special domain with special semantics, namely that any fully qualified
        name ending in ".local." is link-local, and names within this domain
        are meaningful only on the link where they originate.







        share|improve this answer













        There is no problem with DNS and DHCP using the same domain name. But the name .local is special; it is reserved for mDNS and you should not configure a DNS server to use the .localTLD. From RFC6762:




        This document specifies that the DNS top-level domain .local." is a
        special domain with special semantics, namely that any fully qualified
        name ending in ".local." is link-local, and names within this domain
        are meaningful only on the link where they originate.








        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 22 at 6:40









        Johan MyréenJohan Myréen

        475125




        475125






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • 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%2fsuperuser.com%2fquestions%2f1396753%2fcan-dhcp-and-dns-both-use-local-on-the-same-lan%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á

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