Announcement

Collapse
No announcement yet.

.local vs top level domain

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • .local vs top level domain

    We are having a bit of an argument here.

    When would you give AD a .local domain and when a top level domain ?

    Obviously .local isn't routeable .. but in that particular case it doesn't have to.

    Basically there is one Server which supposed to run Exchange (also acting as domain controller) and one webserver which will be joined to the domain.

    The exchange server will host one domain which ie. example.com .. and the webserver will host the website example.com

    Now - would you name the actuall AD example.com or example.local ?

  • #2
    Re: .local vs top level domain

    I would never use a valid 'internet' TLD for an AD domain.

    I would also avoid using .local as a number of operating systems use that by default. Instead I would recommend using something that isn't going to cause any difficulties in the future - .lan, .office, .potato etc

    I would also not host the DNS records for my company's internet domain name on AD DNS servers, even if the webserver is hosted locally - I would choose a registrar that allows me to host the DNS for that domain on their systems. Some companies are expensive, but the majority are very reasonable these days - shop around and you will see just how cheap this is these days.
    Gareth Howells

    BSc (Hons), MBCS, MCP, MCDST, ICCE

    Any advice is given in good faith and without warranty.

    Please give reputation points if somebody has helped you.

    "For by now I could have stretched out my hand and struck you and your people with a plague that would have wiped you off the Earth." (Exodus 9:15) - I could kill you with my thumb.

    "Everything that lives and moves will be food for you." (Genesis 9:3) - For every animal you don't eat, I'm going to eat three.

    Comment


    • #3
      Re: .local vs top level domain

      .local apparently can cause issues with some firewalls as well.

      I normally use .internal
      Michael Armstrong
      www.m80arm.co.uk
      MCITP: EA, MCTS, MCSE 2003, MCSA 2003: Messaging, CCA, VCP 3.5, 4, 5, VCAP5-DCD, VCAP5-DCA, ITIL, MCP, PGP Certified Technician

      ** Remember to give credit where credit is due and leave reputation points sigpic where appropriate **

      Comment


      • #4
        Re: .local vs top level domain

        Originally posted by m80arm View Post
        .local apparently can cause issues with some firewalls as well.

        I normally use .internal
        Well trouble is, .local or .internal etc. are not routable ....

        Comment


        • #5
          Re: .local vs top level domain

          Why would you want your AD FQDN to use a public TLD?
          Gareth Howells

          BSc (Hons), MBCS, MCP, MCDST, ICCE

          Any advice is given in good faith and without warranty.

          Please give reputation points if somebody has helped you.

          "For by now I could have stretched out my hand and struck you and your people with a plague that would have wiped you off the Earth." (Exodus 9:15) - I could kill you with my thumb.

          "Everything that lives and moves will be food for you." (Genesis 9:3) - For every animal you don't eat, I'm going to eat three.

          Comment


          • #6
            Re: .local vs top level domain

            Originally posted by Gomjaba View Post
            Well trouble is, .local or .internal etc. are not routable ....
            And why is that a problem?
            1 1 was a racehorse.
            2 2 was 1 2.
            1 1 1 1 race 1 day,
            2 2 1 1 2

            Comment


            • #7
              Re: .local vs top level domain

              Originally posted by Gomjaba View Post
              Well trouble is, .local or .internal etc. are not routable ....
              Well luckily Domain names aren't routable at all so that is one trouble you might remove from your list
              Marcel
              Technical Consultant
              Netherlands
              http://www.phetios.com
              http://blog.nessus.nl

              MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
              "No matter how secure, there is always the human factor."

              "Enjoy life today, tomorrow may never come."
              "If you're going through hell, keep going. ~Winston Churchill"

              Comment


              • #8
                Re: .local vs top level domain

                Originally posted by Gomjaba View Post
                Well trouble is, .local or .internal etc. are not routable ....
                General wisdom in AD is that this is a good thing. Some sort of device (firewall, routers, ISA servers etc) should be the endpoint for all traffic in from the internet and it decides if it goes any further.
                BSc, MCSA: Server 2008, MCSE, MCSA: Messaging, MCTS
                sigpic
                Cruachan's Blog

                Comment


                • #9
                  Re: .local vs top level domain

                  Originally posted by Gomjaba View Post
                  Now - would you name the actuall AD example.com or example.local ?
                  As before, and as others have suggested, it is best avoided to use a public FQDN for your AD, unless you are sure that your network is not, and never will be, connected to the internet. Which is unlikely these days.

                  I would always pick an AD name ending with an "invalid" FQDN, and would usually base the rest of the name on the company name or initials. In my lab for example, the company name is Vapourware Inc, so the FQDN is vapourware.inc.lan. For a company called Theological Rabbit Stuffers, I might use trs.lan. For a company called Mercury Cauldrons, I would probably use mc.hammer

                  Gareth Howells

                  BSc (Hons), MBCS, MCP, MCDST, ICCE

                  Any advice is given in good faith and without warranty.

                  Please give reputation points if somebody has helped you.

                  "For by now I could have stretched out my hand and struck you and your people with a plague that would have wiped you off the Earth." (Exodus 9:15) - I could kill you with my thumb.

                  "Everything that lives and moves will be food for you." (Genesis 9:3) - For every animal you don't eat, I'm going to eat three.

                  Comment


                  • #10
                    Re: .local vs top level domain

                    In my lab I'm using phetios.lab
                    Works fine either
                    Marcel
                    Technical Consultant
                    Netherlands
                    http://www.phetios.com
                    http://blog.nessus.nl

                    MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
                    "No matter how secure, there is always the human factor."

                    "Enjoy life today, tomorrow may never come."
                    "If you're going through hell, keep going. ~Winston Churchill"

                    Comment


                    • #11
                      Re: .local vs top level domain

                      Originally posted by Gomjaba View Post
                      Well trouble is, .local or .internal etc. are not routable ....
                      Routing occurs at the network layer... domain names are way up there at the presentation layer. Routing and domain namespaces are therefore completely unrelated to each other - so what's your point?
                      Last edited by Stonelaughter; 16th January 2009, 18:15.


                      Tom
                      For my own and your protection, I do not provide support by private message under any circumstances. All such messages will be deleted and ignored.

                      Anything you say will be misquoted and used against you

                      Comment

                      Working...
                      X