on master help sign in
Update using-your-ship.md
commitd503b0016113bc1b80d7123e8ce5dd31d2bbef6e authorMatilde Park <matilde@tlon.io> dateWed 4 Dec 2019, 20:56 (7 years ago) parent6ce7f1c
1 file changed+2−8
content/using/operations/using-your-ship.md+2−8
content/using/operations/using-your-ship.md+2−8
@@ -194,16 +194,10 @@ For a planet or star's DNS proxying request to be made and fulfilled, they must
194194
195195To get `ship.arvo.network` on a planet or star, you must set up DNS routing with its parent ship by starting the `:dns` app.
196196
197−To do so, simply run this command in your ship's Dojo:
197+To do so, simply run this command in your ship's Dojo, passing the IP address as an argument, using the .0.0.0.0 (`@if`) syntax. For example:
198198
199199```
200−> -dns-address +dns/request
201−```
202−
203−You'll then be prompted to enter the public IP address of your ship. You can also pass the IP address as an argument, using the .0.0.0.0 (`@if`) syntax. For example:
204−
205−```
206−> -dns-address +dns/request .1.2.3.4
200+> -dns-address [%dns-address %if .1.2.3.4]
207201```
208202
209203`:dns`, running locally, will make an HTTP request to that IP address on port 80 to confirm that it is itself available at that IP and port. If that fails, you'll receive a `%bail-early` message in `:chat-cli`; this request will retry a few times. If the self-check is successful, the request is relayed to `~zod`, and you'll receive a message saying, `request for DNS sent to ~zod`. Once `~zod` has acknowledged receipt of the request, your local `:dns` app will send a `:chat-cli` message saying `awaiting response from ~zod`.