<div>
Use static IP addresses. You should be able to obtain static addresses from your provider(s) for relatively little expense, if any.
</div>


Use static IP addresses. You should be able to obtain static addresses from your provider(s) for relatively little expense, if any.

<div>
if it is a DC, have it host the DNS service locally at the branch, and point it to it to iself for DNS. easiest would eb to make Dynamic DNS AD intergrated ( or alternatively zone transfer to teh branch DC.<br />
<br />
make sure the DNs forwarder for teh Branch DC( also now DNS) point to ISP dns
</div>


if it is a DC, have it host the DNS service locally at the branch, and point it to it to iself for DNS. easiest would eb to make Dynamic DNS AD intergrated ( or alternatively zone transfer to teh branch DC.

make sure the DNs forwarder for teh Branch DC( also now DNS) point to ISP dns

<div>
<div class="content wysiwyg-content">
I have a domain controller instaled in a branch office, and i use VPN/Routing and remote access to establish the VPN link between this DC and the Main office DC.<br />
the problem that im facing is that i'm using DynDns, so when the DC starts it needs to dial the VPN connection thus i have to put our ISP DNS IP(213.x.x.20) so that the branch office resolve the IP address of my main office. but after establishing the connection it cannot resolve the client names in the main office as the primary DNS of the server is actually the ISP, so every time i have to change it back to the main office DNS IP (10.100.1.1).<br />
<br />
is there any way to resolve this issue?<br />

</div>
</div>


I have a domain controller instaled in a branch office, and i use VPN/Routing and remote access to establish the VPN link between this DC and the Main office DC.
the problem that im facing is that i'm using DynDns, so when the DC starts it needs to dial the VPN connection thus i have to put our ISP DNS IP(213.x.x.20) so that the branch office resolve the IP address of my main office. but after establishing the connection it cannot resolve the client names in the main office as the primary DNS of the server is actually the ISP, so every time i have to change it back to the main office DNS IP (10.100.1.1).

is there any way to resolve this issue?


Branch office DC DNS Problem initiating VPN connection and resolving main office clients

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

A virtual private network (VPN) is a network that uses a public telecommunication infrastructure, such as the Internet, to provide remote offices or travelling users access to a central organizational network securely. VPNs encapsulate data transfers using secure cryptographic methods and other security mechanisms to ensure that only authorized users can access the network and that the data cannot be intercepted.