DNS in Windows server

Jonas Boman 0 Reputation points
2023-06-01T13:51:54.6433333+00:00

I have a internal domain, name.se with both internal machines and external machines. I want to only manage internal machines with the internal dns. example I want to reach external.name.se and this records is not available on the internal dnsserver then I want the server to recognise that and think OK I do not have this record so I send it to google NS.

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,127 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Dave Patrick 426.1K Reputation points MVP
    2023-06-02T01:16:25.75+00:00

    Something here could help.

    https://learn.microsoft.com/en-us/windows-server/networking/dns/deploy/split-brain-dns-deployment

    --please don't forget to upvote and Accept as answer if the reply is helpful--

  2. Hania Lian 7,786 Reputation points Microsoft Vendor
    2024-01-29T07:49:41.5033333+00:00

    Hello, Thank you for posting in Q&A forum. According to your description, you can set up a split-brain DNS configuration. This configuration allows you to use the same domain name for both internal and external resources, while managing them separately. To achieve the requirement, you can do as followings:

    1. Create the Zone Scopes: You can use the following example command to partition the zone scope contoso.com to create an internal zone scope. The internal zone scope will be used to keep the internal version of www.career.contoso.com. Add-DnsServerZoneScope -ZoneName "contoso.com" -Name "internal"
    2. Add Records to the Zone Scopes: add the records representing the Web server host into the two zone scopes - internal and default (for external clients). Add-DnsServerResourceRecord -ZoneName "contoso.com" -A -Name www.career -IPv4Address "65.55.39.10" Add-DnsServerResourceRecord -ZoneName "contoso.com" -A -Name www.career -IPv4Address "10.0.0.39” -ZoneScope "internal" Note that No –ZoneScope parameter is provided in the above example commands when the record is being added to the default zone scope. This is similar to adding records to a vanilla zone.
    3. Create the DNS Policies: In the following example command, 10.0.0.56 is the IP address on the private network interface. Add-DnsServerQueryResolutionPolicy -Name "SplitBrainZonePolicy" -Action ALLOW -ServerInterface "eq,10.0.0.56" -ZoneScope "internal,1" -ZoneName contoso.com REF: https://learn.microsoft.com/en-us/windows-server/networking/dns/deploy/split-brain-dns-deployment Best Regards,
      Hania Lian ============================================ If the Answer is helpful, please click "Accept Answer" and upvote it.
    0 comments