If by work you mean “does it erase the disk”, then yes, sure, it erases the disk, that's exactly what it's for.
It isn't the best way to erase a disk. DBAN writes multiple passes of random data, which is unnecessarily slow and causes unnecessary wear on the disk (that's mostly relevant for SSD). Multiple passes of random data is the paranoid overkill option, but overwriting just once with zeros is just as good unless you're using a 1980s hard disk and facing an adversary with considerable electronics equipment (and even then the recovery possibilities were haphazard).
With an SSD, if you're concerned about someone with a lot of resources trying to recover data, erasing by overwriting is actually not enough, because the SSD keeps some blocks in reserve to manage wear leveling, and overwriting the data that the computer sees doesn't overwrite those blocks, they can be recovered by someone who swaps out the firmware. This is mostly an academic concern, the attack is pretty expensive and low yield (the attacker just gets the bits that chanced to be in the reserve blocks), but the point is that the paranoid overkill option actually underkills. For an SSD, use the secure erase command.
In summary, if you want to wipe the disk so that data can't be recovered, just use the secure erase command (you can use
hdparm to send it), then overwrite with zeros (
cat /dev/zero >/dev/make_sure_you_type_the_correct_device_name).
If you only want to install a different operating system, you don't need to wipe the data. The installer will repartition the disk and create new filesystems.