I have succesfully setup and configured a domain controller and DNS service for my home network. its on a HP Proliant MicroServer running Windows Server 2008 R2 Foundation, everything is running smooth, but the server is not always on. I have specified the server as my preferred DNS server in my network settings on my laptop, and my ISP DNS as the alternate. This works fine, if i shutdown the server my laptop falls back to the secondary DNS. But if i turn the server on again, i can't connect my laptop to any of the domains under the domain controller.
I guess this is because im still using the alternate DNS on my laptop. If i go to the adapter settings and select a new IP, e.g 192.168.1.40 i can connect to the domains on the domain controller again.
Server ----------------------------------------------- Hostname: mproliant IP: 192.168.1.35 Standard Gateway: 192.168.1.1 Services: DNS Domain Controller IIS Domains home.local staging.home.local
Laptop ----------------------------------------------- Hostname: t510 IP: 192.168.1.39 Standard Gateway: 192.168.1.1 Preferred DNS Server: 192.168.1.35 Alternate DNS Server: 89.150.129.4
If i run ipconfig /displaydns i get the following result for staging.home.local and home.local
staging.home.local ---------------------------------------- Name does not exist. home.local ---------------------------------------- Name does not exist.
If i select a new IP on the laptop and go to http://home.local in my browser, the site works.
And i get the following from running ipconfig /displaydns
home.local ---------------------------------------- Record Name . . . . . : home.local Record Type . . . . . : 1 Time To Live . . . . : 575 Data Length . . . . . : 4 Section . . . . . . . : Answer A (Host) Record . . . : 192.168.1.35
Another wierd thing, the network adapter on the server reports "No internet access" until i ping a hostname, e.g. cnn.com
How do i resolve this?