Continuing the discussion from SRV Resource Record supported?:
A portmapper feature would be great.
- Public, open (listening) IPv4 sockets that “connect” to IPv6-only sockets (TCP) so IPv4-only clients can use IPv6-only services without configuring tunnels themselves.
- Applicable to services where latency doesn’t matter that much.
- The user would need to know the external port that has been assigned on the provider’s side (UX and/or API).
- The user defines the target’s hostname and port.
The provider (dynv6) should define bandwidth and aggregate data transmission limits - e.g. per hour - as it causes traffic on the provider’s infrastructure (finite resources).
There are competitors who charge just under €5 per year for one dozen of mapped ports. As dynv6 is free of charge, I don’t think it would be a good idea to introduce this feature if it would add costs.
Personally I’d pay for this service, €6/year max. for DDNS and portmapping combined. And I need this just because one of my (monopoly) ISPs and half of my friends’ ISPs are too lazy to introduce IPv6 for more than seven years already and Teredo doesn’t work reliably / doesn’t work on Android.