there's following configuration. internal network - internal nameserver resolves example.com outside world - amazon route 53 resolves example.com
the internal network has special records example.com, not able move off these records other domain (like example.internal), neither use route 53 nameservers internally.
is possible example www.example.com goes route 53 nameserver , other records handled original nameserver?
copy records statically internal dns not solution (only temporary hack), use failover @ route 53 low ttl, we'd lose feature internal network.
what know internal dns it's microsoft-based solution, coupled activedirectory.
is there solution that? configuring on client side (socks proxy under chrome example) challenging, many clients inside.
yes, delegation. if add:
www ns your.aws.dns.ip that tells client using resolver go your.aws.dns.ip answer www.domain.com.
Comments
Post a Comment