Node Operator Guide
Full nodes resolve SuiNS names on Mainnet and Testnet without extra configuration. The node selects the SuiNS package and registry objects for its network from the chain identifier, so the name-service-* fields that earlier releases accepted in the YAML configuration file no longer exist.
Name resolution means translating a human-readable SuiNS name into the address it points to. Reverse resolution maps an address back to its registered name.
Mysten Labs public nodes:
- Mainnet: https://fullnode.mainnet.sui.io:443
- Testnet: https://fullnode.testnet.sui.io:443
Full node configuration
A current full node needs no SuiNS-specific configuration. The gRPC NameService (LookupName and ReverseLookupName) reads the SuiNS package address, registry ID, and reverse registry ID from values built into the node, and picks the Mainnet or Testnet set by checking the chain identifier of the network the node is on.
Built-in SuiNS values
Each value maps to a specific onchain object in the SuiNS deployment:
- Package address: The address of the SuiNS package. The node uses this to locate the name record types.
- Registry ID: The object ID of the SuiNS registry. The registry maps human-readable names to their resolved addresses.
- Reverse registry ID: The object ID of the reverse registry. The reverse registry maps addresses back to their registered names.
| Value | Mainnet | Testnet |
|---|---|---|
| Package address | 0xd22b24490e0bae52676651b4f56660a5ff8022a2576e0089f79b3c88d44e08f0 | 0x22fa05f21b1ad71442491220bb9338f7b7095fe35000ef88d5400d28523bdd93 |
| Registry ID | 0xe64cd9db9f829c6cc405d9790bd71567ae07259855f4fba6f02c84f52298c106 | 0xb120c0d55432630fce61f7854795a3463deb6e3b443cc4ae72e1282073ff56e4 |
| Reverse registry ID | 0x2fd099e17a292d2bc541df474f9fafa595653848cbabb2d7a4656ec786a1969f | 0xcee9dbb070db70936c3a374439a6adb16f3ba97eac5468d2e1e6fff6ed93e465 |
These values ship with the node binary. You do not set them in fullnode.yaml, and a new deployment of the SuiNS package takes effect when you upgrade to a node release that includes the new values.
How to update an existing configuration
Node releases that still included the JSON-RPC server accepted name-service-package-address, name-service-registry-id, and name-service-reverse-registry-id in fullnode.yaml. A current node ignores these fields. If your configuration file still contains them, remove them to avoid confusion:
- Open your node's YAML configuration file. The default file is
fullnode.yaml. - Remove any
name-service-*fields from the top level of the file. - Save the file.
- Restart the full node process. For how to start the node, see Running a full node.
After the node restarts, it resolves SuiNS names for incoming requests on Mainnet or Testnet.
Which networks support SuiNS name resolution?
Both Mainnet and Testnet support SuiNS name resolution:
- Mainnet: All Mainnet full nodes resolve names by default.
- Testnet: All Testnet full nodes resolve names by default.
Localnet and Devnet do not have a SuiNS deployment. On these networks, the node does not recognize the chain identifier and the NameService methods return an Unimplemented error stating that SuiNS is not configured for the network.
For complete details on configuring a Sui Full Node, see Run a Sui Full Node.