DNS - Create (A) Record

I have a network with over 2000 workstations. My problem involves DNS inside our domain (192.168.xxx.xxx). Something went amiss, so when DHCP assigns an IP, it doesn't always create a Host (A) record. It does create the Pointer record.

I can usually - with a lot of effort - figure out the IP-Hostname connection, then I can resume working on that workstation. After my other work on the workstation is finished, I can open DNS and create the (A) Record ... or not. :confused:

What I need is a way to create the (A) record using a batch file:

C:> createa.bat param1 -- in which param1 is the IP address

The batch file will create the (A) Record and return a commentary on what did or didn't happen.

===========================================================================
Rather than get sidetracked, here's some background.
I don't need to fix what's described below - I only need to create the (A) Record quickly.

• The guy who manages DHCP is trying to figure out what went wrong - and hopefully fix it. I'm not worried about that - it's not my job. Once he fixes that, the problem should stop happening.
• However, I'll still have workstations that have no (A) Record. Eventually that will self-resolve, but making it happen is a logistical nightmare.
• My problem is that I have a huge number of workstations that have no (A) record. If I ping a hostname, or do nslookup, or DNS Forward Lookup on the hostname, the command returns

  Ping request could not find host xxxxx. Please check the name and try again.
  

• That implies that the host doesn't exist. However, usually the host does exist but DNS thinks otherwise.
• If I can figure out the IP and use that IP, then ping, nslookup, DNS Reverse Lookup work as expected. However, it's not always easy to find the IP unless
  • I drive around to 10+ sites, track down the workstation, and run IPconfig /release .... IPconfig /flushDNS .... IPconfig /registerDNS.
    
    **** note: rebooting only works if you first do IPconfig /release .... IPconfig /flushDNS
    or
    
  • I can stay at my desk and hunt through DHCP
• I do most of my work remotely. But if you're using Remote Desktop or a VNC-based connection, as soon as you release the IP, you lose the connection and cannot reestablish the connection, and can no longer reboot remotely. So remotely releasing the IP is a bad idea.
• Once I know the IP-Hostname connection, I can resume working on that workstation. Still, to do the job correctly, I have to open DNS and create the (A) Record.

I only need to create the (A) Record quickly. While I appreciate your efforts to help me correct the underlying problem, don't bother. I can't fix the root problem. I only need to create the (A) Record quickly.
=========================================================================== =