Hello, if I understand corrently, the use of CNAME is just a convenience and no technical feature, right?
In lots of examples on the net, a zonefile for a domain might contain things similar to this: @ORIGIN example.com. .. myhost A 1.2.3.4 www CNAME myhost.example.com. www1 CNAME myhost.example.com. someapp CNAME myhost.example.com. xyz CNAME myhost.example.com. ... Often, the webserver and other applications are not actually running on node 1.2.3.4, but are internally portforwarded to some other node, for various reasons. Now we add an IPv6 address for 'myhost'. But portforwarding doesn't work for IPv6. Instead we are required to use different addresses all over, like so: NOT CORRECT: myhost A 1.2.3.4 myhost AAAA 4321::1 www CNAME myhost.example.com. www AAAA 4321::10 ... Or, NOT CORRECT: myhost A 1.2.3.4 myhost AAAA 4321::1 internal AAAA 4321::10 www CNAME4 myhost.example.com. www CNAME6 internal.example.com. ... So, how would you do it? Is there a nice and elegant way? -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
