DNS servers?
-
On my pfSense LAN tab I have the DNS server values set as 8.8.8.8 and 8.8.4.4 (Google) and on the Dashboard is shows the DNS server(s) as 127.0.0.1, 75.75.76.76, 75.75.75.75, 2001:558:feed::2, and 2001:558:feed::1.
I am not sure where the values on the Dashboard came from (Comast DNS servers?) and if I should change them.
I started looking at this because very recently something is going on with my internet. When using Firefox some pages load just fine, others timeout, some only half the page loads. Chrome and my Roku seem to work just fine, so I'm thinking it's not an issue with my Comcast internet connection.
-
Under System - General Setup - DNS Servers, do you have Allow DNS server list to be overridden by DHCP/PPP on WAN checked?
-
Yes.
-
"On my pfSense LAN tab"
Where do you have them set? Do you mean the lan dhcp server? The firewall lan tab? Confused as to where you think you set "8.8.8.8 and 8.8.4.4"
-
Services: DHCP server, LAN tab, DNS servers: 8.8.8.8 and 8.8.4.4.
-
That is what would be handed out to the clients, not what pfsense would use when asked.
-
@KOM:
Under System - General Setup - DNS Servers, do you have Allow DNS server list to be overridden by DHCP/PPP on WAN checked?
Yes.
This is why. Your pfsense router, which is presumably connected to your Comcast modem directly, is getting its IP and DNS servers from Comcast.
What DNS servers are provided to your clients? Type ipconfig -all from the command line to see.
Of course, the next question is do you care. This is almost certainly not causing the problems you're experiencing.
-
Reggie, Yes, my pfsense router is connected directly to my Comcast modem.
'config -all' reports DNS Servers as 8.8.8.8 and 8.8.4.4.
As far as caring, I have no idea what's going on with Firefox and I admit I'm just shooting in the dark as what might be going on. Thought maybe messing with the DNS servers would be easiest if to mess with.
-
Usually when firefox gets weird it's asking for and receiving an AAAA address for a site but there's no IPv6 connectivity. On more than one occasion I have had to go into about:config and set network.dns.disableIPv6 to true until things got back to normal.
