I set up a Windows 2003 Server Domain with Active Directory and DNS. Our DNS name (per the Active Directory configuration wizard is hq.company.com.au)
DNS is running on the Domain Controller DC01 and the IP address is 192.168.1.101
I also have a router (IP 192.168.1.254) which acts as the DHCP server which assigns clients the Primary DNS address of 192.168.1.101 and the secondary as 192.168.1.254 (the router itself)
This generally works okay, but local computers cannot resolve our website address www.company.com.au
unless I set the primary DNS address to the router/default gateway.
I can do this, but it means that the client logon process takes anywhere for 30 seconds - 2 minutes.
So I'm trying to figure out a way to keep the primary DNS server address as the AD/Windows based DNS server and still be able to resolve our website from all local clients.
Is there a simple change I can make to our DNS configuration to support this? I just figure that the computers on our network should belong to the hq.company.com.au forward lookup zone, but I really don't know.
I've also attached an IPCONFIG from a windows xp client and the domain controller/dns server. The only thing that looks perhaps a little strange to me (again, I'm guessing) is the DNS suffixes....I note that on the client the connection specific suffix is home.gateway (assigned by the router) or the DNS suffix search list.
Would appreciate some step by step instructions to resolve this.