capr Posted June 2, 2012 Share Posted June 2, 2012 Hi all, I am new at this and am just playing around till I get it.... I have a domain controller that is also the DNS server. I recently decided to use it as the DHCP server but am having trouble configuring things. When I installed hte DHCP roll, I chose the default 127.0.0.1 as the DNS server address (this may be the problem, DNS server was the server ip address before I played around) I added the DNS server to all my client computers but they won't pickup the right DHCP server which should be 192.168.1.10(win2k8 server) instead of 192.168.1.1 (which is the router). I don't want to make any changes on the router. What am I missing? I am sure it's just the order that things were done but can't figure it out now. none of the clients have internet access with this DNS server right now My router is issuing DHCP as well as the server. Because the router is first, it looks like that take precedence and then the server can't do anything about it. I can't turn off DCHP on the router since this server is only a virtual server that I play around on. Link to comment https://www.neowin.net/forum/topic/1081351-clients-looking-at-the-wrong-dhcp-server/ Share on other sites More sharing options...
sc302 Veteran Posted June 2, 2012 Veteran Share Posted June 2, 2012 DNS needs to be the server ip. You need to disable dhcp on the router. In an active directory network, only active directory servers can be dns servers for pc's on the network. All dns requests, even Internet, will be handled by the active directory servers. There can only be 1 dhcp server on the network. 2 screws it up, and in many cases the windows server will see another one on the network and will not fully come online. Nick H. 1 Share Link to comment https://www.neowin.net/forum/topic/1081351-clients-looking-at-the-wrong-dhcp-server/#findComment-594904263 Share on other sites More sharing options...
+BudMan MVC Posted June 2, 2012 MVC Share Posted June 2, 2012 "only active directory servers can be dns" Not actually true the way its worded ;) Yes all members of the AD need to point to DNS that has the AD information. Does not actually mean they have to be a directory server. Bind can be used for DNS for your AD, if you want too.. http://technet.microsoft.com/en-us/library/dd316373.aspx Configuring Berkeley Internet Name Domain (BIND) to Support Active Directory Link to comment https://www.neowin.net/forum/topic/1081351-clients-looking-at-the-wrong-dhcp-server/#findComment-594904281 Share on other sites More sharing options...
Choto Cheeta Posted June 2, 2012 Share Posted June 2, 2012 I think the Router DHCP is in need to turned off to allow Windows DHCP to take effect.. Link to comment https://www.neowin.net/forum/topic/1081351-clients-looking-at-the-wrong-dhcp-server/#findComment-594904283 Share on other sites More sharing options...
sc302 Veteran Posted June 2, 2012 Veteran Share Posted June 2, 2012 On 02/06/2012 at 06:52, BudMan said: "only active directory servers can be dns" Not actually true the way its worded ;) Yes all members of the AD need to point to DNS that has the AD information. Does not actually mean they have to be a directory server. Bind can be used for DNS for your AD, if you want too.. http://technet.microsoft.com/en-us/library/dd316373.aspx Configuring Berkeley Internet Name Domain (BIND) to Support Active Directory This is true, but let's keep things simple for him. He put two dhcp servers on the same network for goodness sake. He also doesn't understand what 127.0.0.1 is. The way I am reading his post he put that in the Dns servers in the dhcp scope....well of course he isn't getting squat. Link to comment https://www.neowin.net/forum/topic/1081351-clients-looking-at-the-wrong-dhcp-server/#findComment-594904287 Share on other sites More sharing options...
capr Posted June 2, 2012 Author Share Posted June 2, 2012 On 02/06/2012 at 06:56, sc302 said: This is true, but let's keep things simple for him. He put two dhcp servers on the same network for goodness sake. He also doesn't understand what 127.0.0.1 is. The way I am reading his post he put that in the Dns servers in the dhcp scope....well of course he isn't getting squat. Thanks for trying to simplify things. My dhcp scope is 192.168.1.10/200 and yeah I don't know what this 127.0.0.1 is.... My VMs are currently using bridged network devices so I think I need to use the "internal network" option if I am going to have the server be the DHCP server. Will I run into much trouble if I am using multiple network cards on the server? One will be bridged to the router and use the 192.168.1.10 address while the other one will be internal for all the VMs and can use 10.0.0.1. Will this work? Am I explaining myself correctly? Link to comment https://www.neowin.net/forum/topic/1081351-clients-looking-at-the-wrong-dhcp-server/#findComment-594904369 Share on other sites More sharing options...
+BudMan MVC Posted June 2, 2012 MVC Share Posted June 2, 2012 No you want them to use bridged if you want them to talk with your physical network and act as dhs and dhcp, etc. Internal is going to be natted to your physical network.. Not really something you want to do if your wanting to use vms just like they were physical machines on your normal network, etc. 127.0.0.1 means loopback, the local machine! So if you via dhcp tell the clients of that dchp server that their dns is 127.0.0.1 they would just ask their loopback interface.. Ie they would be asking themselves for dns.. Are they running dns -- so no that is never going to work. DNS needs to be the actual address 192.168.1.x of the box running dns. btw sc302, you know I was just giving you a bit of ****! ;) You completely answered the OP question -- so I was just looking for something to talk about. Link to comment https://www.neowin.net/forum/topic/1081351-clients-looking-at-the-wrong-dhcp-server/#findComment-594904499 Share on other sites More sharing options...
sc302 Veteran Posted June 2, 2012 Veteran Share Posted June 2, 2012 Always looking for something to talk about. :p Link to comment https://www.neowin.net/forum/topic/1081351-clients-looking-at-the-wrong-dhcp-server/#findComment-594904533 Share on other sites More sharing options...
Recommended Posts