3 replies
by cg it
by douglasb
I have run the wizard (by the way, everything was working fine until my ISP changed their primary DNS). However, when I run it I end up with the wrong primary and secondary DNS, don't know why that happens. On the NIC connecting to my ISP I configured the new pri/sec DNS addresses and the second NIC to my local network was also configured correctly. Not sure what went wrong.
by mjost
Assuming a hardware NAT firewall configured as no DHCP., SBS is the DHCP and DNS server, the workstation joined to the domain and is setup for DHCP, DHCP is pointing everyone to the SBS for DNS and the correct Gateway, no prior server lan IP address changes since installed,
then the SBS client DNS is not pointing to itself causing this issue.
Do not configure the DNS client settings on the domain controllers to point to your Internet Service Provider's (ISP's) DNS servers. If you configure the DNS client settings to point to your ISP's DNS servers, the Netlogon service on the domain controllers does not register the correct records for the Active Directory directory service. With these records, other domain controllers and computers can find Active Directory-related information. The domain controller must register its records with its own DNS server.
Hope this helps.
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending