Well, I now have found something that no longer works after the 1.4.0.49.7-CCR firmware was restored; my SMCD3G can no longer work as a DNS forwarder.
Previously when using the 1.4.0.49.7-CCR firmware, it forwarded all DNS requests to 68.87.68.162 and 68.87.74.162, and it worked properly as a DNS forwarder.
After the recent "upgrade" to the 3.1.4.51.1 firmware, it used 68.87.72.130 and 68.87.77.130, and it still worked properly as a DNS forwarder.
Now after the profile rebuild and reload of the 1.4.0.49.7-CCR firmware, it is setup to use the 75.75.75.75 and 75.75.76.76 servers, but it is not actually able to do DNS resolution. This is probably what Nalez
was referring to in this post: »
Re: [Business] ARP Packets from Comcast are Flooding My LOCAL Ne wherein it was reported that firmware release 3.1.4.51.1 had fixed a problem with the SMCD3G not working properly as a DNS forwarder with Comcast's DNSSEC servers.
I doubt that I will bother to call in to try to get this corrected, because I don't want to have to deal with any more down time if somebody screws it up any worse. I will just make a few local config changes so that nothing is using the SMCD3G as a DNS forwarder.