fix: [reversedns] fix nameserver fallback when config is an empty dict

[elhoim]

The reversedns module's documented fallback to Google DNS only triggers when the config key is missing entirely:

if request.get("config"):
    if request["config"].get("nameserver"):
        nameservers = []
        nameservers.append(request["config"].get("nameserver"))
        r.nameservers = nameservers
else:
    r.nameservers = ["8.8.8.8"]

If config is present but empty or lacks nameserver (e.g. {"config": {}}), neither branch sets r.nameservers, so the resolver silently falls back to the system's default nameservers instead of the documented 8.8.8.8 fallback.

An analyst who submits {"config": {}} (a common case when a config dict is built but not yet populated, or when only unrelated config keys are set) gets PTR lookups resolved through whatever DNS servers the host happens to use, rather than the documented, predictable 8.8.8.8. This can produce inconsistent or environment-dependent enrichment results, and is surprising given the module's documented behavior.

Fix

Replaced the if/else block with a single expression that falls back to 8.8.8.8 whenever config is absent, config.nameserver is absent, or either is empty/falsy:

r.nameservers = [(request.get("config") or {}).get("nameserver") or "8.8.8.8"]

This is a pure bug fix restoring the module's already-documented fallback behavior; it does not change the documented contract.

Verification

• python -m py_compile misp_modules/modules/expansion/reversedns.py — succeeded.
• flake8 on the changed file — clean (no output).
• Full module test suite — 161 passed, 4 skipped, 5 subtests passed in 23.42s.

Found during a review of the repository; other findings are being submitted as separate PRs.

🤖 Generated with Claude Code

https://claude.ai/code/session_018dfYpyaSZd1nxSRLr8suj8