Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


IPv6 /64 SUBNET, SUB-DELEGATED REVERSE-ZONE, etc For VPS (NameServer)
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

IPv6 /64 SUBNET, SUB-DELEGATED REVERSE-ZONE, etc For VPS (NameServer)

atErikatErik Member
edited May 2019 in Requests

Hi, requesting for KVM-VPS / OVZ-VPS from EU / US location , which can provide/include an Internet Routable IPv6 SUBNET & MUST Sub-DELEGATE the REVERSE-ZONE of that assigned IPv6 SUBNET to my-domain's DNS-NameServer running in the VPS . Assigned IPv6 SUBNET should be atleast-one IPv6 /64 SUBNET , ( i will prefer to have one IPv6 /64 subnet over having any other smaller subnets, like: /96 IPv6 subnet, etc )

Objective is to allow my DNS-NameServer(s) able to setup/define the PTR/RDNS for any IPv6-Address from that assigned IPv6-SUBNET, for our project's Users.

VPS-PROVIDER MUST BE ABLE TO SETUP/SUB-DELEGATE/POINT THE ASSIGNED /64 or /96 IPv6-SUBNET'S REVERSE-ZONE INTO/TOWARD OUR PROJECT'S DOMAIN/ZONE DNS-NAMESERVER(s).

VPS/VZ-1:
VZ-Type: OpenVZ , Number of CPU Cores: 2 or more,
RAM: 2GB or more , Disk Space: 25GB or more , Disk Type: SSD/HDD,
Bandwidth: 3TB or more , Port Speed: 1Gbps or more,
DDoS-Protection: Not needed but better if available,
Number of IPv4s: 1 , Number of minimum fixed/routable IPv6-Address: 10 ( NameServer, Mail, etc server-apps ),
Must Set 1xIPv4 + 10xIPv6-ADDRESS's PTR/Reverse-DNS ( to match our domains ),
Must be able to assign at-least one/single IPv6 /64 ( or one /96 ) SUBNET,
Must be able to Sub-DELEGATE the REVERSE-ZONE of that assigned IPv6 SUBNET to our DNS-NameServer in VPS,
Location: (almost any) EU location (except UK) , Any location from USA,
Budget: USD $18/year or lower , Billing period: Yearly (via Paypal/Alipay).
Not-oversold/not-crowded vps node provider is preferable.

VPS/VZ-2:
VZ-Type: KVM , Number of CPU Cores: 2 or more,
RAM: 2GB DDR or more , Disk Space: 35GB or more , Disk Type: SSD/HDD,
Bandwidth: 3TB or more , Port Speed: 1Gbps or more,
DDoS-Protection: Not needed but better if available,
Number of IPv4s: 1 , Number of minimum fixed/routable IPv6-Address: 10 ( NameServer, Mail, etc server-apps ),
Must Set 1xIPv4 + 10xIPv6-ADDRESS's PTR/Reverse-DNS ( to match our domains ),
Must be able to assign at-least one/single IPv6 /64 ( or one /96 ) SUBNET,
Must be able to Sub-DELEGATE the REVERSE-ZONE of that assigned IPv6 SUBNET to our DNS-NameServer in VPS,
Location: (almost any) EU location (except UK) , Any location from USA,
Budget: USD $25/year or lower , Billing period: Yearly (via Paypal/Alipay).
Not-oversold/not-crowded vps node provider is preferable.

if possible for you to mention, then i would like to know, what would be your IPv4 /29 one SUBNET's per year fee.

My family & partners/devs working on a project that must assign (fixed+dynamic) IPv6-address to our project's each User & setup PTR/RDNS for each IPv6-Address, etc . Project includes MAIL-server, IM, etc. ( We have sufficient IPv4s on other VPSes, for this project).

Thanks in advance, for your offer/info.


EXTRA-NOTES / EXTRA-INFO:

Single/one /64 IPv6 "SUBNET" has 18-QuinTillion IPv6-"ADDRESS"es.
Single/one /96 IPv6 subnet has 4,294,967,296 (around 4 Billion) IPv6 addresses.
IPv6 /96 subnet is much much smaller subnet than a IPv6 /64 subnet.
One IPv6 /96 subnet contains 4-BILLION TIMES LESS IPv6-addresses THAN One/Single IPv6 /64 subnet. You can create 4-BILLIONS VPSes Each with one /96 SUBNET, from just ONE /64 SUBNET.
Suppose you have a IPv6 /32-subnet : You can divide it into 4-BILLIONS sub-parts/sub-portions, EACH with one /64-subnet = 18-QuinTillion-IPv6-Addresses, OR, You can divide it into 16-MILLIONS sub-parts/sub-portions, EACH with one /56-subnet.
Suppose you have a IPv6 /40-subnet : You can divide it into 16-MILLIONS sub-parts/sub-portions, EACH with one /64-subnet.
Suppose you have a IPv6 /44-subnet : You can divide it into 1-MILLION sub-parts/sub-portions, EACH with one /64-subnet.
Suppose you have a IPv6 /48-subnet : You can divide it into 64-THOUSANDS sub-parts/sub-portions, EACH with one /64-subnet.
Suppose you have a IPv6 /56-subnet : You can divide it into 256 sub-parts/sub-portions, EACH with one /64-subnet.

