A Records not being created for client computers or Server on DNS on Server 2012R2 under DNS\Forward Lookup Zone\Domain

Could you validate if Dynamic Updates is configured.  In order for computer records to be created, Dynamic Updates must be set to either Secure or Non-secure.   it is recommended to configure it for Secure option.

make sure your forward lookup zone secure update as well dynamic (non secure) updated enable. Also reverse lookup zone created in dns server.

To enable secure and non secure update refer below link.

In the DNS console, right-click the zone for which you want to configure dynamic update, and then click Properties .
In the Allow dynamic updates Only secure updates .


To configure dns zone refer below link this will help you to configure dns zone .

http://www.ucs.cam.ac.uk/support/windows-support/winsuptech/activedir/dnsconfig

Dynamic Update is configured.

Everything is configured as recommended

Could you kindly run the following command and post the output file:

dcdiag /dnsall > dnsdiag.txt

Directory Server Diagnosis


Performing initial setup:

   Trying to find home server...

   Home Server = SERVER2012

   * Identified AD Forest.
   Done gathering initial info.


Doing initial required tests

   
   Testing server: Default-First-Site-Name\SERVER2012

      Starting test: Connectivity

         The host bd82dde7-85c9-4cd8-ab43-74f005f1194d._msdcs.beefintl.com

         could not be resolved to an IP address. Check the DNS server, DHCP,

         server name, etc.

         Got error while checking LDAP and RPC connectivity. Please check your

         firewall settings.

         ......................... SERVER2012 failed test Connectivity



Doing primary tests

   
   Testing server: Default-First-Site-Name\SERVER2012

      Skipping all tests, because server SERVER2012 is not responding to

      directory service requests.

   
   
   Running partition tests on : ForestDnsZones

      Starting test: CheckSDRefDom

         ......................... ForestDnsZones passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... ForestDnsZones passed test

         CrossRefValidation

   
   Running partition tests on : DomainDnsZones

      Starting test: CheckSDRefDom

         ......................... DomainDnsZones passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... DomainDnsZones passed test

         CrossRefValidation

   
   Running partition tests on : Schema

      Starting test: CheckSDRefDom

         ......................... Schema passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... Schema passed test CrossRefValidation

   
   Running partition tests on : Configuration

      Starting test: CheckSDRefDom

         ......................... Configuration passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... Configuration passed test CrossRefValidation

   
   Running partition tests on : beefintl

      Starting test: CheckSDRefDom

         ......................... beefintl passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... beefintl passed test CrossRefValidation

   
   Running enterprise tests on : beefintl.com

      Starting test: LocatorCheck

         ......................... beefintl.com passed test LocatorCheck

      Starting test: Intersite

         ......................... beefintl.com passed test Intersite

Any further advice on how to possibly fix this?

I would like you to try the following on one of your computers that is joined to the domain for which there is no record on the server:

IPCONFIG /REGISTERDNS

If it fails the please run ipconfig /all and post the output

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Billing2-PC
   Primary Dns Suffix  . . . . . . . : beefintl.com
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : beefintl.com

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : beefintl.com
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Physical Address. . . . . . . . . : A4-1F-72-73-0E-B2
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::7032:20ba:50ab:6690%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 169.254.10.215(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Monday, October 12, 2015 11:32:31 AM
   Lease Expires . . . . . . . . . . : Tuesday, October 20, 2015 11:32:31 AM
   Default Gateway . . . . . . . . . : 169.254.10.190
   DHCP Server . . . . . . . . . . . : 169.254.10.4
   DHCPv6 IAID . . . . . . . . . . . : 245636978
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-9B-23-23-A4-1F-72-73-0E-B2
   DNS Servers . . . . . . . . . . . : 169.254.10.4
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.beefintl.com:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : beefintl.com
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

IPv4 Address. . . . . . . . . . . : 169.254.10.215(Preferred)
Default Gateway . . . . . . . . . : 169.254.10.190
DHCP Server . . . . . . . . . . . : 169.254.10.4
DNS Servers . . . . . . . . . . . : 169.254.10.4

Why are you using addresses in the APIPA address space? That address range is normally reserved for IPv4 auto-configuration by DHCP clients that can't contact a DHCP server.

I am very surprised to see you are using IP 169.254.x.x because that is the IP range Windows computers use if DHCP ser is unavailable.  What is the IP address for SERVER2012?  If it is 169.254.10.4 then there could be an issue.  If you run the following command, do you get the name resolved to IPs:

nslookup beefintl.com

We are using this address range because when we took on this customer, it was the address range being used on their system. They have quite a few pieces of machines and equipment on the network using these addresses, so changing it would be quite a chore.

I ran nslookup beefintl.com on the server and it did resolve to the proper IP. Should I run it on a PC and see what results?

Go ahead and try nslookup from a client machine. I have a hunch it'll work, but I could be wrong.

I don't think I've ever encountered anyone actually using that address range in production, so I don't know how well everything works with it. Basic communication within the network obviously isn't a problem, and the router seems to be OK with it too (which kinda surprises me, I'll admit). It's possible that DNS "knows" not to register addresses in that range, however.

Come to think of it, though, 2003 DCs used to cause problems by registering APIPA addresses for themselves when they had network adapters that were enabled but not connected to a network, so DNS is at least capable of registering addresses in that range...or at least it was back in those days.

I'll have to dig around some more and see what I can come up with.

Ran nslookup from a logged in PC .

nslookup beefintl.com and got:

Server  Unknown
Address 169.254.10.4

Name beefintl.com
Address 169.254.10.4