Fix DNS_ERROR_INVALID_PROPERTY (0X00002551)

What's this error and when does it hit?

You're trying to add or edit a DNS record—maybe an A record or a CNAME—and you open its properties window. You click OK or Apply, and bam: DNS_ERROR_INVALID_PROPERTY (0X00002551). The error means Windows found a property in the record that doesn't belong there. Think of it like trying to put a square peg in a round hole—the DNS database knows that property isn't valid for that record type.

This usually happens when you copy a record from another zone and paste it in, but the copied record carries over a property that doesn't match the new zone's schema. Or you've used a script to bulk-create records and accidentally set a field that shouldn't be there. I've seen it most often on Windows Server 2016 and 2019 DNS consoles.

Don't panic. We'll fix it in layers. Start with the simplest fix—it takes 30 seconds. If that doesn't work, move to the next. No need to do all three unless you have to.

1. The 30-Second Fix: Refresh and retry

Sometimes the DNS console just glitches. Old data hangs around in the cache. I've seen this a hundred times.

1. Open your DNS Manager (from Server Manager or run dnsmgmt.msc).
2. Right-click the zone where the error happened (like example.com).
3. Click Refresh. The list should reload. You'll see the records flicker and update.
4. Now try adding or editing the record again. Right-click in the zone, choose New Host (A or AAAA) or whatever record type you need.
5. Type the details manually—don't paste from a different zone or file. I recommend typing it fresh. After you click OK, you should see the record appear in the list without any error.

Still getting the error? Move to the next fix.

2. The 5-Minute Fix: Delete and recreate the record

The record itself might be corrupted. One bad property got stuck in it. Deleting and recreating it from scratch usually wipes that out.

1. In DNS Manager, find the record that's throwing the error. It's the one you were editing when the error popped up.
2. Right-click it and select Delete. A warning box will ask if you're sure. Click Yes. The record vanishes from the list.
3. Now recreate it. Right-click the zone, choose New Host (A) (or the correct record type for your needs). Enter the name and IP address exactly as they were before.
4. Click OK. After a second, the record should show up in the list. Right-click it and select Properties. Check the General tab—is the Time to live (TTL) set to something reasonable like 1 hour? If it's blank or shows 0, that's the problem. Set it to 3600 (1 hour) and click OK.

If the error shows up again when you try to create the new record, the zone itself might have a corruption. Let's try the advanced fix.

3. The 15+ Minute Fix: Reset the DNS cache and check for schema issues

This one gets into the guts. The zone's schema (the rules for what properties can exist) might be out of sync. Or the DNS server's cache is holding onto a bad piece of data.

Step 1: Clear the DNS server cache

Open an elevated Command Prompt (right-click Command Prompt and choose Run as administrator).

ipconfig /flushdns

You should see: Successfully flushed the DNS Resolver Cache.

Then clear the server-side cache:

dnscmd /clearcache

If that command isn't recognized, you need to install the DNS Server Tools. But most Windows Server installs have them. You'll see Command completed successfully.

Step 2: Check for duplicate records or schema mismatches

Sometimes the zone has a record that uses a property that was valid in an older version of Windows DNS but not in the current one. For example, if you upgraded from Server 2008 to 2016, some records might have leftover fields.

Export the zone to a text file:

dnscmd . /ZoneExport example.com /ZoneFile example.com.dns

Replace example.com with your actual zone name. This creates a file in C:\Windows\System32\dns\ named example.com.dns.

Open that file in Notepad. Look for lines that have strange properties like DnsServerExtensionFlags or WINS or ScavengeServers attached to an A record. Those shouldn't be there. A normal A record looks like:

hostname        A       192.168.1.10

If you see extra stuff after the IP, that's the problem. Delete the entire line for that record. Save the file.

Now reload the zone with that cleaned file:

dnscmd . /ZoneResetMasters example.com /LocalFile example.com.dns

After you run it, you should see Zone reset masters completed successfully.

Then restart the DNS service to make sure everything takes:

net stop dns && net start dns

Wait about 10 seconds. Then open DNS Manager again. Try adding your record now. It should work without the error.

One last thing: If you still see the error, the issue might be with a specific client machine that has a bad DNS registration. Check the Event Viewer under Windows Logs > System and look for events with source DNS and ID 2 or 4. Those often tell you which hostname is causing the property conflict.