There are some users/people who always worry/ask that Can assigning such amount of IPv6-addresses to only one VPS/user/client will finish-up all IPv6 ? <-- NO, even if world has 100 Billions or more Users/Devices and even if EACH is assigned ONE/single /64 IPv6-SUBNET (18-QuinTillion IPv6-Addresses), it will still be a VERY VERY VERY VERY VERY...VERY tiny fragment of vast IPv6 pool available or assignable (from IANA).

When you want various benefit of AUTO configurations or SLAAC/etc and benefit of other standard (internet routable) IPv6 features, then its better to use IPv6-addresses from IPv6 /64 subnet for the VPS.
When you end-up using a (internet routable) IPv6 /96 subnet ( or any other smaller subnet than the minimum standard /64 IPv6 subnet, for the VPS ) then you will miss some of the standard IPv6 features & you may have to assign fixed-IPv6 or use DHCPv6/etc ( instead of SLAAC ) for dynamic allocation, etc, etc, but for most server-side server-apps, a /96 subnet is still sufficient, ( as long as VPS-provider's Nodes are configured fine).

VPS-Provider either (a) must have/running their own DNS-NAMESERVER(s) and have/own /32 /48 /56 /60 or /64 etc IPv6 Subnet/Blocks/pool from their ISP, OR, (b) have obtained /48 /56 /60 or /64 etc IPv6 Subnet/Blocks/pool from their USP(upstream-service-provider) IPv6 Assigning Authority, OR, (c) have obtained /32 /48 /56 /60 or /64 etc IPv6 Subnet/Blocks/pool from related regional Registries (RIR) under IANA , or (d) have obtained /32 /48 /56 /60 or /64 etc IPv6 Subnet/Blocks/pool from IPv6 Tunnel-Brokers (TB) . VPS-Provider's ISP ( or VPS-provider's USP or TB ) must Sub-Delegate Reverse-Zone for the assigned/obtained IPv6 subnet/blocks toward the VPS-Provider's DNS-NameServers ( or toward the VPS-Provider's Client/User/Customer DNS-NameServers ) . Then such VPS-Providers can further SUB-DELEGATE (Reverse-Zones) for further fractional/portion of IPv6 subnet/block (from their own pool) toward their Client/User/Customer/VPS domain/zone's DNS-NameServer . After setting up DNS-NameServer ( Reverse-Zone Delegation ) to point toward the next down-level NameServer ( Client's/Customer's DNS-NameServer ) , VPS-Provider need to configure their DHCPv6 ( or SLAAC, etc ) allocation server, & allocate the fractional SUBNET ( which was setup for Delegation toward Client's/User's/Customer's DNS-NameServer ) from their primary SUBNET pool , toward the IPv6-enabled network-interface of Client's/User's/Customer's VPS.

IPv6 Reverse-Zone Sub-Delegation Setup Process is similar ( though not exactly same ) to the process of Setting up a IPv4 Reverse-Zone Sub-Delegation for a /24 /30 etc IPv4 SUBNET, toward a Client's/User's/Customer's DNS-NameServers/VPS:
https://tools.ietf.org/html/rfc8501
https://tools.ietf.org/html/rfc2317
https://www.ripe.net/manage-ips-and-asns/db/support/configuring-reverse-dns
https://simpledns.com/kb/77/how-to-sub-delegate-a-reverse-zone-ipv4
https://www.netdaily.org/tag/29-classless-reverse-delegation-bind/
https://serverfault.com/questions/433400/ipv6-reverse-dns-delegation
https://www.gestioip.net/docu/ipv6_reverse_dns_delegation.html
https://serverfault.com/questions/521799/delegating-24-and-64-reverse-zones
https://unix.stackexchange.com/questions/115924/zone-delegation-in-bind
https://tools.ietf.org/html/rfc4472
https://www.royhochstenbach.com/delegating-reverse-lookup-zones-for-big-subnets/

i have copy-pasted various sections from various webpages & written this post message quickly from my own understanding , so there may be mistakes & discontinuity in the flow of submitted message here , sorry about that.


