How to configure DNS for a Windows 2016 DC that does “not completely master a domain” ? RRS feed

  • Question

  • Explanation:

    For historical reasons years ago our company decided to outsource a number of applications with the domain extension  to different providers.

    Now we need to install  an inhouse Active Directory for

    How can I setup my DC + DNS in order to first  look for “anything” on our internal network and IF NOT FOUND go on the internet ?

    Thus for example when:

    -           I operate (login,  force a gpo update, etc…)  on a computer in the domain  it finds my DC,

    -          I want to connect to app1.  I go on the internet  (to an IP we do not control, owned by Provider 1)

    -          I want to connect to app2.  I go to our inhouse server

    -          I want to connect to app3.  I go on the internet (to an IP we do not control owned by Provider 3)

    Let me just add that I cannot ask either of the providers to change anything in THEIR settings, and I HAVE  to use the  domain  for the AD.

    Wednesday, October 9, 2019 9:41 AM

All replies

  • First of all, this post is in the wrong forum.

    As for the question.  I am not 100% sure, but I think what you seek is the default behavior.

    Also, the applications you are creating in house, don't need to have the FQDN such as "", you can simply create some user friendly CNAMES such as "App2" You will need to create all these sites in house and you can name them whatever you want now.

    Nosh Mernacaj, Identity Management Specialist

    Wednesday, October 9, 2019 5:24 PM