Unable to update repository pfSense
-
-
@elvisimprsntr said in Unable to update repository pfSense:
From pfSense GUI or CLI, no.
Using Q9 for upstream DNSHow have you configured DNS, resolver or forward? And your clients use pfSense for DNS lookup?
-
@elvisimprsntr If forwarding, ensure DNSSEC is disabled.
Any restrictions on unbound or is it set to listen on All interfaces?
I would next restart DNS Resolver/unbound, or maybe pfSense.
-
- DNS Resolver
- Yes Clients use pfSense
I tried starting unbound. same issue.
I remotely rebooted my fiber modem (NVG599), and released and renewed WAN interface.Seems to be working again.
Running 2.7.2 with all the latest patches.
This just started happening since I applied the latest swath of patches.
It is behaving like something on pfSense crashed or stops working.
When I disable DNSSEC can't resolve static mappings.
https://forum.netgate.com/topic/196269/att-fiber-dns-issue/13
-
@elvisimprsntr said in Unable to update repository pfSense:
This just started happening since I applied the latest swath of patches.
I know it is obvious but I'd revert patches regarding unbound and see what happens.
-
Are clients, which can resolve, using pfSense for DNS or being passed quad9 to use directly?
What is the DNS behaviour setting in General Setup?
-
@stephenw10 said in Unable to update repository pfSense:
Are clients, which can resolve, using pfSense for DNS or being passed quad9 to use directly?
Client are served pfSense LAN IP address
What is the DNS behaviour setting in General Setup?
-
Hmm, and Diag > DNS Lookup just fails for all configured severs? For any fqdn?
-
Correct.
After rebooting my fiber modem, and releasing and renewing the WAN interface it is working again.
To see if it has any affect, I also deleted the IPv6 Q9 DNS servers.
-
Hmm, weird. Hard to imagine what could have caused that for pfSense but not clients behind it.
