Problem
A network share uses DNS-based discovery and resolves to a stale NAS address after appliance replacement, making project mounts fail until caches expire.
Solution
Root Cause / Diagnostic:
Operating systems cache DNS lookups locally (`nscd`, macOS `mDNSResponder`, or Windows DNS Client). When a NAS appliance is replaced or assigned a new IP address, client workstations continue attempting to connect to the cached stale IP address, resulting in failed mount scripts, disconnected shares, and broken NLE media relinks.
Actionable Fix:
1. Local DNS Cache Flush: Flush the local workstation DNS resolver cache (Windows: `ipconfig /flushdns`; macOS: `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`).
2. Static DHCP Reservation Enforcement: Configure static MAC-based IP reservations on your router/DHCP server so NAS appliances retain the identical IP address permanently across hardware upgrades.
3. Hostname Resolution Validation: Execute `ping [NAS_Hostname]` from the workstation terminal to confirm the hostname resolves immediately to the correct, updated IP address.
Pro Tip:
Always assign your NAS a static IP address in your router; if you replace your NAS and its IP changes, cached network names will break your editing drive mounts until you flush your DNS.
Operating systems cache DNS lookups locally (`nscd`, macOS `mDNSResponder`, or Windows DNS Client). When a NAS appliance is replaced or assigned a new IP address, client workstations continue attempting to connect to the cached stale IP address, resulting in failed mount scripts, disconnected shares, and broken NLE media relinks.
Actionable Fix:
1. Local DNS Cache Flush: Flush the local workstation DNS resolver cache (Windows: `ipconfig /flushdns`; macOS: `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`).
2. Static DHCP Reservation Enforcement: Configure static MAC-based IP reservations on your router/DHCP server so NAS appliances retain the identical IP address permanently across hardware upgrades.
3. Hostname Resolution Validation: Execute `ping [NAS_Hostname]` from the workstation terminal to confirm the hostname resolves immediately to the correct, updated IP address.
Pro Tip:
Always assign your NAS a static IP address in your router; if you replace your NAS and its IP changes, cached network names will break your editing drive mounts until you flush your DNS.