AAAA for packages.openmediavault.org?

  • I installed OMV in my IPv6-only network today. I want to install the ZFS plugin, so I reloaded the plugin list. It didn't complete, so I created a user and ran  sudo apt update .

    It told me packages.openmediavault.org couldn't be resolved. I then ran dig (on my laptop, connected to the same network) to check if it was resolvable. Here's the output:



    I also checked against Google's DNS servers. Both suggest that no AAAA record is configured for the OMV-specific package server, and therefore it is unreachable through IPv6. Is this intentional? Is IPv6 supported for downloading packages?

    • Official Post

    Is this intentional? Is IPv6 supported for downloading packages?

    While there are no ipv6 records for openmediavault.org or omv-extras.org, both have packages hosted by github which should have ipv6 records. Since packages.openmediavault.org is hosting the same packages as openmediavault.github.io/packages/, you don't need to worry about packages.openmediavault.org resolving.

    omv 8.2.2-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.2.1 | compose 8.1.6 | cterm 8.0 | borgbackup 8.1.7 | tempmon 8.0.3 | mergerfs 8.0.1 | scripts 8.0.1 | writecache 8.1.7


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!