I have a local Forward Lookup Zone (Win Server 2003) for zxurian.com that has it's own A record, as well as a few subdomain records. I also use Route 53 for public DNS, and have a hosted zone there of "zxurian.com"
Is it possible to setup my local DNS to be first in the chain for computers behind it, but if a request for a subdomain isn't found locally, pass it to Route 53 for further lookup? I'd rather not copy every subdomain from Route 53 into my local DNS.
Ex. request for foo.zxurian.com
- First stop is my local DNS (192.168.0.1) -- not found
- Forwards to Route 53. (aws56.awsdns-123.org) -- found, returns 220.127.116.11
- foo.zxurian.com is no pointing to 18.104.22.168 in local dns cache
Additional Information - Added 2015-01-22 13:02
Local authoritative server (192.168.0.1) - public IP (100.101.102.103)
Lookup Zones zxurian.local 192.168.0.1 dionysus.zxurian.local 192.168.0.10 loki.zxurian.local 192.168.0.12 zxurian.com 22.214.171.124 (public web server) test.zxurian.com 192.168.0.50 (internaly hosted web server)
Route 53 Authoritative Server
zxurian.com 126.96.36.199 (public web server) test.zxurian.com 100.101.102.103 (public address of internal web server) download.zxurian.com 188.8.131.52 (public web server)
So with that information, what I'm trying to ask/accomplish:
A computer outside the local network would always use Route 53, not an issue.
On a computer inside the local network, a request to
download.zxurian.com would first try the local server (since all local computers use the local server for DNS), but upon failing to find a matching record, it would then look to Route 53.
Would this happen by the local DNS passing the request to route 53, then passing the answer back to the client, or would the client then ask Route 53 directly, or would it happen at all?