Article Details

Original Article Text

Click to Toggle View

Cisco switches hit by reboot loops due to DNS client bug. Multiple Cisco switch models are suddenly experiencing reboot loops after logging fatal DNS client errors, according to reports seen by BleepingComputer. Starting at approximately 2 AM, what appears to be a firmware bug in the switches' internal DNS client service began treating DNS lookup failures as fatal errors, causing affected devices to reboot repeatedly. Switches impacted by the bug are logging fatal errors similar to the following before rebooting: Based on reports from administrators who contacted BleepingComputer, Reddit discussions, and Cisco Community forum [1, 2] posts, the fatal errors originate from the DNSC (DNS Client) task and occur when the switches attempt to resolve "www.cisco.com" and NTP time servers. Administrators report that the reboot cycle repeats every few minutes, severely disrupting network operations. "The cycle repeats every few minutes. This is obviously pretty disruptive and I'm not going to be able to sustain operations like this for very long," a Cisco customer wrote on Reddit. Based on reports, the bug appears to impact a wide range of Cisco switch models, including: Several administrators report that the failures began around the same time across separate networks, suggesting the issue was globally triggered or tied to a time-based condition. While Cisco has not yet publicly disclosed the root cause, BleepingComputer was told that Cisco support acknowledged the issue to at least one customer, stating it affects CBS, SG, and Catalyst 1200/1300 switches. For now, administrators have discovered temporary workarounds that stop the reboot loops, including disabling DNS resolution, disabling SNTP or time synchronization, and blocking outbound internet access from switch management interfaces. Multiple users report that disabling DNS configurations stopped the reboot loops, even when DNS servers were reachable and functioning normally. In Cisco Community forum posts, users also confirmed that removing DNS resolution resolved the reboot loops. BleepingComputer has contacted Cisco for comment and will update this article as more information becomes available. 7 Security Best Practices for MCP As MCP (Model Context Protocol) becomes the standard for connecting LLMs to tools and data, security teams are moving fast to keep these new services safe. This free cheat sheet outlines 7 best practices you can start using today.

Daily Brief Summary

VULNERABILITIES // Cisco Switches Experience Reboot Loops Due to DNS Client Bug

Multiple Cisco switch models are experiencing continuous reboot loops due to a firmware bug in the internal DNS client service.

The issue began at approximately 2 AM and affects switches attempting DNS lookups, causing them to treat failures as fatal errors.

Administrators report significant disruptions to network operations, with reboot cycles occurring every few minutes, impacting business continuity.

Affected models include CBS, SG, and Catalyst 1200/1300 switches, with the problem appearing globally and possibly linked to a time-based condition.

Temporary solutions involve disabling DNS resolution, SNTP, or time synchronization, and blocking outbound internet access from switch management interfaces.

Cisco support has acknowledged the issue, but the root cause remains undisclosed, prompting administrators to seek workarounds.

Continuous monitoring and prompt implementation of temporary fixes are crucial to mitigate operational disruptions until a permanent solution is released.