Server member of 1 Domain, but in different DNS domain

[loneWolf9]

Ok, I understand the basic of DNS. Not an DNS expert, but know enough to setup the basics.

However I have a question maybe someone can help with.

We have a server from our domain "ABC.net" that has to be located at our parent company "XYZ.net" for reason not getting into.

The server is a member of our domain, Server.ABC.net.
However has a DNS domain entry add to it for XYZ.net

I understand that it uses the DNS server for XYZ.net

If you ping it the server comes back as Server.XYZ.net

My question is why would one need to put in the entry for XYZ.net
When there is a trust, between domains, and all authenication comes from the ABC.net domain.

Would it not be eaiser to just let it be part of the ABC.net domain?

Can anyone explain to me why you might want to do this?

Just trying to better understand.

 

[itsp1965]

I think where your confusion lies is the separation of AD domain and DNS domain entries. Your server may be physically part of the ABC.net AD domain (for authentication, resource access etc) and by default has a host entry for it in the associated DNS database.

This is not to say that the hostname itself cannot be resolved by other non AD DNS servers as well.
Let's say the server is an application server where the app has its own auth scheme and users located in XYZ.NET need to access it.

You can either have XYZ.NET DNS forward the request to servera.ABC.net or another a host name entry could have been added to XYZ.NET instead (not the best means but it can be done)in order to help folks resolve the name.

Hope this helps.