Please DO NOT MENTION Any VPS-Provider's Name/Plans Who Cannot Provide at-least one IPv6 SUBNET , i understand some VPS-Provider cannot/don't-want-to understand/setup Reverse-Zone Delegation ( thats why i provided extra-notes & links , it is matter of simple few lines in "named.conf" & related files ) . But please keep in mind , i posted this message only to find-out who or which offer/plan/deal(s) can DELEGATE Reverse-Zone for the assigned IPv6 subnet.

PLEASE AVOID MENTION of VPS-Providers or Plans/Offers/Deals which include only one/few IPv6-"ADDRESS" or NO-IPv6 or NO-IPv6-Subnet. Thank you.

AGAIN, PLEASE DON'T MENTION ANY VPS-PROVIDER'S NAME/PLANS WHICH CANNOT PROVIDE ANY IPv6 "SUBNET"/"BLOCK".

Thanked by 1uptime

Comments

  • pikepike Veteran

    Try ColoCrossing.

    Thanked by 1uptime
  • uptimeuptime Member
    edited May 2019

    wow.

    nice one.

    Impressive production values, impeccably scripted, perfectly matched with an all-star cast.

    A wild ride sure to leave every audience on the edge of their seats ...

    waiting for a deluge of support tickets to rain down from the sky.

    Recently at a sneak preview in Memphis ...

    a free bucket of amphetamine-flavored popcorn ...

    was given to every seventh theater-goer !!1!

    This is the story-within-a-story of that magical night.

    @atErik said:
    Hi, requesting for KVM-VPS / OVZ-VPS from EU / US location , which can provide/include an Internet Routable IPv6 SUBNET & MUST Sub-DELEGATE the REVERSE-ZONE of that assigned IPv6 SUBNET to my-domain's DNS-NameServer running in the VPS . Assigned IPv6 SUBNET should be atleast-one IPv6 /64 SUBNET , ( i will prefer to have one IPv6 /64 subnet over having any other smaller subnets, like: /96 IPv6 subnet, etc )

    Objective is to allow my DNS-NameServer(s) able to setup/define the PTR/RDNS for any IPv6-Address from that assigned IPv6-SUBNET, for our project's Users.

    VPS-PROVIDER MUST BE ABLE TO SETUP/SUB-DELEGATE/POINT THE ASSIGNED /64 or /96 IPv6-SUBNET'S REVERSE-ZONE INTO/TOWARD OUR PROJECT'S DOMAIN/ZONE DNS-NAMESERVER(s).

    VPS/VZ-1:
    VZ-Type: OpenVZ , Number of CPU Cores: 2 or more,
    RAM: 2GB or more , Disk Space: 25GB or more , Disk Type: SSD/HDD,
    Bandwidth: 3TB or more , Port Speed: 1Gbps or more,
    DDoS-Protection: Not needed but better if available,
    Number of IPv4s: 1 , Number of minimum fixed/routable IPv6-Address: 10 ( NameServer, Mail, etc server-apps ),
    Must Set 1xIPv4 + 10xIPv6-ADDRESS's PTR/Reverse-DNS ( to match our domains ),
    Must be able to assign at-least one/single IPv6 /64 ( or one /96 ) SUBNET,
    Must be able to Sub-DELEGATE the REVERSE-ZONE of that assigned IPv6 SUBNET to our DNS-NameServer in VPS,
    Location: (almost any) EU location (except UK) , Any location from USA,
    Budget: USD $18/year or lower , Billing period: Yearly (via Paypal/Alipay).
    Not-oversold/not-crowded vps node provider is preferable.

    VPS/VZ-2:
    VZ-Type: KVM , Number of CPU Cores: 2 or more,
    RAM: 2GB DDR or more , Disk Space: 35GB or more , Disk Type: SSD/HDD,
    Bandwidth: 3TB or more , Port Speed: 1Gbps or more,
    DDoS-Protection: Not needed but better if available,
    Number of IPv4s: 1 , Number of minimum fixed/routable IPv6-Address: 10 ( NameServer, Mail, etc server-apps ),
    Must Set 1xIPv4 + 10xIPv6-ADDRESS's PTR/Reverse-DNS ( to match our domains ),
    Must be able to assign at-least one/single IPv6 /64 ( or one /96 ) SUBNET,
    Must be able to Sub-DELEGATE the REVERSE-ZONE of that assigned IPv6 SUBNET to our DNS-NameServer in VPS,
    Location: (almost any) EU location (except UK) , Any location from USA,
    Budget: USD $25/year or lower , Billing period: Yearly (via Paypal/Alipay).
    Not-oversold/not-crowded vps node provider is preferable.

    if possible for you to mention, then i would like to know, what would be your IPv4 /29 /30 etc one SUBNET's per year fee.

    My family & partners/devs working on a project that must assign (fixed+dynamic) IPv6-address to our project's each User & setup PTR/RDNS for each IPv6-Address, etc . Project includes MAIL-server, IM, etc. ( We have sufficient IPv4s on other VPSes, for this project).

    Thanks in advance, for your offer/info.


    EXTRA-NOTES / EXTRA-INFO:

    Single/one /64 IPv6 "SUBNET" has 18-QuinTillion IPv6-"ADDRESS"es.
    Single/one /96 IPv6 subnet has 4,294,967,296 (around 4 Billion) IPv6 addresses.
    IPv6 /96 subnet is much much smaller subnet than a IPv6 /64 subnet.
    One IPv6 /96 subnet contains 4-BILLION TIMES LESS IPv6-addresses THAN One/Single IPv6 /64 subnet. You can create 4-BILLIONS VPSes Each with one /96 SUBNET, from just ONE /64 SUBNET.
    Suppose you have a IPv6 /32-subnet : You can divide it into 4-BILLIONS sub-parts/sub-portions, EACH with one /64-subnet = 18-QuinTillion-IPv6-Addresses, OR, You can divide it into 16-MILLIONS sub-parts/sub-portions, EACH with one /56-subnet.
    Suppose you have a IPv6 /40-subnet : You can divide it into 16-MILLIONS sub-parts/sub-portions, EACH with one /64-subnet.
    Suppose you have a IPv6 /44-subnet : You can divide it into 1-MILLION sub-parts/sub-portions, EACH with one /64-subnet.
    Suppose you have a IPv6 /48-subnet : You can divide it into 64-THOUSANDS sub-parts/sub-portions, EACH with one /64-subnet.
    Suppose you have a IPv6 /56-subnet : You can divide it into 256 sub-parts/sub-portions, EACH with one /64-subnet.

    There are some users/people who always worry/ask that Can assigning such amount of IPv6-addresses to only one VPS/user/client will finish-up all IPv6 ? <-- NO, even if world has 100 Billions or more Users/Devices and even if EACH is assigned ONE/single /64 IPv6-SUBNET (18-QuinTillion IPv6-Addresses), it will still be a VERY VERY VERY VERY VERY...VERY tiny fragment of vast IPv6 pool available or assignable (from IANA).

    When you want various benefit of AUTO configurations or SLAAC/etc and benefit of other standard (internet routable) IPv6 features, then its better to use IPv6-addresses from IPv6 /64 subnet for the VPS.
    When you end-up using a (internet routable) IPv6 /96 subnet ( or any other smaller subnet than the minimum standard /64 IPv6 subnet, for the VPS ) then you will miss some of the standard IPv6 features & you may have to assign fixed-IPv6 or use DHCPv6/etc ( instead of SLAAC ) for dynamic allocation, etc, etc, but for most server-side server-apps, a /96 subnet is still sufficient, ( as long as VPS-provider's Nodes are configured fine).

    VPS-Provider either (a) must have/running their own DNS-NAMESERVER(s) and have/own /32 /48 /56 /60 or /64 etc IPv6 Subnet/Blocks/pool from their ISP, OR, (b) have obtained /48 /56 /60 or /64 etc IPv6 Subnet/Blocks/pool from their USP(upstream-service-provider) IPv6 Assigning Authority, OR, (c) have obtained /32 /48 /56 /60 or /64 etc IPv6 Subnet/Blocks/pool from related regional Registries (RIR) under IANA . VPS-Provider's ISP ( or VPS-provider's USP ) must Sub-Delegate Reverse-Zone for the assigned/obtained IPv6 subnet/blocks toward the VPS-Provider's DNS-NameServers ( or toward the Client's/User's/Customer's DNS-NameServers ) . Then such VPS-Providers can further SUB-DELEGATE (Reverse-Zones) for further fractional/portion of IPv6 subnet/block (from their own pool) toward their Client/User/VPS domain/zone's DNS-NameServer . After setting up DNS-NameServer ( Reverse-Zone Delegation ) to point toward the next down-level NameServer ( Client's/Customer's DNS-NameServer ) , VPS-Provider need to configure their DHCPv6 ( or SLAAC, etc ) allocation server, & allocate a fractional SUBNET from their primary SUBNET pool, toward the IPv6-enaled network-interface of Client's/Customer's VPS.

    IPv6 Reverse-Zone Sub-Delegation Setup Process is similar ( though not exactly same ) to the process of Setting up a IPv4 Reverse-Zone Sub-Delegation for a /24 /30 etc IPv4 SUBNET, toward a Client's/User's/Customer's DNS-NameServers/VPS:
    https://tools.ietf.org/html/rfc8501
    https://tools.ietf.org/html/rfc2317
    https://www.ripe.net/manage-ips-and-asns/db/support/configuring-reverse-dns
    https://simpledns.com/kb/77/how-to-sub-delegate-a-reverse-zone-ipv4
    https://www.netdaily.org/tag/29-classless-reverse-delegation-bind/
    https://serverfault.com/questions/433400/ipv6-reverse-dns-delegation
    https://www.gestioip.net/docu/ipv6_reverse_dns_delegation.html
    https://serverfault.com/questions/521799/delegating-24-and-64-reverse-zones
    https://unix.stackexchange.com/questions/115924/zone-delegation-in-bind
    https://tools.ietf.org/html/rfc4472

    i have copy-pasted various sections from various webpages & written this post message quickly from my own understanding , so there may be mistakes & discontinuity in the flow of submitted message here , sorry about that.


    Please DO NOT MENTION Any VPS-Provider's Name/Plans Who Cannot Provide at-least one IPv6 SUBNET , i understand some VPS-Provider cannot/want-to understand/setup Reverse-Zone Delegation ( thats why i provided extra-notes & links , it is matter of simple few lines in named.conf ) . But please keep in mind , i posted this message only to find-out who or which offer/plan/deal can DELEGATE Reverse-Zone for the assigned IPv6 subnet.

    PLEASE AVOID MENTION of VPS-Providers or Plans/Offers/Deals which include only one/few IPv6-"ADDRESS" or NO-IPv6 or NO-IPv6-Subnet. Thank you.

    AGAIN, PLEASE DON'T MENTION ANY VPS-PROVIDER'S NAME/PLANS WHICH CANNOT PROVIDE ANY IPv6 "SUBNET"/"BLOCK".

    we must go deeper

    Thanked by 2angstrom atErik
  • angstromangstrom Moderator

    Good luck with your budget

    Thanked by 2uptime Clouvider
  • atErikatErik Member

    LET user @vimalware answered one of my previous request, & mentioned about AlphaVPS , they can assign IPv6 subnet almost 2 dollars less than what i've given above.
    i'm almost sure there are many other VPS-providers with much better deal than AlphaVPS.
    AlphaVPS sales/support rep did not want to setup Delegation.

  • Shot2Shot2 Member

    <3

  • atErikatErik Member

    i have forgotten to add "NATIVE IPv6 PREFERRED" in my op/top post.

  • anyNodeanyNode Member, Host Rep

    Hello,

    I've read your post, we wouldn't be able to help using our IPv6, but have you considered bringing your own?

    Potentially ask here https://www.lowendtalk.com/discussion/114478/the-aio-ip-related-thread-ipv4-ipv6-asn for a /48 IPv6 (minimum globally routeable) and have your provider announce it (we would be able to do so)

    As for your OVZ requirement we could fulfil that at $24/yr with BYOIP as described above. KVM however you need to increase your budget

  • atErikatErik Member
    edited May 2019

    For any IPv4/IPv6-"ADDRESS" you setup the REVERSE-DNS-ADDRESS , ( you add/setup PTR,etc dns-record in your(VPS-Provider/ISP/USP's) DNS-NameServer for your client/customer , & point toward Client's/Customer's host.zone / host.domain ).

    For any IPv4/IPv6-"SUBNET" you SUB-DELEGATE the REVERSE-ZONE , ( you add/setup NS,CNAME,etc dns-records in your(VPS-Provider/ISP/USP's) DNS-NameServer for your client/customer , & point toward Client's/Customer's host.zone / nameserver ).

  • @atErik said:
    For IPv4/IPv6-"ADDRESS" you setup the REVERSE-DNS, ( you setup PTR,etc dns-record in your(VPS-Provider/ISP/USP) DNS-NameServer for your client/customer & point to Client's/Customer's host.zone / host.domain ).

    For IPv4/IPv6-"SUBNET" you SUB-DELEGATE the REVERSE-ZONE, ( you setup NS,CNAME,etc dns-records in your(VPS-Provider/ISP/USP) DNS-NameServer for your client/customer & point to Client's/Customer's host.zone / nameserver ).

    ...what?

  • uptimeuptime Member
    edited May 2019

    @doghouch said:

    @atErik said:
    For IPv4/IPv6-"ADDRESS" you setup the REVERSE-DNS, ( you setup PTR,etc dns-record in your(VPS-Provider/ISP/USP) DNS-NameServer for your client/customer & point to Client's/Customer's host.zone / host.domain ).

    For IPv4/IPv6-"SUBNET" you SUB-DELEGATE the REVERSE-ZONE, ( you setup NS,CNAME,etc dns-records in your(VPS-Provider/ISP/USP) DNS-NameServer for your client/customer & point to Client's/Customer's host.zone / nameserver ).

    ...what?

    HE SAID:

    For any IPv4/IPv6-"ADDRESS" you setup the REVERSE-DNS-ADDRESS , ( you add/setup PTR,etc dns-record in your(VPS-Provider/ISP/USP's) DNS-NameServer for your client/customer , & point toward Client's/Customer's host.zone / host.domain ).

    For any IPv4/IPv6-"SUBNET" you SUB-DELEGATE the REVERSE-ZONE , ( you add/setup NS,CNAME,etc dns-records in your(VPS-Provider/ISP/USP's) DNS-NameServer for your client/customer , & point toward Client's/Customer's host.zone / nameserver ).

    I hope this is clear to you now!

  • atErikatErik Member
    edited May 2019

    BuyVM.net ( under FranTech.ca, @Francisco ) can assign native /64 IPv6 SUBNET (which includes 18-QuinTillion IPv6-Addresses) in LU location VPS, and their other location's VPS can assign tunneled(HE) /64 IPv6 SUBNET , their 2GB KVM plan is $7/month (much much higher than my budget) , a 512MB KVM plan is $20/yr is available (as of 2019-May-24th) . My/our pre-sales-ticket inquiry was answered by FranTech (quickly) , FranTech will upgrade their network & assign even /48 IPv6 SUBNET from next year . Their (VPS-Management) Panel currently allows to manually add/edit PTR/RDNS record (for the included IPv4 & IPv6-subnet's IP-Addresses) , their Panel do not yet support API based PTR/RDNS add/update from scripts in VPS . FranTech/BuyVM can do+support Sub-DELEGATION of REVERSE-ZONE (for the assigned IPv6-Subnet) toward the customer's/client's nameserver in VPS.

    As of today (2019-May-24th) this is what i've found related & shown publicly in their website ( KVM : "SLICE-512" : 1 Core @ 3.50+ GHz , Fair Share CPU Usage , 512 MB Memory , 10 GB SSD Storage , Unmetered Bandwidth/month , 1 IPv4 Address , USD $2.00/m or USD $20.00 / yr , DirectAdmin is now included with all plans at no additional cost! , Unmetered Dedicated KVM Slice Servers , BuyVM Anycast Network : Build your own global CDN today! , Anycast is a routing feature BuyVM offers for free to all customers , Anycast locations: (a) Las Vegas, Nevada, USA (West Coast) , (b) Piscataway, New Jersey, USA (East Coast) , (c) Roost, Luxembourg (LU), Europe , Anycast is free for all BuyVM VPS customers, Your total cost will be three VPS purchases , Anycast works even with our popular 128MB annual plans )

    i'm still waiting for response from few other VPS-Providers.
    and any user is welcome to post about any VPS-Provider that can do IPv6-SUBNET's reverse-zone delegation into their VPS with (close+comparable) resources+price which i mentioned in op/1st-post.
    i had to mention BuyVM/FranTech becasue of their UNMETERED bandwidth resources (and willingness to listen & serve their customers/clients).

    Thanked by 1uptime
  • FoulFoul Member

    @atErik
    Do you just love to spam and send tl;dr?

    Stop copying and pasting stuff,

    When none of the shit you say makes sense?

    Thanked by 1skorous
  • FalzoFalzo Member

    @uptime said:
    wow.

    nice one.

    Impressive production values, impeccably scripted, perfectly matched with an all-star cast.

    A wild ride sure to leave every audience on the edge of their seats ...

    waiting for a deluge of support tickets to rain down from the sky.

    Recently at a sneak preview in Memphis ...

    a free bucket of amphetamine-flavored popcorn ...

    was given to every seventh theater-goer !!1!

    This is the story-within-a-story of that magical night.

    @atErik said:
    Hi, requesting for KVM-VPS / OVZ-VPS from EU / US location , which can provide/include an Internet Routable IPv6 SUBNET & MUST Sub-DELEGATE the REVERSE-ZONE of that assigned IPv6 SUBNET to my-domain's DNS-NameServer running in the VPS . Assigned IPv6 SUBNET should be atleast-one IPv6 /64 SUBNET , ( i will prefer to have one IPv6 /64 subnet over having any other smaller subnets, like: /96 IPv6 subnet, etc )

    Objective is to allow my DNS-NameServer(s) able to setup/define the PTR/RDNS for any IPv6-Address from that assigned IPv6-SUBNET, for our project's Users.

    VPS-PROVIDER MUST BE ABLE TO SETUP/SUB-DELEGATE/POINT THE ASSIGNED /64 or /96 IPv6-SUBNET'S REVERSE-ZONE INTO/TOWARD OUR PROJECT'S DOMAIN/ZONE DNS-NAMESERVER(s).

    VPS/VZ-1:
    VZ-Type: OpenVZ , Number of CPU Cores: 2 or more,
    RAM: 2GB or more , Disk Space: 25GB or more , Disk Type: SSD/HDD,
    Bandwidth: 3TB or more , Port Speed: 1Gbps or more,
    DDoS-Protection: Not needed but better if available,
    Number of IPv4s: 1 , Number of minimum fixed/routable IPv6-Address: 10 ( NameServer, Mail, etc server-apps ),
    Must Set 1xIPv4 + 10xIPv6-ADDRESS's PTR/Reverse-DNS ( to match our domains ),
    Must be able to assign at-least one/single IPv6 /64 ( or one /96 ) SUBNET,
    Must be able to Sub-DELEGATE the REVERSE-ZONE of that assigned IPv6 SUBNET to our DNS-NameServer in VPS,
    Location: (almost any) EU location (except UK) , Any location from USA,
    Budget: USD $18/year or lower , Billing period: Yearly (via Paypal/Alipay).
    Not-oversold/not-crowded vps node provider is preferable.

    VPS/VZ-2:
    VZ-Type: KVM , Number of CPU Cores: 2 or more,
    RAM: 2GB DDR or more , Disk Space: 35GB or more , Disk Type: SSD/HDD,
    Bandwidth: 3TB or more , Port Speed: 1Gbps or more,
    DDoS-Protection: Not needed but better if available,
    Number of IPv4s: 1 , Number of minimum fixed/routable IPv6-Address: 10 ( NameServer, Mail, etc server-apps ),
    Must Set 1xIPv4 + 10xIPv6-ADDRESS's PTR/Reverse-DNS ( to match our domains ),
    Must be able to assign at-least one/single IPv6 /64 ( or one /96 ) SUBNET,
    Must be able to Sub-DELEGATE the REVERSE-ZONE of that assigned IPv6 SUBNET to our DNS-NameServer in VPS,
    Location: (almost any) EU location (except UK) , Any location from USA,
    Budget: USD $25/year or lower , Billing period: Yearly (via Paypal/Alipay).
    Not-oversold/not-crowded vps node provider is preferable.

    if possible for you to mention, then i would like to know, what would be your IPv4 /29 /30 etc one SUBNET's per year fee.

    My family & partners/devs working on a project that must assign (fixed+dynamic) IPv6-address to our project's each User & setup PTR/RDNS for each IPv6-Address, etc . Project includes MAIL-server, IM, etc. ( We have sufficient IPv4s on other VPSes, for this project).

    Thanks in advance, for your offer/info.


    EXTRA-NOTES / EXTRA-INFO:

    Single/one /64 IPv6 "SUBNET" has 18-QuinTillion IPv6-"ADDRESS"es.
    Single/one /96 IPv6 subnet has 4,294,967,296 (around 4 Billion) IPv6 addresses.
    IPv6 /96 subnet is much much smaller subnet than a IPv6 /64 subnet.
    One IPv6 /96 subnet contains 4-BILLION TIMES LESS IPv6-addresses THAN One/Single IPv6 /64 subnet. You can create 4-BILLIONS VPSes Each with one /96 SUBNET, from just ONE /64 SUBNET.
    Suppose you have a IPv6 /32-subnet : You can divide it into 4-BILLIONS sub-parts/sub-portions, EACH with one /64-subnet = 18-QuinTillion-IPv6-Addresses, OR, You can divide it into 16-MILLIONS sub-parts/sub-portions, EACH with one /56-subnet.
    Suppose you have a IPv6 /40-subnet : You can divide it into 16-MILLIONS sub-parts/sub-portions, EACH with one /64-subnet.
    Suppose you have a IPv6 /44-subnet : You can divide it into 1-MILLION sub-parts/sub-portions, EACH with one /64-subnet.
    Suppose you have a IPv6 /48-subnet : You can divide it into 64-THOUSANDS sub-parts/sub-portions, EACH with one /64-subnet.
    Suppose you have a IPv6 /56-subnet : You can divide it into 256 sub-parts/sub-portions, EACH with one /64-subnet.

    There are some users/people who always worry/ask that Can assigning such amount of IPv6-addresses to only one VPS/user/client will finish-up all IPv6 ? <-- NO, even if world has 100 Billions or more Users/Devices and even if EACH is assigned ONE/single /64 IPv6-SUBNET (18-QuinTillion IPv6-Addresses), it will still be a VERY VERY VERY VERY VERY...VERY tiny fragment of vast IPv6 pool available or assignable (from IANA).

    When you want various benefit of AUTO configurations or SLAAC/etc and benefit of other standard (internet routable) IPv6 features, then its better to use IPv6-addresses from IPv6 /64 subnet for the VPS.
    When you end-up using a (internet routable) IPv6 /96 subnet ( or any other smaller subnet than the minimum standard /64 IPv6 subnet, for the VPS ) then you will miss some of the standard IPv6 features & you may have to assign fixed-IPv6 or use DHCPv6/etc ( instead of SLAAC ) for dynamic allocation, etc, etc, but for most server-side server-apps, a /96 subnet is still sufficient, ( as long as VPS-provider's Nodes are configured fine).

    VPS-Provider either (a) must have/running their own DNS-NAMESERVER(s) and have/own /32 /48 /56 /60 or /64 etc IPv6 Subnet/Blocks/pool from their ISP, OR, (b) have obtained /48 /56 /60 or /64 etc IPv6 Subnet/Blocks/pool from their USP(upstream-service-provider) IPv6 Assigning Authority, OR, (c) have obtained /32 /48 /56 /60 or /64 etc IPv6 Subnet/Blocks/pool from related regional Registries (RIR) under IANA . VPS-Provider's ISP ( or VPS-provider's USP ) must Sub-Delegate Reverse-Zone for the assigned/obtained IPv6 subnet/blocks toward the VPS-Provider's DNS-NameServers ( or toward the Client's/User's/Customer's DNS-NameServers ) . Then such VPS-Providers can further SUB-DELEGATE (Reverse-Zones) for further fractional/portion of IPv6 subnet/block (from their own pool) toward their Client/User/VPS domain/zone's DNS-NameServer . After setting up DNS-NameServer ( Reverse-Zone Delegation ) to point toward the next down-level NameServer ( Client's/Customer's DNS-NameServer ) , VPS-Provider need to configure their DHCPv6 ( or SLAAC, etc ) allocation server, & allocate a fractional SUBNET from their primary SUBNET pool, toward the IPv6-enaled network-interface of Client's/Customer's VPS.

    IPv6 Reverse-Zone Sub-Delegation Setup Process is similar ( though not exactly same ) to the process of Setting up a IPv4 Reverse-Zone Sub-Delegation for a /24 /30 etc IPv4 SUBNET, toward a Client's/User's/Customer's DNS-NameServers/VPS:
    https://tools.ietf.org/html/rfc8501
    https://tools.ietf.org/html/rfc2317
    https://www.ripe.net/manage-ips-and-asns/db/support/configuring-reverse-dns
    https://simpledns.com/kb/77/how-to-sub-delegate-a-reverse-zone-ipv4
    https://www.netdaily.org/tag/29-classless-reverse-delegation-bind/
    https://serverfault.com/questions/433400/ipv6-reverse-dns-delegation
    https://www.gestioip.net/docu/ipv6_reverse_dns_delegation.html
    https://serverfault.com/questions/521799/delegating-24-and-64-reverse-zones
    https://unix.stackexchange.com/questions/115924/zone-delegation-in-bind
    https://tools.ietf.org/html/rfc4472

    i have copy-pasted various sections from various webpages & written this post message quickly from my own understanding , so there may be mistakes & discontinuity in the flow of submitted message here , sorry about that.


    Please DO NOT MENTION Any VPS-Provider's Name/Plans Who Cannot Provide at-least one IPv6 SUBNET , i understand some VPS-Provider cannot/want-to understand/setup Reverse-Zone Delegation ( thats why i provided extra-notes & links , it is matter of simple few lines in named.conf ) . But please keep in mind , i posted this message only to find-out who or which offer/plan/deal can DELEGATE Reverse-Zone for the assigned IPv6 subnet.

    PLEASE AVOID MENTION of VPS-Providers or Plans/Offers/Deals which include only one/few IPv6-"ADDRESS" or NO-IPv6 or NO-IPv6-Subnet. Thank you.

    AGAIN, PLEASE DON'T MENTION ANY VPS-PROVIDER'S NAME/PLANS WHICH CANNOT PROVIDE ANY IPv6 "SUBNET"/"BLOCK".

    we must go deeper

    long live the full quote.

    Thanked by 2uptime atErik
  • Jake4Jake4 Member
    edited May 2019

    Wtf did you write like 100 line when your only looking to spend less than $24 a year on a 2GB ram KVM VPS.

  • If your willing to double your yearly spend (50usd) you can go with letbox.com and get a solid kvm server and /64 ipv6 range. Current budget your asking is basically impossible for non garbadge host however it's non managed so you have to know how to setup your own networking. Manedged hosting is alot more expensive

    Thanked by 1letbox
Sign In or Register to comment.