Connection to External DNS Server
Hi,
I have an AD Integrated DNS Server + Domain Controller running on Windows 2003. Client PCs are authenticated via this AD root Domain, DNS server.
Scenario : Client PCs are authenticated to my AD Integrated DNS Server + Domain Controller. However, there is a new requirement whereby these PCs need to communicate with an External DNS server as well. Ex, when they need to access webmail.XXX.com from their PCs, this should route to an External DNS server as long as it realises that there is no such entry in my AD integrated DNS Server + Domain Controller. We cannot add a forwarder primarily as its a root "." server. We might not be able to delete the root and restart the DNS service due to any possible production issues etc.
If I create a Standalone DNS server with perhaps a forwarder request to an external DNS Server and if i want my Client PCs to be able to send a request when required (Ex. when they need to access webmail.xxx.com) What should I do ?
- Does my external DNS server need to be in the Domain as well ?
- Do i need to add an additional entry in my AD Integrated DNS Server + Domain Controller with an entry of my Standalone DNS Server (Hostname + IP) ?
What other alternatives are there pls ?
I have an AD Integrated DNS Server + Domain Controller running on Windows 2003. Client PCs are authenticated via this AD root Domain, DNS server.
Scenario : Client PCs are authenticated to my AD Integrated DNS Server + Domain Controller. However, there is a new requirement whereby these PCs need to communicate with an External DNS server as well. Ex, when they need to access webmail.XXX.com from their PCs, this should route to an External DNS server as long as it realises that there is no such entry in my AD integrated DNS Server + Domain Controller. We cannot add a forwarder primarily as its a root "." server. We might not be able to delete the root and restart the DNS service due to any possible production issues etc.
If I create a Standalone DNS server with perhaps a forwarder request to an external DNS Server and if i want my Client PCs to be able to send a request when required (Ex. when they need to access webmail.xxx.com) What should I do ?
- Does my external DNS server need to be in the Domain as well ?
- Do i need to add an additional entry in my AD Integrated DNS Server + Domain Controller with an entry of my Standalone DNS Server (Hostname + IP) ?
What other alternatives are there pls ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi,
I already have a Secondary DC with an DNS entry. This Secondary DC replicates with my primary DC.
I can add a Third Dns entry on my DHCP Server but does that mean the Client PC will attempt to resolve the hostname from the 1st DNS entry and if it fails, try the 2nd entry and thereafter try resolving via the 3rd DNS entry ? or would it attempt a connection to the 1st DNS entry, and if it cannot resolve ----> Send a reply indicating that it could not find the host ! Thanks
I already have a Secondary DC with an DNS entry. This Secondary DC replicates with my primary DC.
I can add a Third Dns entry on my DHCP Server but does that mean the Client PC will attempt to resolve the hostname from the 1st DNS entry and if it fails, try the 2nd entry and thereafter try resolving via the 3rd DNS entry ? or would it attempt a connection to the 1st DNS entry, and if it cannot resolve ----> Send a reply indicating that it could not find the host ! Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi,
Reckon you are right. What i basically need is for my internal DNS server to communicate with an External DNS Server to resolve addresses not present in my DNS server. When client PCs attempt to access an external address, we want the dns entry to be forwarded to the respective external dns server to resolve the hostname.
What other alternatives are there ? Thanks alot.
Reckon you are right. What i basically need is for my internal DNS server to communicate with an External DNS Server to resolve addresses not present in my DNS server. When client PCs attempt to access an external address, we want the dns entry to be forwarded to the respective external dns server to resolve the hostname.
What other alternatives are there ? Thanks alot.
ASKER
Issue was only partially resolved
OOPS haven't been online for awhile, but the last part you're looking at setting up forwarders.
The last two links are step-by-step guides, the others are for understanding.
http://support.microsoft.com/kb/304491
http://www.computerperformance.co.uk/w2k3/services/DNS_conditional_forward.htm
http://www.windowsnetworking.com/articles_tutorials/dns_conditional_forwarding_in_windows_server_2003.html
http://www.techrepublic.com/article/step-by-step-standard-and-conditional-forwarding-in-windows-2003-dns/5112303
The last two links are step-by-step guides, the others are for understanding.
http://support.microsoft.com/kb/304491
http://www.computerperformance.co.uk/w2k3/services/DNS_conditional_forward.htm
http://www.windowsnetworking.com/articles_tutorials/dns_conditional_forwarding_in_windows_server_2003.html
http://www.techrepublic.com/article/step-by-step-standard-and-conditional-forwarding-in-windows-2003-dns/5112303
Do users need to access domain XXX.com for any other servers/services?
If not then create a zone on your DNS server called XXX.com.
Next, create an Host A record for webmail and give it the external address.