Windows Server 2019 AD & DNS replication
Hello, I'm running into issues with AD & DNS replication on a recently joined server in our environment. Environment: Three writable DCs in separate sites: Server A (Site A) – Windows Server 2019, AD DS & DNS (healthy) Server B (Site B) – Windows Server 2019, AD DS & DNS (healthy) Server C (Site B, new) – Windows Server 2019, AD DS & DNS (failing) Issues Observed Inbound replication to Server C from Server A & Server B successfully propagates for both AD and DNS zone/record changes. Outbound replication from Server C to Server A & Server B fails for both AD and DNS zone/record changes. Server A logs Event ID 1311 (KCC). Server A & B logs Event ID 1925 when trying to establish the link to Server C. What I’ve Tried: Pointed each servers NIC's to a heathy DC with the correct suffix. I've checked any windows FW and network FW rules to make sure no blockages. Verified A+SRV records for both heathy DC's. Confirmed AD-Integrated zones on all 3 servers show correct ACLs and records. I've tried running repadmin → still errors. Tested RPC connectivity: TCP 135 open. Ensured subnets/site mappings are correct in Sites and Services. I've tried to seed a zone and record on the healthy servers in efforts of t/s. Any help would be greatly appreciated!
Announcing Public Preview of Zero Trust DNS
In today's evolving cybersecurity landscape, traditional perimeter defenses are no longer sufficient . As organizations embrace the Zero Trust security model, ensuring that devices only communicate with trusted network destinations becomes paramount. We are excited to announce the public preview of Zero Trust DNS (ZTDNS), a new feature in Windows 11 Insider builds designed to enforce domain-name-based network access controls, enhancing your organization's security posture. ZTDNS empowers enterprise IT administrators to natively apply outbound domain-name-based network access controls on Windows 11 endpoints. This helps prevent access to untrusted destinations, reducing the risk of a slew of network attacks from malware communication to data exfiltration. What is Zero Trust DNS? ZTDNS integrates the Windows DNS client with trusted Protective DNS (PDNS) servers to control outbound IP traffic based on domain names. When ZTDNS is configured on a Windows 11 device to use PDNS servers that support DNS over HTTPS (DoH) or DNS over TLS (DoT), ZTDNS ensures that: The Windows DNS client forces the use of encrypted DNS and queries are only sent to the configured PDNS servers. Outbound traffic is permitted only to IP addresses resolved by these trusted PDNS servers or to IP ranges with a manual exception plumbed by the IT administrator. All other IPv4 and IPv6 outbound traffic is blocked by default, adhering to the "deny by default" principle of Zero Trust. A log of attempted outbound connections is maintained on the device. This approach reduces the need for deep packet inspection or reliance on insecure signals like plain-text DNS or Server Name Indication (SNI) when attempting to determine the domain name associated with outbound traffic. This makes ZTDNS an important tool in the Zero Trust toolbelt since DNS traffic and SNI are increasingly being encrypted. It also aligns with Zero Trust principles by assuming all destinations are untrusted by default, only allowing connections to destinations explicitly permitted through DNS resolutions provided by trusted PDNS servers. For more information, visit our previous blog post on design of ZTDNS. Threats Zero Trust DNS Helps Mitigate Implementing ZTDNS can bolster your defenses against various network-based threats, including: DNS Hijacking: By ensuring that only DNS resolutions from trusted PDNS servers are used, ZTDNS helps prevent attackers from redirecting traffic to malicious sites. Malicious Communications: Blocking outbound connections to IP addresses not resolved through trusted DNS queries helps disrupt phishing and even non-administrative malware stagers and beacons. Data Exfiltration: Restricting outbound traffic to approved domains reduces the risk of sensitive data being transmitted to unauthorized destinations without conducting analysis of domain name resolution patterns. Getting Started with Zero Trust DNS To enable ZTDNS in your environment: Get a supported Windows 11 build Enroll your device in the Windows Insider Program (Canary channel) and update to build 27766+. Unlock ZTDNS In an administrator command prompt, run: reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters" /v Experiment4712 /d 0xbe8261eb /t REG_DWORD Reboot the device. Ensure all applications and services are configured to use the Windows DNS client Configure applications like Edge and Chrome to use the Windows DNS client instead of their custom client (disable BuiltInDnsClientEnabled policy). Add manual allow exceptions Teleconferencing applications like Teams use WebRTC which negotiates IP addresses for peers within a TLS tunnel and has no DNS visibility. These IP subnets are also publicly documented and need manual allow exceptions for the application to work with ZTDNS. Add manual allow exceptions for IP addresses that are necessary for your productivity applications/services but are not discovered through DNS. Here is a sample command, for manual allow exception, which needs to run in administrator command prompt: netsh ztdns add exception name=AppName description="Description of AppName" subnets=192.0.2.128/25,198.51.100.0/24,3fff::/48, 3fff:123::/38 Here is a link Microsoft 365 services that may need manual allow exceptions. Set your trusted Protective DNS server (needs to be DoH/ DoT capable) In an administrator command prompt, replace example data in following sample commands with information about your desired DNS server before running: netsh ztdns add server type=doh address=203.0.113.0 template=https://doh.resolver.example/dns-query netsh ztdns add server type=dot address=2001:db8::1 hostname=dot.resolver.example Enable ZTDNS ZTDNS can be enabled using Audit mode or Enforcement mode. Audit mode logs all expected ZTDNS behavior without the actual enforcement. Check out the next blog post for finding and comprehending ZTDNS logs. Enabling ZTDNS in audit mode is recommended before moving on to Enforcement mode. In an administrator command prompt, run: netsh ztdns set state enable=yes audit=yes Enforcement mode blocks untrusted traffic. In an administrator command prompt, run: netsh ztdns set state enable=yes audit=no Now you should have ZTDNS running! In a rare situation where you experience unexpected connectivity issues for some application, please restart the application. If the issue persists, please reboot the device. Disable ZTDNS ZTDNS is a powerful lockdown feature. In case you lose network connectivity due to misconfiguration, you can disable ZTDNS to restore your network connectivity. In an administrator command prompt, run: netsh ztdns set state enable=no audit=no Note: ZTDNS is currently in Public Preview and is intended for evaluation and feedback only. Do not deploy in production environments. Breaking changes may occur before General Availability (GA). Check out the next blog post Troubleshooting Zero Trust DNS for information on ZTDNS logs, sharing feedback and bug reports with the team. Join Me at RSAC 2025 I am excited to share that I will be attending the RSA Conference 2025! If you are planning to be there, stop by Microsoft booth N-5744 or Microsoft Security Hub and ask for Aditi Patange to discuss how ZTDNS can enhance your organization's security posture. Securing the Present, Innovating for the Future Security is a shared responsibility. Through collaboration across hardware and software ecosystems, we can build more resilient systems secure by design and by default, from Windows to the cloud, enabling trust at every layer of the digital experience. The updated Windows Security book is available to help you understand how to stay secure with Windows. Learn more about Windows 11 and Copilot+ PCs. To learn more about Microsoft Security solutions, visit our website. Bookmark the Security blog to keep up with our expert coverage on security matters. Also, follow us on LinkedIn (Microsoft Security) and X (@MSFTSecurity) for the latest news and updates on cybersecurity.DNS lookup performance
Hello all I've got this to do what I want but thought I'd run it past people who know more than me in the hope someone would be kind enough to advise on the following. The intention is to run this every few minutes using task scheduler, I'll push to one or more machines with an RMM. Questions. Is this an efficient an accurate way to do this? Are there any improvements anyone wants to suggest for the code Am I re-inventing a wheel that I can get somewhere for free or low cost? I'm waiting for the new version of GRC's DNS testing tool so this is a stopgap unless it works well enough. TIA # Define an array to store the DNS Servers to be queried with thier FQDN and IP address $dnsServers = @() # Add 5 hosts with their FQDN and IP addresses $dnsServers += [PSCustomObject]@{ FQDN = "OurDNS1"; IPAddress = "14.15.16.17" } $dnsServers += [PSCustomObject]@{ FQDN = "OurDNS2"; IPAddress = "11.12.13.14" } $dnsServers += [PSCustomObject]@{ FQDN = "Cloudflare"; IPAddress = "1.1.1.1" } $dnsServers += [PSCustomObject]@{ FQDN = "Quad9"; IPAddress = "9.9.9.9" } $dnsServers += [PSCustomObject]@{ FQDN = "Google"; IPAddress = "8.8.8.4" } # Define an array to store target FQDNs $targetFqdns = @( "bbc.co.uk", "www.porsche.com", "www.amazon.co.uk" ) # Get the current date in yyyy-MM-dd format $currentDate = Get-Date -Format "yyyy-MM-dd" # Define the path to the CSV file with the current date in the filename $filePath = "$PSScriptRoot\DNSResults_$currentDate.csv" # Initialize the CSV file with headers if it doesn't exist if (-not (Test-Path $filePath)) { "Timestamp,Milliseconds,TargetURL,DNSServerIP,DNSServer" | Out-File -FilePath $filePath } # Loop through each target host and then each DNS server foreach ($targetFqdn in $targetFqdns) { foreach ($dnsServer in $dnsServers) { # Measure the time taken to run the command $measure = Measure-Command -Expression { nslookup $targetFqdn $dnsServer > $null 2>&1 } # Get the current date and time in ISO 8601 format $timestamp = Get-Date -Format "yyyy-MM-ddTHH:mm:ss" # Get the total milliseconds and round up to a whole number $milliseconds = [math]::Ceiling($measure.TotalMilliseconds) # Append the timestamp, milliseconds, domain, server, and name to the CSV file $result = "$timestamp,$milliseconds,$targetFqdn," $dnsServerUSed = "$($dnsServer.IPAddress),$($dnsServer.FQDN)" $output = $result + $dnsServerUsed $output | Out-File -FilePath $filePath -Append } }
DNS proxy for splunk cloud net rule still denied
I have set up my azure FW for DNS proxy and changed the v-nets dns to the private IP of the FW. I have the firewall pointing to custom dns servers. I created a FW rule to allow port 9997 to our splunk cloud instance from any IP. clients are still denied On a VM I can verify its using the FW IP, and I see dns queries in the logs. I'm not sure what I'm missing.Troubleshooting Zero Trust DNS
By adopting Zero Trust DNS (ZTDNS), organizations can strengthen their Zero Trust deployments, ensuring that Windows 11 devices only communicate with trusted network destinations. This blog post will help ZTDNS Public Preview selfhosters retrieve and update ZTDNS configuration, find ZTDNS logs, debug ZTDNS, share feedback, and report bugs to the team. Some known issues are also listed. Retrieving ZTDNS configuration You can find information on the commands to retrieve trusted server information, manually allowed exceptions, state of ZTDNS, and more by running the following in command prompt: netsh ztdns show help Updating ZTDNS configuration You can add new exceptions or servers while ZTDNS is running on your device using the same commands from ZTDNS deployment process. You can run the following in command prompt to get more information: netsh ztdns add help You can find information on the commands to delete certain configurations like trusted servers, manually allowed exceptions, and more by running the following in command prompt: netsh ztdns delete help Finding ZTDNS logs When you have ZTDNS running your device, you can check Event Viewer to see logs for all attempted connections from the device. Search for ‘Event Viewer’ in Start menu and open it. In the left panel, go under ‘Applications and Service Logs’ -> ‘Microsoft’ -> ‘Windows’ -> ‘ZTDNS’. You should see three logs under this folder: BlockedConnections – contains logs about connections blocked by ZTDNS. Each blocked connection log contains information about the time of the blocked connection, source IP address, source port, destination IP address, destination port, and name of initiating process. Operational – contains logs about ZTDNS configuration and service state changes. PermittedConnections – contains logs about connections allowed by ZTDNS. Each permitted connection log contains information about the time of the permitted connection, source IP address, source port, destination IP address, destination port, and name of initiating process. (Note: this log is disabled by default and can be enabled by right clicking on ‘PermittedConnections’ in the left panel and selecting ‘Enable Log’.) Debugging ZTDNS If you experience connectivity issues after enabling ZTDNS, verify that ZTDNS has at least one trusted DNS server set. To see all trusted DNS servers set for ZTDNS, run the following in command prompt: netsh ztdns show server Check connectivity to the trusted DNS server using ping and try resolving an allowed domain name using the trusted DNS server with Resolve-DnsName. After this, ping to the resolved IP address should succeed. Alternatively, you can ping an allowed domain name directly which should use the Windows DNS client and trusted DNS server for name resolution. This will check connectivity to the trusted DNS server as well as the resolved endpoint. If your issue still persists, please file a bug. You can restore network connectivity by disabling ZTDNS. In an administrator command prompt, run: netsh ztdns set state enable=no audit=no Reporting feedback and bugs We value your feedback! Your feedback from testing ZTDNS in preview is crucial for us as we get ready for GA. To share your feedback or report a bug: Search for ‘Feedback Hub’ in Start Menu and open it. In the left panel, click ‘Feedback’. Click ‘+ Give new feedback’ button to enter new feedback or upvote an existing entry that matches your feedback. In section 1. ‘Summarize your feedback’ text box, enter ‘[ZTDNS]’ and then your feedback. In section 2. ‘Choose a category’, select ‘Problem’ if you want to report a bug and ‘Suggestion’ if you want to give feedback. For the left dropdown box, choose ‘Network and Internet’ and for the right dropdown box, choose ‘DNS’. Fill out Section 3. and 4. Click ‘Submit’. Known issues Chromium-based WebView2 applications (including new Outlook and Teams) use their own encrypted DNS clients instead of using the Windows DNS client. On a Windows 11 device with ZTDNS enabled, based on the DNS server being contacted by the WebView2 DNS client, these applications will fail to send traffic to any resolved IP addresses. We are actively working to solve this for all applications using Chromium under the hood, including our own. You can track the linked Chromium issue for the latest updates.BPA Errors: DNS can't resolve GC, Kerberos, PDC Resource Record, etc.
Hello, I've been poking around this for hours now and could use another set of eyes. This server has been the PDC for quite some time but I discovered the last people that managed this place, didn't demote the old 2008R2 server (thankfully it still existed virtualized). So I was able to do a graceful demotion of that and removed it from the domain. I'm now trying to resolve some other errors in that come up in the BPA scan... All reference DNS and I just can't figure this out. I've been beating head against the wall trying to understand what's happening, This is MS Server Standard 2022 only 1 DC and DNS. (yeah I know, don't get me started, but it's a really small office)... Would love some suggestions. Thanks!DNS record auto registered even the auto registration option was unchecked
Hello guys, I have an DC which have two NICs, A for Domain service and B for camera server. I don't want the IP address of NIC B registered in our DNS, so I uncheck the auto register option in the advance setting of NIC B. However, the IP address of it still keep registering t our DNS even I have manually deleted that option. I have checked the steps in the official article and it doesn't help. https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/unwanted-nic-registered-dns-mulithomed-dc Any suggestion is much appreciated.Windows DNS server crash?
Our DNS servers crashed and took our network down. I rebooted them and its back but I foud the below error I have never seen before. Can't find anything in any log but this and its never happened before. Is thewre any way to tell what caused this? Event ID 906 lsass (796,G,0) A significant portion of the database buffer cache has been written out to the system paging file. This may result in severe performance degradation. See help link for complete details of possible causes. Previous cache residency state: 64% (23809 out of 37063 buffers) (72 seconds ago) Current cache residency state: 15% (4338 out of 28472 buffers) Current cache size vs. target: 99% (214.508 / 214.711 MBs) Physical Memory / RAM size: 8191.023 MBs
