DNS timeout,DHCP timeout consistently
-
Hi,
I have not been able to work out why I keep losing internet connection as unifi consoles' reasons for this are mainly:
Failure Stage= DNS
Failure Reason=DNS Timeout
Failure Stage= DHCP
Failure Reason=DHCP Timeout
I am using pfsense as my DNS server and gateway. As well as pfblocker.
I have tried different DNS servers, currently I changed it to cloudflare 1.1.1.1 1.0.0.1
From pfsense I don't see anything wrong with it.
The services status dashboard always has green ticks. But the only thing jumping out is the DNSBL yellow exclamation mark error because of feeds not updating. But I fixed it to be a green tick.
The layout is:
HFC to rj45 -> pfsense re0 wan in -> pfsense re1 lan out -> unifi US-16-150W switch -> ap ac + u6 enterprise. Also connected is the gen 2 cloud key. Plus tv and sonos sound bar. Everything else is wifi. Please let me know what information you require for troubleshooting.
Or any suggestions.
Also it crashed/went into panic mode because apparently the config file was missing.Edit: Staying connected with Ethernet works but still experiences the same drop in internet connection as WiFi. The access point WiFi transmition\broadcast drops making it not available to connect to. And then in under a minute to a couple seconds the WiFi broadcast is broadcasting again with internet connection. Its stuck on a working, not working back to working loop.
-
@nrg said in DNS timeout,DHCP timeout consistently:
Con.necting with Ethernet works perfectly
Then how is it a pfsense problem? If dhcp and dns are working fine with wire - then its clearly wireless issue.. Pfsense has no way to know if client is wired or wireless.. To pfsense they are the same.
-
@johnpoz Correction. Ethernet works fine connection wise but still experiences the same problems as the WiFi DNS timeouts DHCP timeouts ect.. It stays connected but receives no internet briefly until it resolves itself for both wifi and ethernet.
Edit: Added a better explanation as an edit. -
@nrg is dns restarting on pfsense? Is the dhcp server?
If your registering dhcp into dns that can restart unbound on every dhcp action. But dhcp even being down wouldn't cause a client that already has a lease to stop working..
Dhcp leases are renewed at the 50% mark and will continue to run until the lease expires, the client would then do a discover.. Look at your dns and dhcp logs.. are you being flooded with dns renews that are not being renewed? As the client gets closer and closer to expire - it will ask more and more often, faster and faster desperately trying to renew, until it finally expires.
While dns restarting could be problematic for internet access and could see that blipping on you if its restarting a lot.. But dhcp could be off for days and would not have a problem - unless your lease is something insanely short. Default is like 2 hours I believe, I have mine set to like 4 days..
