Which trust is created with child domain?

I've got a situation I've never run across before, and I need some AD help/suggestions.  Just to complicate matters further, for the first time in 35 years, I'm not part of corporate IT.  Due to security regulations, the development group I just started with has to be able to block access to any of our servers from anyone in corporate, including IT (especially domain admins).

Right now, we all login to domain A (company.corporate.com), and all assets (users, laptops, servers, printers, etc.) are members of that domain, and all of our HR, Finance, Marketing, etc. is in that domain so we need to be able to access it.  (We also use O365 to host our Exchange.)  Because of this, and the fact that even domain admins can't legally have any access to our work (including overriding permissions), I've suggested creating a new domain B, secure.company.corporate.com.  I originally thought this would be a no-brainer, then I remembered one-way trusts in a parent/child relationship went out the window with NT.

How can I create a one-way transitive trust between domains A and B where A trusts B?  If I can't do this with a parent/child domain relationship, how should I go about it?  I don't mind dropping the company part of the domain name if I have to, but I want to keep the corporate.com piece of the name if at all possible (domain B would be secure.corporate.com in that case), which I don't think I can do if I create a standalone forest/domain and create a one-way transitive forest trust.

Anybody have any ideas on where I can start with this?  Are there any other solutions I'm missing?  (It's imperative that no one, including domain admins, from domain A can touch anything in domain B.)

A trust relationship is a logical link established between two domains. Between the two domains, one domain is called the trusting domain while the other is called the trusted domain. When a trust relationship is in place, the trusting domain honors the logon authentication of the trusted domain.

Generally, the trusted domain contains the users, while the trusting domain contains the resources. Therefore, users from the trusted domain will be able to access resources in the trusting domain because the users are trusted.

Trusts can be created automatically or manually. Trusts can also be classified as transitive and non-transitive. Transitive trust simply means that if Domain A trusts Domain B and Domain B trusts Domain C, then Domain A trusts Domain C.

Similarly with non-transitive trusts, if Domain A trusts Domain B and Domain B trusts Domain C, then Domain A does NOT trust Domain C. Also, trusts can be one-way or two-way. Different types of trusts described below are either one- or two-way by default.

Which trust is created with child domain?

Tree-root trust

A tree-root trust is implicitly established when you add a new tree root domain to a forest. The only domains that participate in the tree-root trust are those at the top of each of the trees. Tree-root trusts are two-way transitive trusts created automatically.

Parent-child trust

A parent-child trust relationship is implicitly established when you create a new child domain in a tree. The DCPromo process automatically creates a trust relationship between the new domain and the domain that immediately precedes it in the DNS namespace hierarchy. Parent-child trusts are two-way transitive trusts created automatically.

Shortcut trust

A shortcut trust must be explicitly created by a system administrator between two domains in the same forest. This type of trust is typically used in large forests where the administrator would manually create this type of trust to improve user logon time for those users that logon to computers in another domain within the forest. This type of trust is transitive and can be configured as one- or two-way.

External trust

An external trust must be explicitly created by a system administrator between two domains in different forests, or between a domain in an Active Directory forest and a Windows NT 4.0 or earlier domain. This trust is very useful when migrating resources from a Windows NT 4.0 domain to one within an Active Directory domain. This type of trust is non-transitive and can be one- or two-way.

Forest trust

A forest trust must be explicitly created by a systems administrator between two forest root domains (Windows 2003 and later). This trust allows for all domains in one forest to transitively trust all domains in another forest. However, this type of trust is not transitive over three or more forests. Forest trusts can be one-or two-way. Forest trusts are only available when the forest functional level is set to Windows Server 2003 or later.

Realm trust

A realm trust must be explicitly created by a systems administrator between a non-Windows Kerberos realm and a Windows 2003 or later domain. This type of trust can be transitive or non-transitive and one- or two-way.

The most important component in regards to trust relationships is the proper planning to ensure that users are provided with the access to resources that they require.

What type of trust relationship is automatically created between the domains?

Each time you create a new domain in a forest, a two-way, transitive trust relationship is automatically created between the new domain and its parent domain.

What are the different types of domain trusts?

There are four types of Active Directory trusts available — external trusts, realm trusts, forest trusts, and shortcut trusts. Each is explained below: External trust: You will create an external trust only if the resources are located in a different Active Directory forest.

What is one way and two

Some one-way trusts can be either non-transitive or transitive depending on the type of trust being created. In a two-way trust, Domain A trusts Domain B and Domain B trusts Domain A. This configuration means that authentication requests can be passed between the two domains in both directions.

What is a trust domain?

A trusted domain is a domain that the local system trusts to authenticate users. In other words, if a user or application is authenticated by a trusted domain, this authentication is accepted by all domains that trust the authenticating domain.