I don't view it as a security risk at all. Now, if that domain is yours and it points to a web server I suppose I could cause you some public embarrassment by publishing or emailing:
WeKillLotsOfKittensEveryDay.ochin.org But, it would have a bonus for you. Everyone that fat fingered the first part of www.ochin.org<http://www.ochin.org> would still get there. Now if it is someone else's domain and it is to get their app to work, go for it. No issue at all. From: [email protected] [mailto:[email protected]] On Behalf Of Dave Lum Sent: Friday, September 2, 2016 4:09 PM To: '[email protected]' Subject: [NTSysADM] Wildcard DNS I've never run into this before, but I have a request to create a wildcard DNS entry for something like *.trickstuff.mydomain.com, so the DNS entry would look like *. trickstuff.mydomain.com 23.54.200.44 It seems to work, where I can ping yougoobers.trickstuff.mydomain.com and it resolves as I'd expect. Is there much of a security risk associated with this? Just feels wrong... David Lum Systems Administrator III P: 503.943.2500 E: [email protected]<mailto:[email protected]> A: 1881 SW Naito Parkway, Portland, OR 97201 [Facebook Link]<https://www.facebook.com/OCHINinc>[Twitter Link]<https://twitter.com/ochininc>[Linkedin Link]<http://www.linkedin.com/company/ochin> www.ochin.org<https://www.ochin.org/> [OCHIN email] Attention: Information contained in this message and or attachments is intended only for the recipient(s) named above and may contain confidential and or privileged material that is protected under State or Federal law. If you are not the intended recipient, any disclosure, copying, distribution or action taken on it is prohibited. If you believe you have received this email in error, please contact the sender with a copy to [email protected]<mailto:[email protected]>, delete this email and destroy all copies.
