What attackers do. Attackers change how their malware finds its command and control servers, for example using fast-changing DNS records or domain generation algorithms, so that blocking a single address or domain does not cut them off. This serves Command and Control.
How to defend. Use protective DNS with threat intelligence, block newly registered domains where acceptable, and collect DNS logs centrally. Analytics that detect algorithmically generated domain names and fast-changing DNS records help. Correlate DNS data with endpoint telemetry so each suspicious lookup can be tied to the process that made it.
Signs to look for. Look for many failed lookups for random-looking domains, domains with very short time to live values and frequently changing addresses, and hosts resolving domains nobody else in the organisation uses. A common gap is not analysing failed DNS lookups at all.