browser.preferred_protocolsrecord that can be set to a list of the defined protocols.
browser.preferred_protocolsis not set, a browser should use the following value as a default
["bzz", "ipfs", "https", "http", "ftp"]. If
browser.preferred_protocolsis set but is not complete, a browser should append the absent protocols in the default order specified above. A domain can have a single content identifier for each distributed protocol stored in
bzzprotocol. See Dweb records for more information.
dwebhash records are set, a browser should fall back to legacy ipfs record that is set as
ipfs.html.valuerecords are set, a browser should fall back to DNS resolution that is set within
dns.*records are set, a browser should fall back to the
browser.redirect_urlkey has a priority over
ipfs.redirect_domain.valueif both are set.
http://prefix for any domain in the address bar if the protocol is not specified explicitly by a user. For blockchain domain names (assuming a browser supports many protocols), it is preferred to determine a protocol only after resolving domain records.
ipfs.redirect_domain.valuecontains full URL according to RFC-1738 and no additional actions required to provide redirect.
dns.*— For traditional DNS records
dweb.*— For distributed content records
browser.*— Hint records to help a browser determine a preferred hypermedia protocol
Resolverrecords may contain classical DNS records along with other records. To distinguish those from other CNS (Crypto Name Service) records, the
dns.*namespace is used. So DNS
Acorresponds to the
dns.ACNS record. Any listed DNS record described in RFC standards is supported. All record names must follow the uppercase naming convention.
CNAMErecord set to
example.com.must be configured as one crypto record
Arecords set to
10.0.0.2must be configured as one crypto record
www.example.comrecord can only be set inside a resolver of
www.example.combut never inside
dns.ttl. TTL for an individual record type can be set in
ttlfor individual an record type is not set, a default
dns.ttlmust be applied. If a
dns.ttlrecord is not set, the client recommends using
300(5 minutes) as a default value.
dns.ttlinstead of TTL for individual records is recommended due to higher gas efficiency.
dweb.*namespace. Each protocol has its own sub-namespace for its data using a canonical name. Example: Swarm's protocol canonic name is
bzzso its records are stored at
.hashrecord used to reference content in the distributed network. Example:
dweb.ipfs.hashfor IPFS protocol.
ipfs.html.valuedeprecated in favor of
ipfs.redirect_domain.valuedeprecated in favor of