I don't profess to have any crystal ball into the future, or even deep understanding of the ever-evolving world of economics, but I do understand that people need jobs. Despite the increasing capabilities of today's machines, we're a long way of from sitting back and letting technology take care of our needs.

I believe in trying to help in little ways. For example, I don't use self-checkout machines at the supermarket, even if it means I have to stand in line. I don't want to help eliminate someone's job. I have similar feelings about self-serve gas pumps, bank machines, and cleaning up my own table when leaving a fast-food restaurant.

Are my efforts misguided and futile? Perhaps. Nevertheless, I believe that just because a thing CAN be done, that doesn't mean it SHOULD be done. I don't want to see wider replacement of human workers unless something else develops to mitigate further impoverishment of the working class.

Now every man must come at times to the aid of the party through the general precept that ethical behavior demands support of the community. It is by reason of erroneous reasoning of this kind that we become unjust and in general evil, or worse, slytherins;

If you're doing NAT, sure, but some of the affected devices are the routers themselves. As for things being "non-existent", that's besides the point. I'm just pointing out that the situation is more nuanced than "nothing can be done".

Consider that the target of this attack was Dyn. That's Dyn as in "dynamic". A big chunk of their business involves mapping host names to dynamic IP addresses. Caching someone's dynamic IP address for a 30 days may or may not yield the desired result. The fact that you happen to have "zero issues" probably means only that you attempted to connect to exactly "zero" dynamic DNS clients.

There are possible technical solutions. In the case of the Mirai botnet attacks, the released source code identifies the affected devices. Device manufacturers can be mapped to MAC addresses. ISP's could filter traffic from known vulnerable hardware devices to known DDoS attack targets.

Is this an easy solution? No. Is this a comprehensive solution? No. Would ISP's want to take on this responsibility? No. But is it technically possible? Yes.

The problem is this:
Github.com:
Name Server: NS1.P16.DYNECT.NET
Name Server: NS2.P16.DYNECT.NET
Name Server: NS3.P16.DYNECT.NET
Name Server: NS4.P16.DYNECT.NET...

There's nothing wrong with having all your DNS servers under the same subdomain. What matters is what IP addresses those names resolve to. I've seen primary and secondary DNS servers that aren't even on different IPV4 subnets, never mind geographically distant ones.