Navigation section

internal domain

About this tag
The internal domain tag covers discussions about managing Windows Server domains where the internal domain name matches a public top-level domain, such as example.com. This configuration can cause DNS resolution conflicts, leading to issues like email delivery failures for POP clients when connected to the internal network or VPN. Users explore solutions like adding subdomains to separate internal and external namespaces, reconfiguring DNS records, and migrating clients. Common themes include Windows Server 2016, DNS troubleshooting, and best practices for avoiding split-brain DNS scenarios.
  1. A

    Server 2016 Help with DNS issue (.com top level domain)

    Im running a windows 2016 domain. top level internal domain is example.com and so is external domain (where website is hosted). this is not a good practice but it is what it is. I could add a sub domain but not sure on how to reconfigure and move all clients. I added a www A record with the...
    • anax
    • Thread
    • client connection dns domain setup email accounts email configuration external domain guidance internal domain local clients mx records network issues pop mail public website reconfiguration record subdomain top level domain troubleshooting vpn windows server 2016
    • Replies: 4
    • Forum: Windows Server Forums
Back
Top