Child pages
  • CommIT VPC DNS and VPN Setup

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

To make the development environment identical to the production environment, configure your client to override the authoritative DNS server(s) for the domain to the development environment.  You can either configure your DNS, or you can use a VPN.


Currently, the DNS server for VPC-Dev runs on a personal, free t2.micro instance in EC2 and is accessible at  You will need a secondary resolver for real addresses, such as, (Level3), or, or


VPN with L2TP over IPSec


Account Name: commitdev
Click Authentication Settings...


yum -y install Installation 

yum install -y --enablerepo=epel openswan xl2tpd bind

Configure /etc/named.conf and the zone file /var/named/masters/ (see examples attached).  Configure xl2tpd and Openswan.

chkconfig named on

chkconfig ipsec on

chkconfig xl2tpd on

Recursion is disabled and rate limiting is set at 5 per second.  Since there are a total of 3 records, this is basically impossible to use in any form of attack, ever, and it's in a personal account anyway.


named logs to /var/log/messages


/etc/init.d/named stop

This is configured to serve up the A and/or CNAME records for,, and for the specific VPC environment. 

VPN Docs:

pretty much just stole