long logon times is no dhcp related but usually dns related.
how much ram does your server have?

 

it has 16gb

 

These virtual machines only take a long time if im login into it via the domain

 

Are they pointed at the DC for dns? They should be. They should not be pointed to the internet for dns.

 

have changed the dns to that off the server and still it is taking forever to log in

the dns of my server is the same as its ip address

 

lets see a ipconfig /all from one of the wkstation vms

Have you reviewed the event logs for clues?

 

Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter
Physical Address. . . . . . . . . : 00-15-5D-00-0B-00
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::7989:9253:774f:ccc7%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.12(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 07 February 2013 08:30:04
Lease Expires . . . . . . . . . . : 08 April 2013 08:30:05
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.11
DHCPv6 IAID . . . . . . . . . . . : 234886493
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-98-08-C1-00-15-5D-00-0B-00
DNS Servers . . . . . . . . . . . : 192.168.0.11
NetBIOS over Tcpip. . . . . . . . : Enabled
unnel adapter isatap.JPROD.local:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : JPROD.local
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
unnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

event logs say the following

event id 129
NtpClient was unable to set a domain peer to use as a time source because of discovery error. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: An existing connection was forcibly closed by the remote host. (0x80072746)

event id 5781
Dynamic registration or deletion of one or more DNS records associated with DNS domain 'JPROD.local.' failed. These records are used by other computers to locate this server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition).

event id 6038

Microsoft Windows Server has detected that NTLM authentication is presently being used between clients and this server. This event occurs once per boot of the server on the first time a client uses NTLM with this server.

NTLM is a weaker authentication mechanism. Please check:

Which applications are using NTLM authentication?
Are there configuration issues preventing the use of stronger authentication such as Kerberos authentication?
If NTLM must be supported, is Extended Protection configured?

 

Assuming your domain name is jprod.local from a workstation vm to a nslookup jprod.local. What does it return?

 

I have done a nslook up and it has returned with the name and ip address of my server

 

That certainly is good. How much ram are you allocating to the vms?
If you ping the server vm what is the reponse time?
Have you run dcdiag on the dc? What errors does it present?

 

It may be worth running the DNS bets practices analyzer also to see if any non-compliant issues.