Skip to content

Latest commit

 

History

History
90 lines (63 loc) · 3.62 KB

offline_dns.md

File metadata and controls

90 lines (63 loc) · 3.62 KB
Raw

Running bosh-lite and cloudfoundry using a custom dns and offline

by Vinicius Carvalho

Emulating Offline usage of BOSH

Run scripts/disable_container_internet to disable Internet on containers except for DNS.

To re-enable Internet, run scripts/enable_container_internet.

Using custom DNS

Install dnsmasq

A simple dns proxy for mac, its really easy to install if you have homebrew on your system

brew install dnsmasq

Follow the instructions at the end of the homebrew install to configure and start dnsmasq, which should look something like this:

To configure dnsmasq, copy the example configuration to /usr/local/etc/dnsmasq.conf
and edit to taste.

  cp /usr/local/opt/dnsmasq/dnsmasq.conf.example /usr/local/etc/dnsmasq.conf

To have launchd start dnsmasq at startup:
    sudo cp -fv /usr/local/opt/dnsmasq/*.plist /Library/LaunchDaemons
Then to load dnsmasq now:
    sudo launchctl load /Library/LaunchDaemons/homebrew.mxcl.dnsmasq.plist

Modify the dnsmasq configuration file to add an entry for your custom DNS, for example:

address=/.vincloud.com/10.244.0.34

Will add a wildcard domain pointing to my HA-PROXY machine in cloudfoundry.

Go to your network preferences and add 127.0.0.1 as your first DNS server.

Modify cf-release

Next step, edit cf-releases/cf-release.yml, replace any occurrence of xxx.xxx.xxx.xxx.xip.io with your own custom domain, you may end up with something like this:

    resource_directory_key: vincloud.com-cc-resources
    srv_api_uri: https://api.vincloud.com

+------------------------------------+---------+---------------+-------------+
| Job/index                          | State   | Resource Pool | IPs         |
+------------------------------------+---------+---------------+-------------+
| api_z1/0                           | running | large_z1      | 10.244.1.10 |
| ha_proxy_z1/0                      | running | router_z1     | 10.244.0.34 |
| hm_z1/0                            | running | medium_z1     | 10.244.1.14 |
| loggregator_trafficcontroller_z1/0 | running | small_z1      | 10.244.0.10 |
| loggregator_trafficcontroller_z2/0 | running | small_z2      | 10.244.2.10 |
| loggregator_z1/0                   | running | large_z1      | 10.244.0.14 |
| loggregator_z2/0                   | running | large_z2      | 10.244.2.14 |
| login_z1/0                         | running | medium_z1     | 10.244.1.6  |
| nats_z1/0                          | running | medium_z1     | 10.244.0.6  |
| postgres_z1/0                      | running | large_z1      | 10.244.0.30 |
| router_z1/0                        | running | router_z1     | 10.244.0.22 |
| runner_z1/0                        | running | runner_z1     | 10.244.0.26 |
| taskmaster_z1/0                    | running | runner_z1     | 10.244.1.18 |
| uaa_z1/0                           | running | large_z1      | 10.244.1.2  |
+------------------------------------+---------+---------------+-------------+

you can now use cf target http://api.<YOURDOMAIN> instead of the xip.io version.

Running offline

You may not have network connectivity sometimes. I had a hard time getting OSX to use the nameserver once my network was down, thanks to this serverfault post

Set all your network interface dns servers to 127.0.0.1:

   networksetup -setdnsservers Ethernet 127.0.0.1
   networksetup -setdnsservers Wi-Fi 127.0.0.1
    ...

Create a file /etc/resolver/whatever: nameserver 127.0.0.1 domain .

Now this should work offline.