DNS Forwarder that is not recursive. Is this allowed?


we have situation have domain controllers across world have own child dns domains:

ex.   sitea.mycompany.com , siteb.mycompany.com, etc

these sites have own internet connectivity mpls company's data center.

currently remote dns servers have forwarders point dns servers in data center.    the data center dns servers have forwarders go out internet resolve outside dns queries.

this solution works, side effect have noticed related websites utilize akamai.    since outside dns queries being sourced data center dns servers, akamai returning ip addresses closest data center in us, , not remote sites spread out across world.  

in order fix need local dns servers go out local internet connection , resolve own external dns queries.   akamai see source ip local site , return ip closer site us.

the data center dns servers have dns zones can expanded @ time:

ex.   mycompany.com, domain-today.com, lookhere1.local, etc.      domain-tomorrow.com can added next month.

new domains added month , isn't practical touch each remote dns server add new stub domain.

my idea have data center dns servers listed top forwarder servers.    the data center dns servers configured not recursive, if zone not live on not forward internet dns server.   remote dns server go down it's forwarder list , send request next server (which configure internet dns server)?

if isn't viable solution have other suggestions?


since description don't know in advance domains setup on dc servers, , don't know external domains you'll want lookup, i'm not sure conditional forwarders much.

having tested believe idea should work, eg setting dns servers in dc not recursive , configuring remote dns servers connect internet rest of them. couldn't replicate setup, did :

set dns server not recursive, , confirm server on network still local lookups external lookups failing. add second choice dns server on other server external lookups. machine able local lookups still , able external lookups well. when tried resolving domain exists both on internet , on dns server worked, , crucially, when queried record on zone exists on dns server still resolved (so server hadn't stopped querying local dns server).

as understand it, when you've disabled recursion on dns server, if receives request external domain reply gives indicates can't resolve query, not record doesn't exist, machine requesting move onto next preference rather giving up.



Windows Server  >  Network Infrastructure Servers



Comments

Popular posts from this blog

Group Policy Event ID 1058 Error Code 1326 (The user name or password is incorrect)

Suspicious event log Event ID: 4905

DCOM received error "2147746132" from...