Unfortunately, our #DNS provider #Transip does not allow #DNAME records, so the practical use for us (community at https://dewar.nl) is zero (unless we migrate to another provider that supports them, but maybe too much hassle there).
I contacted Transip about this and they were not planning on adding support, but maybe if more people ask about this?
So are you using Transip and would DNAME records be useful for you (for #DKIM) or otherwise, do send them a message about this!
2/2
TIL about #DNS #DNAME records, which are like CNAME records, but then allow forwarding an entire DNS subtree to another name or domain.
This seems perfect for forwarding #DKIM records, e.g. have _domainkey.example.com forward to _domainkey.example.net so both share the same set of mailservers. Using DNAME allows a single record, instead of one record per DKIM selector with CNAME (which does not scale).
What's weird is that this approach does not seem to be mentioned anywhere wrt DKIM?
1/2
Route 53 Resolver DNS Firewall 的 chain 處理
在「Stop the CNAME chain struggle: Simplified management with Route 53 Resolver DNS Firewall」這邊看到的新功能。
說實話... 我早就忘記 Route 53 Resolver DNS Fir
#AWS #CDN #Cloud #Computer #DNS #Murmuring #Network #Security #Service #53 #amazon #aws #cdn #chain #cloud #cname #dname #dns #firewall #record #resolver #route #security #service
ie Taiwan in simplified Chinese is a DNAME for Taiwan in traditional Chinese. Funny the simplified version exists though as Taiwan uses the traditional one
Anyway, nice example of DNAME #DNS
Matthijs Kooijman
Gea-Suan Lin
John Shaft