Thanks for the replies.
I have tried ipconfig /flushdns on the server ESET is installed and ran nslookup from that same server to the machine name which returns the correct IP address (192.168.6.167) which is what running ipconfig /all shows me too so i know its the correct IP.
IP address in ERA is 192.168.6.182 for the machine, which is incorrect.
I have removed the computer from our domain entirely, removed any records from DHCP and DNS and can see that after adding the machine back to the domain it picks up the correct IP in DHCP and DNS records - i am almost convinced its the ERA that is at fault.
If i were to run the custom IP search and push install from there, would it fix the DNS and IP discrepancy?
Thanks,
Ash