DNS Attacks
Dangling Records
Let’s say a company sets up a temporary site - julyoffer.company.com - which is only supposed to be active for 1 month and will not be used after that.
Since it’s a temporary site, you might not include it in your main website, but rather make a new microsite. You use the hosting provider hostingco and set up a DNS record like so:
When the julyoffer site is taken down, but the DNS record is left dangling, then you might have a problem. If hostingco recycles the temporary cloud names (temp-1234), then an attacker may be able to set up his own site on temp-1234.hostingco.example
In that case, the attacker could take over traffic coming to julyoffer.example.com. He could use that to host malware on a trusted domain, or conduct a phishing campaign.
Last updated
