Sign inTry Free

Important

New database features are no longer connected to engine versions; features are now enabled independently during scheduled update windows, and “major” and “minor” releases no longer exist in Helios. Please visit the release notes to view the latest features available in your database clusters.

INET6_NTOA

On this page

The INET6_NTOA() function converts an IPv6 or IPv4 internet address from its binary representation to its text representation.

Syntax

INET6_NTOA( bin_str )

Arguments

  • bin_str: binary string.

Return Type

String.

The return string is lowercase. It has a maximum length of 39 characters.

If the argument is not a valid address - returns NULL.

Examples

SELECT INET6_NTOA(UNHEX('0A000101'));
+-------------------------------+
| INET6_NTOA(UNHEX('0A000101')) |
+-------------------------------+
| 10.0.1.1                      |
+-------------------------------+
SELECT INET6_NTOA(UNHEX('48F3000000000000D4321431BA23846F'));
+-------------------------------------------------------+
| INET6_NTOA(UNHEX('48F3000000000000D4321431BA23846F')) |
+-------------------------------------------------------+
| 48f3::d432:1431:ba23:846f                             |
+-------------------------------------------------------+
SELECT INET6_NTOA(INET6_ATON('2001:db8:8714:3a90::12'));
+--------------------------------------------------+
| INET6_NTOA(INET6_ATON('2001:db8:8714:3a90::12')) |
+--------------------------------------------------+
| 2001:db8:8714:3a90::12                           |
+--------------------------------------------------+
SELECT HEX(INET6_ATON(INET6_NTOA(UNHEX('48F3000000000000D4321431BA23846F'))));
+------------------------------------------------------------------------+
| HEX(INET6_ATON(INET6_NTOA(UNHEX('48F3000000000000D4321431BA23846F')))) |
+------------------------------------------------------------------------+
| 48F3000000000000D4321431BA23846F                                       |
+------------------------------------------------------------------------+

Related Topics

Last modified:

Was this article helpful?

On this page

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In