NNS and DNS support for human friendly container names #3

New issue

Closed

opened 2025-12-28 18:06:33 +00:00 by sami · 3 comments

sami commented

2025-12-28 18:06:33 +00:00

Owner

Originally created by @realloc on GitHub (May 19, 2021).

Originally assigned to: @KirillovDenis on GitHub.

Problem
It may not be convenient for humans to operate with NeoFS low level ContainerID and ObjectID.

Proposed solution
Use NNS to allow looking up ContainerID by it's domain and friendly name string. It should be also possible to mirror the same mechanism for regular DNS to simplify application client-side development.

Originally created by @realloc on GitHub (May 19, 2021). Originally assigned to: @KirillovDenis on GitHub. **Problem** It may not be convenient for humans to operate with NeoFS low level `ContainerID` and `ObjectID`. **Proposed solution** Use NNS to allow looking up `ContainerID` by it's domain and friendly name string. It should be also possible to mirror the same mechanism for regular DNS to simplify application client-side development.

sami closed this issue

2025-12-28 18:06:34 +00:00

sami commented

2025-12-28 18:06:34 +00:00

Author

Owner

@alexvanin commented on GitHub (May 27, 2021):

Name resolving should be done in client side IMO. We can provide resolving module in neofs-sdk-go and use it in neofs-cli and protocol gates.

@alexvanin commented on GitHub (May 27, 2021): Name resolving should be done in client side IMO. We can provide resolving module in `neofs-sdk-go` and use it in neofs-cli and protocol gates.

sami commented

2025-12-28 18:06:34 +00:00

Author

Owner

@realloc commented on GitHub (Jul 15, 2021):

Recently, we came to an agreement to have a well-known ID for the NNS contract in SideChain. Human-friendly address aliases may be stored there, additionally to the NNS in mainnet. If there will be a DNS zone mapped to the NNS records, we have two more possible sources for aliases.

Hence, the resolver module has to work with NNS or DNS, depending on the configuration.

@realloc commented on GitHub (Jul 15, 2021): Recently, we came to an agreement to have a well-known ID for the NNS contract in SideChain. Human-friendly address aliases may be stored there, additionally to the NNS in mainnet. If there will be a DNS zone mapped to the NNS records, we have two more possible sources for aliases. Hence, the resolver module has to work with NNS or DNS, depending on the configuration.

sami commented

2025-12-28 18:06:34 +00:00

Author

Owner

@alexvanin commented on GitHub (Sep 9, 2021):

So basically we want to expand NeoFS API Client interface with DNS \ NNS support. Client should:

support TXT names of the container,
support endpoint to DNS server.
resolve container names.

Unfortunately, client is still in neofs-api-go repository.

@alexvanin commented on GitHub (Sep 9, 2021): So basically we want to expand NeoFS API Client interface with DNS \ NNS support. Client should: - support TXT names of the container, - support endpoint to DNS server. - resolve container names. Unfortunately, client is still in neofs-api-go repository.