Re: Intranet Naming Standard? - TCP-IP

This is a discussion on Re: Intranet Naming Standard? - TCP-IP ; 1/2 the team wants to use companyname.com, or companyname.gbl That half of the team is on the correct track, although a subdomain of your publically registered domain name is best, not some made up unregistered domain name such as companyname.gbl.. ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Re: Intranet Naming Standard?

  1. Re: Intranet Naming Standard?


    1/2 the team wants to use companyname.com, or companyname.gbl

    That half of the team is on the correct track, although a subdomain of your publically registered domain name is best, not some made up unregistered domain name such as companyname.gbl.. That latter is just as bad an idea as that of the other half of the team:

    1/2 the team wants to create new TLD(s) for these devices.

    That half of the team isn't thinking things through.  There's no guarantee that the TLDs that they choose won't exist in the future in both the diminutive root and the augmented root.  Indeed they may already exist in the augmented root.  As such, that half of the team is proposing cutting your company off from any public use of those TLDs.



    You could use local., the commonly-suggested TLD for this sort of thing.  However: 

    It's not officially guaranteed to work.  local. is not reserved by RFC 2606.  The several attempts to include it as a reserved TLD never succeeded.  Although the possibility is unlikely, it might be used publically in the future.
    It won't work in practice in various situations, because it is already hi-jacked by something else.  Apple's Rendezvous hi-jacks it, for example (even though it isn't a RFC 2606 reserved TLD that Apple can officially use).


    Instead, make use of the very nature of the DNS namespace and use subdomains. Have, say, workstations.example.com.,  servers.example.com., services.example.com., and routers.example.com. subdomains.  You have this facility in DNS.  Use it.


    us126509-1.companyname.com or us126509-1.lan?
    a8usaca0001.companyname.com or a8usaca0001.wan?
    us126509-1.internal.routers.example.com.
    a8usaca0001.external.routers.example.com.
    companystore.companyname.com or companystore.app?
    peoplesoft.companyname.com or peoplesoft.app?
    timecard.companyname.com or timecard.app?
    companystore.services.example.com.
    peoplesoft.services.example.com.
    timecard.services.example.com.
    sunfile1.companyname.com or sunfile1.unx?
    fileserver1.sun.servers.example.com.
    Private IP's (virtual hosting, router-router heartbeats,etc ... ) .PRI?


    No.  Use the domain names that are already provided by the standards, such as 1.0.168.192.in-addr.arpa. for 192.168.0.1 for example; employing walldns to make life simple for yourself if you like.


  2. Re: Intranet Naming Standard?

    Jonathan de Boyne Pollard wrote:
    >
    >
    >
    >


    ( html stuff deleted )

    If this is intended for public perusual, please repost in readable form !


    --
    Peter Håkanson
    IPSec Sverige ( At Gothenburg Riverside )
    Sorry about my e-mail address, but i'm trying to keep spam out,
    remove "icke-reklam" if you feel for mailing me. Thanx.

  3. Re: Intranet Naming Standard?

    In article , Jonathan de
    Boyne Pollard wrote:

    >
    >
    > [etc]


    HTML news postings, just say no.

    Sam

+ Reply to Thread