Remote office, no DC and a public DNS Server


we trying unique setup, turning out more trouble expected.

we have 1 office, contains our servers, dhcp, dns, dc, exch, file...etc   office has own internet connection.

servers: 192.168.0.109 our dns , dc server.

we have second office, connected main office via fiber connection.   second office disaster muster zone , needed connect them own internet connection.  essentially, if main office down, office needs have access internet.

we configured firewall on remote office side use 8.8.8.8 , 192.168.0.109 our dns, when try ping dc name not resolve.

we have added names/ips house files, allows resolve servers name, not able authenticate ad @ all.  when log computers logging in via cached credentials , when try access network shares, need enter credentials.

is trying possible without having local dc

using 1 public , 1 internal dns in same dns server list definetly not idea because query results unpredictable because hard predict of dns servers used process query. if firewall supports it, can use conditional forwarding or dns views configure firewall forward queries internal names internal dns , send rest public dns.

so, scenario absolutely possible, have name resolution right: queries names in ad domain should forwarded dc/dns server, while rest can sent public dns.


gleb.



Windows Server  >  Directory Services



Comments

Popular posts from this blog

Global Catalog ?

mailing list

Global Catalog