on master help sign in
Merge pull request #487 from urbit/star-operators

Update star operator instructions

commit4bbc20db2914d72b344ebb4fdf7c13ef39a76f58 authorMorgan Sutherland <msutherl@users.noreply.github.com> dateTue 14 May 2019, 13:56 (7 years ago) parentc875e0d7885326
1 file changed+6−7
getting-started/operating-a-star.md+6−7
getting-started/operating-a-star.md+6−7
@@ -27,17 +27,16 @@ Below are some handy operations for the use and maintenance of your star.
2727
2828### DNS Proxying
2929
30−Your star is not aware of its own IP address by default. This means its dependent planets won't get DNS routing.
30+Previously star operators needed to run `:dns|ip` in the Dojo in order to set up DNS routing with their parent galaxy. This is no longer required.
3131
32−To provide DNS routing to your star's dependents, you need to set your star's IP address.
32+### Maintaining Connectivity
3333
34−+ Wait for the initial post-boot sync to succeed.
35−+ Enter `:dns|ip` into the Dojo.
36−+ The dojo will prompt you to enter something. Enter your IP address here.
34+Occasionally, your star might lose network connectivity due to a known timer issue or by falling out of sync with the Ethereum blockchain. When this happens, there are a few things to try:
3735
38−### Maintaining Connectivity
36+1. Enter the `|bonk` command in the Dojo to reset the timer and restore connectivity.
37+2. Run `|start %eth-manage`, then `:eth-manage %look-ethnode` to ensure that your star is synced up to the latest block.
3938
40−Occasionally, your star might lose network connectivity due to a known timer issue. When this happens, enter the `|bonk` command in the Dojo to reset the timer and restore connectivity.
39+When in doubt, contact [support@urbit.org](mailto:support@urbit.org).
4140
4241### Escaping a Sponsor
4342