DNS Resolver is not stable

Follow

Trey Gwaltney

• December 09, 2022 15:02

I use a monitoring tool called Uptime Kuma. It has been monitoring my systems and I have been using the names in the machines registration in DHCP <ServerName>.localdomain. The issues is that monitoring system CONSTANTLY has issues getting a resolution. When it does fail, I can go into another system on the networking and do a nslookupo and it reports a failure as well. I can try again in 30 mins and the lookup is working again. Since seeing this issue, I have DNS checker on the the monitor and it report frequent DNS lookup request failures. 

I believe this is an issue with the DNS services in Firewalla. I have have tried Unbound and it is no different. Here are some examples: 

└─(15:50:48)──> nslookup vidm.vrealize.localdomain                                                                                                                 1 ↵ ──(Thu,Dec08)─┘

Server: 192.168.25.1

Address: 192.168.25.1#53

** server can't find vidm.vrealize.localdomain: NXDOMAIN

Shortly later... 

└─(16:00:31)──> nslookup vidm.vrealize.localdomain                                                                                                               130 ↵ ──(Thu,Dec08)─┘

Server: 192.168.25.1

Address: 192.168.25.1#53

Name: vidm.vrealize.localdomain

Address: 192.168.25.95

0

• 

  Firewalla

  • December 09, 2022 16:59

  What is your LAN DNS or ISP DNS? are those local or they are the popular / ISP provided ones? Also, which firewalla are you using? what mode it is running? are you using beta or production?

  0

  Comment actions Permalink
• 

  Trey Gwaltney

  • December 09, 2022 20:08

  LAN DNS: 192.168.25.1 (Firewalla)

  WAN DNS: 8.8.8.8, 8.8.4.4 (Google DNS)

  Firewalla Purple: Box Version 1.9742 (STABLE) 

  Firewalla Mode: Router

  DNS Service: Unbound: All Devices

  DNS Booster: All Devices

  0

  Comment actions Permalink
• 

  Trey Gwaltney

  • December 09, 2022 20:16

  

  0

  Comment actions Permalink
• 

  Firewalla

  • December 09, 2022 21:26

  I created a ticket for you on this, and will get someone to follow up. 

  0

  Comment actions Permalink
• 

  Raul

  • February 20, 2023 03:12

  I've been having this issue for months. It was fixed for a while but the issue came back. The replacement box I received (Different hardware issue) is now also seeing this same exact DNS issue.

  0

  Comment actions Permalink
• 

  Firewalla

  • February 20, 2023 05:53

  What kind of issues are you having? I looked at the OP's ticket, it is related / specific to his network topology. Are you doing the same?

  0

  Comment actions Permalink
• 

  Raul

  • February 20, 2023 12:34

  A similar setup. Support ticket # 60328

  A monitoring tool (PRTG) that monitors devices by DNS lookup.
  Many devices lose their DNS name (but still reachable by ping) every so often (I verify by pinging and then using nslookup).

  0

  Comment actions Permalink
• 

  Rajeev Mehra

  • September 05, 2024 13:49

  I know this is an old thread, but I have the same problem on my FWP. I have a ticket open for over a year now, the tech support people just keep pushing back, saying it works right on the FWP (when they are in there, using their support tunnel) but there is no resolution for DNS on my own network. I guess I should try disabling Unbound on my FWP, maybe that is causing the trouble.

   

   

   

  0

  Comment actions Permalink
• 

  Firewalla

  • September 05, 2024 16:03
  • Edited

  I did see your case, may I know when you did a NSlookup, was server.lan up and running? if you manually ping its IP, does it work? if you query, fire.walla, does it work?

  0

  Comment actions Permalink

Please sign in to leave a comment.