Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

LAN Domain, Best Practice

  • 15-10-2012 8:08pm
    #1
    oB1
    Registered Users, Registered Users 2 Posts: 706 ✭✭✭


    So; i have a domain for a company to create.

    I wanted to get people's opinions to the "Best Practice" for creating this.

    I have two ideas in mind; saidcompanynet.com OR Lan.saidcompanynet.com

    is it bad practice to name the root domain, as a child-like domain?

    ideas and opinions are welcomed!

    Cheers

    Rob


Comments

  • #2
    tech
    Registered Users, Registered Users 2 Posts: 2,860 ✭✭✭tech


    I assume your reffering to active Directory?

    if so mycompany.local

    dont use a FQDN on a LAN as in mycompany.com


  • #3
    oB1
    Registered Users, Registered Users 2 Posts: 706 ✭✭✭oB1


    tech wrote: »
    I assume your reffering to active Directory?

    if so mycompany.local

    dont use a FQDN on a LAN as in mycompany.com

    Yes, of course, sorry; I am referring to AD.

    My question wasn't really about using a FQDN for the LAN - using a FQDN isn't an issue really, at least not on my own professional experience, IMO you run in to DNS issues if you do, anyway, back to my question at hand: Im asking if its bad practice to name the Parent domain like a sub domain
    " Lan.SaidCompanynet.com "

    R


  • #4
    demanufactured
    Closed Accounts Posts: 5,756 ✭✭✭demanufactured


    RobertHopkins wrote: »

    Yes, of course, sorry; I am referring to AD.

    My question wasn't really about using a FQDN for the LAN - using a FQDN isn't an issue really, at least not on my own professional experience, IMO you run in to DNS issues if you do, anyway, back to my question at hand: Im asking if its bad practice to name the Parent domain like a sub domain
    " Lan.SaidCompanynet.com "

    R
    Name it lan.saidcompanyname.local or saidcompanyname.local.


Advertisement