It appears that Brotman, Alex <alex_brot...@comcast.com> said: >It was suggested that some additional context may help the conversation a bit. > >In the email world, typically a valid A/MX for the 5321.From Domain is >required for delivery (the envelope sender). Typically, you'll see these as >"alex_brot...@comcast.com" in a valid/good message. There have been two >instances lately where using a wildcard has led to abuse. > >First example: > >thisisawildcardresponse.ph. 3600 IN A 45.79.222.138
There's a bunch of TLD wildcards, a few from sloppiness not removing the collision test records they had when they were new, the rest deliberate. One even has an MX. It seems to me this is shooting yourself in the foot. If it screws up their mail, well, so be it. R's, John *.ARAB has address 127.0.53.53 *.ARAB mail is handled by 10 your-dns-needs-immediate-attention.ARAB. *.PH has address 45.79.222.138 *.VG has address 88.198.29.97 *.WS has address 64.70.19.203 *.WS mail is handled by 1 mail.hope-mail.com. *.XN--FIQS8S is an alias for wildcard.cnnic.cn. wildcard.cnnic.cn has address 218.241.105.10 *.XN--FIQZ9S is an alias for wildcard.cnnic.cn. wildcard.cnnic.cn has address 218.241.105.10 *.XN--NGBRX has address 127.0.53.53 *.XN--NGBRX mail is handled by 10 your-dns-needs-immediate-attention.XN--NGBRX. *.XN--NODE has address 188.93.95.11 _______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
