VMware on AD server created strange DNS entries 1

[zaccaz]

hi there, w2k3sp2 std server with fix ipaddr 192.168.222.1, after installed vmware server 1.0.4 on it, it automatically created vmnet1 & vmnet8 with ipaddr 192.168.249.1 & 192.168.241.1

as that w2k3sp2 server is active directory server as well, now in dns this server got 3 entries: 192.168.222.1, 192.168.249.1, 192.168.241.1

somehow for the rest of the windows clients in subnet 192.168.222.0, they will 1st resolved the server as 192.168.249.1 which is unreachable....

i tried to manually delete 192.168.249.1 & 192.168.241.1 in dns server, but after a while both came back again

q1. wondering if it's possible to prevent those vmnet1 & vmnet8 ipaddr being loaded into dns server?

q2. if q1 is not possible, other than manually fixing the hosts file on windows clients, any tricks to force all clients resolve that w2k3sp2 server as 192.168.222.1?

million thanks in advance!

 

[IRudebwoy]

FYI, I would never install VMware or any large, potentially CPU intensive, package on my AD server. It's resources are precious and need to be treated as such.

With that said, I would change the VMware configuration to delete the vmnet1 & vmnet8 interfaces and just use the bridge interface which doesn't require an IP address.

 

[zaccaz]

i c, many thx!