@ -26,7 +26,7 @@ No. Not yet. You get 1600x900. See the bottom of this ReadMe for details.
## DNS Setup
## DNS Setup
You'll likely want to create a DNS zone specifically for this script for better control over the hosts included. I would recommend using a TLD not normally available, to be sure you don't have any overlap with existing DNS names. This domain doesn't need to be publicly queried, and actually it's probably in interest of security if it isn't.
You'll likely want to create a DNS zone specifically for this script for better control over the hosts included. I would recommend using a TLD not normally available, to be sure you don't have any overlap with existing DNS names. This domain doesn't need to be publicly queried, and actually it's probably in interest of security if it isn't.
The best way to explain the zone set up is by example. Let's assume you create the zone "not-a-real.lan" and you have 5 hosts, known as host1.not-a-real.lan through host5.not-a-real.lan.
The best way to explain the zone set up is by example. Let's assume you create the zone "**not-a-real.lan**" and you have 5 hosts, known as *host1.not-a-real.lan* through *host5.not-a-real.lan*.
If you create the following entries (BIND format shown):
If you create the following entries (BIND format shown):
```
```
$ORIGIN not-a-real.lan.
$ORIGIN not-a-real.lan.
@ -41,7 +41,7 @@ host5 IN A 10.0.0.5
```
```
#### How will this work on the client?
#### How will this work on the client?
In this case, the script will create aliases called host1 through host5.
In this case, the script will create aliases called *host1* through *host5*.
Hosts 1, 2, and 5 will connect with, for example, `ssh -t your.username@10.0.0.1`
Hosts 1, 2, and 5 will connect with, for example, `ssh -t your.username@10.0.0.1`
