Questions

Create a private network with the same or similar domain name

Tags:
+
0 Votes
Locked

Create a private network with the same or similar domain name

RTC-IT
I own my domain name and it is registered through an external host provider for my website. I would like to create a private network with the same or similar domain name without causing conflicts with my existing domain host and not have problems qualifying the name. How should I address this and/or is it possible. I will be using various free server platforms and computers. They will all have internet access, (although some might remain isolated members of the active directory for testing purposes).

My example domain name:
>www.mydomain.com

Can I use names such as;
>mydomain.com
>private.mydomain.com
>mydomain.local
>local.mydomain.com
>server1.private.mydomain.com

or should i just choose some other name and later deal with attempting to migrate or cluster servers.
  • +
    0 Votes

    yes

    gdeangelis

    You can use mydomain.com. Companies do this all the time. Your site should be protected from the internet and in a dmz. This is assuming you are not using the website's server for authentication-a/d for your internal domain. That would not be advisable.
    You won't have any problems with name resolution, because that is done externally through the company hosting your records on the outside, so to speak. Internally, your server, if on the same domain, would have its own internal host record, independent of the external dns.

    +
    0 Votes
    vovokorp

    You can create a private network by using a dedicated server provided by XnYnZ.com .The full server will be dedicated to you so that you can create your own private network.

    +
    0 Votes
    JPElectron

    Let's say your public domain (website) is: example.com

    You should avoid using just that for any internal active directory network (it will cause you problems later on with DNS names, and possibly leak internal FQDN/records to the Internet which is a security risk).

    When setting up active directory you can still use your public domain, but the AD should be a separate zone, this is often referred to as NetBios domain name, or pre-Windows 2000 domain name, for example...

    internal.example.com or private.example.com

    You can also use any of the following non-public and un-registerable root domains like...

    .test
    .example
    .invalid
    .localhost

    ...or with a NetBios domain...

    newco.test
    newco.example
    newco.invalid
    newco.localhost

    In any case, the second "zone" (really a sub-domain) is what will show up in the "logon to" drop-down box at CTRL+ALT+DEL, for example...

    FQDN: internal.example.com Logon domain: INTERNAL
    Full computer names: pc1.internal.example.com, pc2.internal.example.com, server5.internal.example.com, etc.

    FQDN: newco.example Logon domain: NEWCO
    Full computer names: pc1.newco.example, pc2.newco.example, server5.newco.example

  • +
    0 Votes

    yes

    gdeangelis

    You can use mydomain.com. Companies do this all the time. Your site should be protected from the internet and in a dmz. This is assuming you are not using the website's server for authentication-a/d for your internal domain. That would not be advisable.
    You won't have any problems with name resolution, because that is done externally through the company hosting your records on the outside, so to speak. Internally, your server, if on the same domain, would have its own internal host record, independent of the external dns.

    +
    0 Votes
    vovokorp

    You can create a private network by using a dedicated server provided by XnYnZ.com .The full server will be dedicated to you so that you can create your own private network.

    +
    0 Votes
    JPElectron

    Let's say your public domain (website) is: example.com

    You should avoid using just that for any internal active directory network (it will cause you problems later on with DNS names, and possibly leak internal FQDN/records to the Internet which is a security risk).

    When setting up active directory you can still use your public domain, but the AD should be a separate zone, this is often referred to as NetBios domain name, or pre-Windows 2000 domain name, for example...

    internal.example.com or private.example.com

    You can also use any of the following non-public and un-registerable root domains like...

    .test
    .example
    .invalid
    .localhost

    ...or with a NetBios domain...

    newco.test
    newco.example
    newco.invalid
    newco.localhost

    In any case, the second "zone" (really a sub-domain) is what will show up in the "logon to" drop-down box at CTRL+ALT+DEL, for example...

    FQDN: internal.example.com Logon domain: INTERNAL
    Full computer names: pc1.internal.example.com, pc2.internal.example.com, server5.internal.example.com, etc.

    FQDN: newco.example Logon domain: NEWCO
    Full computer names: pc1.newco.example, pc2.newco.example, server5.newco.example