Creating parent reverse lookup zone when child zones already exist — what happens?
We have an AD-integrated DNS environment that has accumulated a large number of reverse lookup zones over time, created without any parent zone — essentially DNS sprawl from years of admins creating individual subnet zones rather than working from a parent. We currently have approximately 80+ reverse lookup zones including: Dozens of x.10.in-addr.arpa zones covering various 10.x.x.x subnets Multiple x.172.in-addr.arpa zones A handful of others including 100.192.10.in-addr.arpa, 168.192.in-addr.arpa, 204.167.in-addr.arpa, 215.204.167.in-addr.arpa, 135.7.in-addr.arpa None of these were ever delegated from a parent zone — they were just created independently. The 10.in-addr.arpa zone does not exist. Domain controllers are a mix of Windows Server 2019 Standard (majority) and Windows Server 2025 Standard. Our goal is to create 10.in-addr.arpa as the consolidation point going forward — new registrations go there, and we migrate existing child zones into it one at a time, deleting old ones as we go at a pace we're comfortable with. Before touching anything, we need to understand what creating 10.in-addr.arpa will actually do to the existing child zones. Specifically: Will existing records in the child zones be deleted? We've seen the TechNet article documenting records vanishing when creating a child zone under an existing parent — does the same destructive behaviour occur in the reverse direction? Will auto-delegations be created in the new parent zone pointing to the existing child zones, and if so how quickly? Will the child zones continue to function normally for queries while the parent exists alongside them? Will dynamic registration start hitting the parent zone for subnets not covered by an existing child zone, or will something unexpected happen? We can't test this in a lab as we don't have a replica environment available, and can't risk touching production without understanding the behaviour first. Pointers to any documentation covering this specific scenario would also be appreciated — we've been unable to find anything that addresses creating the parent after the children already exist independently.Lots of DNS Server events 5504 on AD DNS server from Cloudflare etc
Hi! I'm getting about 18 events with id 5504 while trying to resolve some DNS names, like fullfiles.xyz. The DNS server is configured to use provider DNS and root hints. I can suppress these messages by disabling root hints or by disabling EDNS0 with dnscmd /config /enablednsprobes 0. I tried to use packet capture on the DC and on the router, and analyzed the results with AI, which answered: "You receive malformed patterns on the WAN interface." Can anybody explain the cause of this problem? Any ideas to fix it? Thanks!
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!
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
DNS Issue - nslookup resolve to random localhost ip
Hello all, I am new here. hope there is someone will help me. Please help me to resolve this issue. the host domain upxxxxx.edu.my can be resolve using public DNS. but while using internal DNS it will resolve to random localhost IP. i had restart the DNS/AD server. i made nslookup again after reboot then it appear 127.118.0.45 (other local IP address). *this is new fresh install windows server 2022 std with AD, DHCP and DNS roles. thank you for your help. i am very appreciate the effort.Strange DNS problem on Server 2022
I installed a new Server 2022 DC on my network as the only DC. It serves DNS for our network and for a few weeks all has been working fine. However, lately I have been having a problem using Outlook to access my secondary email address at comcast.net. For long periods the attempt to download email fails. I did some checking and found that when I do a nslookup on imap.comcast.net I get this: Non-authoritative answer: Name: imap.comcast.net (note, there are no IP addresses) If I do the same but specify Google's DNS server (8.8.8.8) I get: Non-authoritative answer: Name: imap.ge.xfinity.com Addresses: 2001:558:fc0a:3:f816:3eff:fea5:2243 2001:558:fc0a:3:f816:3eff:fe95:679f 2001:558:fc0a:3:f816:3eff:fe0c:7c51 2001:558:fc0a:3:f816:3eff:fe51:b939 2001:558:fc0a:3:f816:3eff:fee8:1979 2001:558:fc0a:3:f816:3eff:fe6b:52a6 2001:558:fc0a:3:f816:3eff:fe5d:49ac 2001:558:fc0a:3:f816:3eff:fe84:7ff1 2001:558:fc0a:3:f816:3eff:fef5:7c75 2001:558:fc0a:3:f816:3eff:fe8d:2a36 2001:558:fc0a:3:f816:3eff:fe57:df5e 2001:558:fc11:9:f816:3eff:fee9:ffd6 2001:558:fc11:9:f816:3eff:fedd:4bc5 2001:558:fc11:9:f816:3eff:fe40:d128 2001:558:fc11:9:f816:3eff:fec1:ef59 2001:558:fc11:9:f816:3eff:fe48:d86d 96.118.18.255 96.118.18.251 96.118.18.249 96.118.18.240 96.118.18.254 96.118.17.101 96.118.17.82 96.118.18.242 96.118.19.1 96.118.19.5 96.118.18.230 96.118.17.194 96.118.18.11 96.118.19.0 96.116.224.191 96.116.224.174 Aliases: imap.comcast.netdns sortorder bug introduced over 10 years ago
As of Windows server 2012 there was a sort order bug introduced in the dns manager. All info is treated as a tekst string eventhough they are not. Therefore ip numbers are sorted wrong, dates are sorted wrong and managing the dns sometimes becomes a nightmare when sorting is needed. The solution is so simple, sort the original numbers, an ipnumer is a 32bit number. A timestamp is a number respresenting seconds after a start time. Please fix this so 2 comes after 1 and not after 19 or 199, etc. 1 January2024 does NOT follow 1 Jan 2024, there is a whole year of 364 other days in between. Neither does ip number 11.2.3.4. follow 1.2.3.4, nor does 111.2.3.4 😞 I and others have started reporting this bug as soon as it appeared but everytime we got answers like export to Excel (does not help) and other non answers. How hard is it to fix this? Today I need to delete some old dns records that were not properly scavaged. I CANNOT sort on timestamp to get all old records together. 😞
