Allowing non-domain members to register in DNS
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.
Any ideas on what may be causing this?
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.
Any ideas on what may be causing this?
ASKER
Yes
ASKER
Well my problem doesn't dissapear per se; I can obviously resolve the servers by name if I put entries in DNS for them but the problem I was trying to solve was auto-registration with DNS
Configure the machine with a primary DNS suffix of your domain.
Accidently submitted..
part2
go to system properties, computer name tab, CHANGE button, MORE button, type your primary DNS suffic (ie yourdomain.local or yourdomain.com), check the box, OK ..ok..ok..ok ...test
part2
go to system properties, computer name tab, CHANGE button, MORE button, type your primary DNS suffic (ie yourdomain.local or yourdomain.com), check the box, OK ..ok..ok..ok ...test
ASKER
Which machine do you mean? The DNS server or the client? Are you saying that I should make the client join the domain? These development servers are purposely not part of the domain.
ASKER
More research.
Adding an etnry to the DNS forward lookup zone e.g. ServerGX28 192.168.1.11 allows the server name to resolve for domain member machines but not for non-domain memeber machines which I guess is part of my problem.
It appears that the DNS server is not allowing non-domain servers to register themselves and it's also not providing proper DNS service for non-somain member computers.
Adding an etnry to the DNS forward lookup zone e.g. ServerGX28 192.168.1.11 allows the server name to resolve for domain member machines but not for non-domain memeber machines which I guess is part of my problem.
It appears that the DNS server is not allowing non-domain servers to register themselves and it's also not providing proper DNS service for non-somain member computers.
See here: http://technet2.microsoft.com/WindowsServer/en/Library/d0e19b57-c368-46c2-b017-caf25ae150ec1033.mspx
If you are stating that the virtual machines also get their IPs from the one DHCP server, then you can set the DHCP server:
To modify this setting, select the Enable DNS dynamic updates according to the settings below check box and click Always dynamically update DNS A and PTR records, which is located in Properties on the DNS tab on the applicable DHCP server or on one of its scopes.
Try that and see what happens.
If you are stating that the virtual machines also get their IPs from the one DHCP server, then you can set the DHCP server:
To modify this setting, select the Enable DNS dynamic updates according to the settings below check box and click Always dynamically update DNS A and PTR records, which is located in Properties on the DNS tab on the applicable DHCP server or on one of its scopes.
Try that and see what happens.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
if you manually enter host records in DNS, does your problem dissapear?
Cheers!