Windows 10: Event ID 504, DNS server could not create zone

​

Some Windows users reported that the DNS server could not create zone %1 from registry data. If you open the Event Viewer, you may see Event ID 504 – DNS server could not create zone. In this post, we will discuss this issue and see how it can be resolved. What is a DNS server […]

This article Event ID 504, DNS server could not create zone first appeared on TheWindowsClub.com.

read more...

 

Setting up a DNS Server on UNIX

installing a dns server is extremely simple, just install it, create zone files. zone files are a bit harder to understand but still easy

 

Error creating DNS records in DNS Zone Scope

I apologize in advance for the long post. I wanted to make sure I added all the information needed to help me troubleshoot this issue.

We are building a POC at AWS. We have a direct VPN tunnel from our on premise network to our VPC.

We are looking to create an instance of our SSO and LDAP in AWS. Reason being so that authentication for any hosted web application will no longer rely on our on premise network. We also need our on premise clients to communicate with the on premise SSO
and LDAP instances while the on premise network is available.

Our supporting Servers and Workspaces in AWS need to speak directly to the SSO and LDAP instance in the cloud (not the on premise instances of SSO and LDAP).

That being said, we built a Standalone Windows Server 2016 running DNS in AWS (DNS01-AWS). This DNS server has all of our forward and reverse zones loaded as Secondary zones (The Primary zones are located on our on premise DDI Device). The plan is to use
Windows DNS Policies (on our DNS Server at AWS) to resolve queries based on Geo-Location. So lets say our AWS subnet is 192.168.0.0/24 and our on prem subnet is 10.10.0.0/24. The dns zone is mycompany.com.

On premise DNS should resolve like this:

sso.mycompany.com - 10.10.5.2

ldap.mycompany.com - 10.10.5.3

At AWS DNS should resolve like this:

sso.mycompany.com - 192.168.5.2

ldap.mycompany.com - 192.168.5.3

***Every other existing DNS record within our forward or reverse zones should resolve normally.

FYI...Externally DNS is hosted and has been adjusted so that sso.mycompany.com resolves to 192.168.5.2

To get this working I issued the following powershell commands on the DNS server at AWS (DNS01-AWS):

Add-DnsServerClientSubnet -Name "AWSSubnets" -IPv4Subnet "192.168.0.0/24" - (Command was successful)

Add-DnsServerClientSubnet -Name "OnPremSubnets" -IPv4Subnet "10.10.0.0/24" - (Command was successful)

Add-DnsServerZoneScope -ZoneName "mycompany.com" -Name "MyCompanyAWS" - (Command was successful)

Add-DnsServerZoneScope -ZoneName "mycompany.com" -Name "MyCompanyOnPrem" - (Command was successful)

Add-DnsServerResourceRecord -ZoneName "mycompany.com" -A -Name "ldap" -IPv4Address "192.168.5.3" -ZoneScope "MyCompanyAWS" - (Command failed with the [INDENTED] message below)

Add-DnsServerResourceRecord : Failed to create resource record ldap in scope MyCompanyAWS of zone mycompany.com on

server DNS01-AWS.

At line:1 char:1

+ Add-DnsServerResourceRecord -A -ZoneName mycompany.com -Name ldap -I ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : InvalidArgument: (ldap:root/Microsoft/...rResourceRecord) [Add-DnsServerResourceRecord]

, CimException

+ FullyQualifiedErrorId : WIN32 9611,Add-DnsServerResourceRecord

I tried adding the "-Computername" paramter to the command, but that didn't help. I tried removing all the double quotes (I saw someone issue this command without double quotes), but that didn't help. The "-Verbose" option doesn't give me any more information.

Any help is appreciated.

 

DNS Servers

I run a DNS server locally, so when a domain is already cached, I get it back almost instantly, otherwise it responds as fast as the first server in my list (75.75.75.75 in my case.)