Not able to post this as reply...
I have tested a few hosts, and as I said the host now has AAAA record
However some of the DNS servers required to look that up does not.
These servers are common for everyone using the CDN, as such I do not see this to be specific to backend.
New test is with gentoo.ipxe.se
;; QUESTION SECTION:
;gentoo.ipxe.se. IN AAAA
;; ANSWER SECTION:
gentoo.ipxe.se. 3596 IN CNAME gentoo-ipxe.azureedge.net.
gentoo-ipxe.azureedge.net. 1796 IN CNAME gentoo-ipxe.afd.azureedge.net.
gentoo-ipxe.afd.azureedge.net. 26 IN CNAME star-azureedge-prod.trafficmanager.net.
star-azureedge-prod.trafficmanager.net. 26 IN CNAME dual.part-0025.t-0009.t-msedge.net.
dual.part-0025.t-0009.t-msedge.net. 102 IN CNAME part-0025.t-0009.t-msedge.net.
part-0025.t-0009.t-msedge.net. 119 IN AAAA 2620:1ec:bdf::53
part-0025.t-0009.t-msedge.net. 119 IN AAAA 2620:1ec:46::53
NS for azureedge.net has proper AAAA records, so no problem so far, verify with: (I will leave out the response. *due to limited message size")
> nslookup -type=NS azureedge.net
NS for trafficmanager.net does NOT have AAAA record
> nslookup -type=NS trafficmanager.net
just to be sure, try these (which have no answer):
> nslookup -type=AAAA tm1.dns-tm.com
> nslookup -type=AAAA tm2.dns-tm.com
> nslookup -type=AAAA tm1.edgedns-tm.info
> nslookup -type=AAAA tm2.edgedns-tm.info
Same for NS t-msedge.net no AAAA
> nslookup -type=NS t-msedge.net
The same DNSs as mentioned previously that are lacking IPv6