Remove SRV records using DNSCMD

What is the exact command (with parameters) to remove a SRV record from DNS on a 2003 server using DNSCMD?

I've done a lot of searching for the exact command format (with examples) but I have been unsuccessful.  

Please don't give me links to sites that simply talk about it or that have examples for adding records only.  My search is very specific looking for how to remove SRV records.
Please don't reply unless you know the proper format for sure.  Don't give me strings that you "think" might work. I need what does work.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Here's an example.
dnscmd <srvname> /recorddelete _ldap._tcp.gc SRV 0 100 3268

Open in new window

If you were to look at this record's properties prior to deletion, you would see the following info:
Service:  _ldap
Protocol:  _tcp
Priority:  0
Weight:  100
Port Number:  3268
Host offering this service:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DrDave242Senior Support EngineerCommented:
Footech's syntax is correct. I'm just commenting to add that you don't have to specify every parameter, only as many as you need to uniquely identify the particular record or records you want to delete. To use the example above, if there were only one SRV record named gc in that location, you could leave out everything after "SRV" in the command (the priority, weight, port number and hostname).
jpgillivanConsultantAuthor Commented:
Footech, The command as accepted.  Thanks.  However for some reason the record keeps popping back in to DNS.  The issue here is that someone tried to install a 2012 server as a DC in to a 2003 domain.  The user did not realize this until afterward that 2003 to 2012 is not an upgrade path.  He removed the 2012 server and had issue. He called us and we seized the roles back to the 2003 box.  I am in the process of migrating to 2008 then to 2012/16.  I have manually cleaned up a lot of left over entries from the incorrect server but the SRV records keep coming back and I think that is causing issues as when we unplug the 2003 box, no one can log in to the domain even though the 2008 box is up and (DNS, DHCP and AD running).
SD-WAN: Making It Work for You

As bandwidth requirements and Internet costs grow, businesses naturally want to manage budgets by reducing reliance on their most expensive connection types. Learn more about how to make SD-WAN work for your business in our on-demand webinar!

We can definitely assist with that, I would recommend opening up another question for that.
There is no problem with installing a Server 2012 DC in a domain with Server 2003 DCs.  The domain functional level must be 2003 though.

You'd have to describe exactly what SRV records are involved.  The majority of SRV records are automatically registered by each DC for itself.  The Netlogon service does this at startup and every 60 minutes.  You may want to have a look at the netlogon.dns file for incorrect entries.  If found, you may need to stop the Netlogon service, delete/rename the netlogon.dns and netlogon.dnb files, and start the Netlogon service.

I do recommend opening a new question though so more experts will see the current issue you have, and you can describe more fully.
jpgillivanConsultantAuthor Commented:
Footech, I meant to say that the client tried to install server 2016 DC.
Still not an issue -
If the FFL was at Server 2000 level, the install of a 2016 DC would be blocked.  If it was at Server 2003 level, there would be no issue.  Something else is going on. I stand by my previous recommendations.
jpgillivanConsultantAuthor Commented:
Footech, I have examined the netlogon.dns and there are no records of the removed 2016 server.  Yet, they still remain in DNS.
jpgillivanConsultantAuthor Commented:
I'm marking this as resolved for the question originally asked as the command worked.  There appears to be deeper issues that I have to look in to.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.