landrush 0.4.0 → 0.4.1
Sign up to get free protection for your applications and to get access to all the features.
- data/README.md +23 -8
- data/lib/landrush/command.rb +1 -1
- data/lib/landrush/version.rb +1 -1
- metadata +1 -1
data/README.md
CHANGED
|
@@ -16,24 +16,33 @@ Install under Vagrant (1.1 or later):
|
|
|
16
16
|
|
|
17
17
|
## Usage
|
|
18
18
|
|
|
19
|
+
### Get started
|
|
20
|
+
|
|
19
21
|
Enable the plugin in your `Vagrantfile`:
|
|
20
22
|
|
|
21
23
|
config.landrush.enable
|
|
22
24
|
|
|
23
|
-
Bring up a machine that has a private network IP address and a hostname (see the `Vagrantfile` for an example)
|
|
25
|
+
Bring up a machine that has a private network IP address and a hostname (see the `Vagrantfile` for an example)
|
|
24
26
|
|
|
25
27
|
$ vagrant up
|
|
26
28
|
|
|
27
29
|
And you should be able to get your hostname from your host:
|
|
28
30
|
|
|
29
31
|
$ dig -p 10053 @localhost myhost.vagrant.dev
|
|
30
|
-
|
|
32
|
+
|
|
31
33
|
If you shut down your guest, the entries associated with it will be removed.
|
|
32
34
|
|
|
35
|
+
|
|
36
|
+
### Static entries
|
|
37
|
+
|
|
33
38
|
You can add static host entries to the DNS server in your `Vagrantfile` like so:
|
|
34
39
|
|
|
35
40
|
config.landrush.host 'myhost.example.com', '1.2.3.4'
|
|
36
41
|
|
|
42
|
+
This is great for overriding production services for nodes you might be testing locally. For example, perhaps you might want to override the hostname of your puppetmaster to point to a local vagrant box instead.
|
|
43
|
+
|
|
44
|
+
### Unmatched Queries
|
|
45
|
+
|
|
37
46
|
Any DNS queries that do not match will be passed through to an upstream DNS server, so this will be able to serve as the one-stop shop for your guests' DNS needs.
|
|
38
47
|
|
|
39
48
|
### Visibility on the Guest
|
|
@@ -42,11 +51,9 @@ Linux guests using iptables should automatically have their DNS traffic redirect
|
|
|
42
51
|
|
|
43
52
|
### Visibility on the Host
|
|
44
53
|
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
All you do is drop a file in `/etc/resolver/$DOMAIN` with information on how to connect to the DNS server you'd like to use for that domain.
|
|
54
|
+
If you're on an OS X host, we can use a nice trick to unobtrusibly add a secondary DNS server only for specific domains.
|
|
48
55
|
|
|
49
|
-
|
|
56
|
+
If you name all of my vagrant servers with the pattern `$host.vagrant.dev` and then drop a file called `/etc/resolver/vagrant.dev` with these contents:
|
|
50
57
|
|
|
51
58
|
```
|
|
52
59
|
# Use landrush server for this domain
|
|
@@ -62,14 +69,22 @@ resolver #8
|
|
|
62
69
|
port : 10053
|
|
63
70
|
```
|
|
64
71
|
|
|
65
|
-
|
|
66
72
|
This gives us automatic access to the landrush hosts without having to worry about it getting in the way of our normal DNS config.
|
|
67
73
|
|
|
74
|
+
There's also a handy command to automate the creation of this file:
|
|
75
|
+
|
|
76
|
+
```
|
|
77
|
+
vagrant landrush install
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
### Additional CLI commands
|
|
81
|
+
|
|
82
|
+
Check out `vagrant landrush` for additional commands to monitor the DNS server daemon.
|
|
83
|
+
|
|
68
84
|
## Work in Progress - Lots to do!
|
|
69
85
|
|
|
70
86
|
* The guest visibility strategy assumes iptables-based firewall.
|
|
71
87
|
* Lots of static values that need configurin' - config location, ports, etc.
|
|
72
|
-
* VirtualBox only right now, need to support VMWare
|
|
73
88
|
* Tests tests tests.
|
|
74
89
|
|
|
75
90
|
## Contributing
|
data/lib/landrush/command.rb
CHANGED
data/lib/landrush/version.rb
CHANGED