I have an AD Domain controller that runs as the DNS server for the domain. There is a separate (non-Windows) DHCP server that issues the IP addresses for the sub-net and the DHCP server is set to point to the DC as being the primary DNS server so all clients point to and use my main DNS server. The DNS server forwards requests it can't resolve to the WAN gateway. All works fine as long as the client or server is a member of the domain.
I have 2 sandbox servers that are not domain members; their main use is to run Virtual Server 2005 images and each image requests and gets an IP address from the same DHCP server. These machines can all access the internet via the DNS server's name resolution but they can't resolve each other's names.
I think that my problem is that these non-domain member machines do not get their IP addresses registered in the DNS server.
I tried changing the security setting for the DNS server but it still doesn't seem to register the non-domain member IP addresses.
by Batuhan Cetin
Within the dynamic life of an IT administrator, we hold many information in our minds like user names, passwords, IDs, phone numbers, incomes, service tags, bills and the order from our wives to buy milk when coming back to home.…
Setting up a Microsoft WSUS update system is free relatively speaking if you have hard disk space and processor capacity.
However, WSUS can be a blessing and a curse. For example, there is nothing worse than approving updates and they just have…
This Micro Tutorial will teach you how to add a cinematic look to any film or video out there. There are very few simple steps that you will follow to do so.
This will be demonstrated using Adobe Premiere Pro CS6.
When cloud platforms entered the scene, users and companies jumped on board to take advantage of the many benefits, like the ability to work and connect with company information from various locations. What many didn't foresee was the increased risk…