said by noisefloor:The CFG file deployed for the D3G in the last year had to be set to 75.75.75.75 for static routing to work right.
Unless you have statics configured I don't see a reason the gateway would have those servers present.
I have no control over that setting. That setting, like many other configurable settings in the SMCD3G-CCR, can only be set by Comcast. The only DNS server setting in the SMCD3G-CCR that the customer can change is the two DNS servers that the SMC's DHCP server assigns to its DHCP clients (that setting does not change the DNS servers that the SMCD3G-CCR uses internally).
FWIW, I do have a /29 static IP block (as is shown in my previous post), but I can't see why that would make any difference. I do know for a fact that I am able to use the 75.75.75.75 and 75.75.76.76 IP addresses because my local DNS server uses those IP addresses for forwarding. And the
ICSI Netalyzr test shows that my local DNS is/was DNSSEC compliant whether I forward to the 75.75.75.75 and 75.75.76.76 IP addresses or to the 68.87.68.162 and 68.87.74.162 IP addresses, or to the SMCD3G's IP address (this is both before and after the new 3.1.4.51.1 firmware was loaded).
My previous post was just to point out that the new 3.1.4.51.1 firmware does not automatically assign the 75.75.75.75 and 75.75.76.76 IP addresses, nor are those specific IP addresses required to use Comcast's DNSSEC servers (the 68.87.68.162 and 68.87.74.162 IP addresses that my SMCD3G gets from Comcast are also Comcast DNSSEC servers, and they work properly as DNSSEC servers).