VLLM_ALLOW_LONG_MAX_MODEL_LEN=1 VLLM_WORKER_MULTIPROC_METHOD=spawn vllm serve --model /llm/models/Qwen/Qwen3.8-27B-FP8 --dtype=float16 --enforce-eager --port 8000 --host 0.0.0.0 --trust-remote-code --disable-sliding-window --gpu-memory-util=0.90 --max-num-batched-tokens=8192 --max-model-len=192608 --block-size 64 -tp=2 --speculative-config '{"method":"mtp","num_speculative_tokens":2}' --enable-auto-tool-choice --tool-call-parser qwen3_xml --reasoning-parser qwen3 --max-num-seqs=4 --kv-cache-dtype fp8 

  # `.local` (mDNS) resolution on Ubuntu 24.04 — troubleshooting aide Setup assumed: LAN interface (e.g. `enpXsY`), a Docker bridge (`docker0` — ignore it). Goal: resolve `myserver.local` etc. via mDNS, falling back to a local/unix DNS server for the LAN. ## Symptoms ``` resolvectl query myserver.local myserver.local: resolve call failed: No appropriate name servers or networks for name found ``` ## Diagnose ```bash resolvectl status ``` Read two levels: 1. **Global** — `Protocols: +mDNS` means mDNS is enabled globally. 2. **Per-link** — the LAN interface must show `mDNS/DNS-SD` in `Current Scopes`.    ⚠️ Per-link settings **override** the global section. Typical failure:    global `+mDNS` but the LAN link shows `-mDNS` (another link, e.g. a bridge,    may correctly show `+mDNS`). ## Fix ### 1. Enable mDNS globally (persistent) `/etc/systemd/resolved.conf` (or a drop-in so the main file stays clean): ```bash sudo mkdir -p /etc/systemd/resolved.conf.d s...