Windows Server 2008 R2

Fenitis
Member

196

03-05-2016, 11:20 AM

You're frequently connecting your client to the domain server even after updating its IP address. The DHCP, DNS, and ADDS settings should resolve this issue.

Fenitis

03-05-2016, 11:20 AM #1

You're frequently connecting your client to the domain server even after updating its IP address. The DHCP, DNS, and ADDS settings should resolve this issue.

stare56
Junior Member

03-07-2016, 07:15 PM

It involves more steps than initially thought. You need to configure your server as a DNS server, not just install it. Then you must set up your PC's IP address so it connects to the server as its DNS provider. Finally, it will become part of the domain.

stare56

03-07-2016, 07:15 PM #2

Shanniee_
Member

104

03-08-2016, 01:11 AM

How I can setup the DNS Server?

Shanniee_

03-08-2016, 01:11 AM #3

How I can setup the DNS Server?

iAptone
Junior Member

03-08-2016, 04:15 AM

DNS was already set up during the installation of AD. On the client machine, navigate to DNS servers and input the IP address of your DC. This approach works.

iAptone

03-08-2016, 04:15 AM #4

DNS was already set up during the installation of AD. On the client machine, navigate to DNS servers and input the IP address of your DC. This approach works.

jolo012b
Member

03-23-2016, 10:27 PM

Did you list the DNS server as the primary in the DHCP configuration? Since you're using a .net domain, if your DNS records aren't accepted initially, the system will search further. You might consider using the FQDN instead.

jolo012b

03-23-2016, 10:27 PM #5