NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

mini4mw's avatar
mini4mw
Guide
Mar 22, 2021
Solved

dnsmasq failure

I was running V2.5.1.16 and have been for 6+ months no issue.  The other night the internet went down and I logged into the Orbi via web and verified the provider issue.  While there I noticed the upgrade to 2.6.2.104.  Since nothing was working (internet down) I figured it was a good time to upgrade and via the web upgraded the router and 3 sats.  All came back fine on the new code and later on internet was fine when the provider came back.  

 

Within 24hrs the machines on DHCP stopped having internet access.  Checking things out I found internet was fine but DNS was failing.  Requests to router IP just timing out.  Rebooted and fine.  Within 24hrs it happened again.  Rebooted, searched for issue, enabled telnet to router and started poking around.  Within 24hrs it happened again and this time just restarted dnsmasq via init,d.  I grepped through /var/log but I don't see anything there related to DNS.  init.d doesn't have any status commands for the service and no systemctl so I can't status the service but the pid is there.  Next time it happened I just reloaded the config and that fixed the issue (init,d option to 'reload' instead of 'restart' which just re-reads the config).  It happened the 5th time in almost as many days and I just downgraded to the old code (2.5.1.16) on everything. So far everything is fine.  If someone wants to debug the issue I'd be happen to collect data as time permits.  As a work around while on the new version I can screenscrape to ensure telnet is enabled and run a script to telnet to the router and reload the service as necessary to prevent any outages longer than perhaps 5 minutes.

 

Anyway, something definitely broken with dnsmasq.  I'm sure it passed the mustard to release the code but I've lucked out and have the 'special' setup to cause it to break.  It would be nice if:

1) it would check itself, simple task as mentioned

2) NG allow you to set your own DNS servers and only force dnsmasq when secure functions are enabled that require filtering.

  • based on same thread and update from reddit;

    i upgraded again to 2.6.2.104.  Within 4 hours I had two more DNS outages.  Same as before, DNS lookups to orbi router timing out.  Log into router via telnet, reload the config (I'm not sure if dnsmasq was dead, just started documenting pid after last outage) and it started working again.  On the 3rd outage I turned DST off (Advanced->administration->NTP->uncheck DST).  I reloaded dnsmasq again (no reboots) and so far I've been good for 4 hours.  Hopefully this fixes the issue.  1 hour off doesn't matter too much to me.

13 Replies

    • vajim's avatar
      vajim
      Master

      mini4mw wrote:

      PS, since I've downgraded I haven't had the issue again..


      nice

  • FURRYe38's avatar
    FURRYe38
    Guru - Experienced User

    You can set custom DNS on the RBR under Advanced tab/Internet. 

     

    Be aware there are problems with the user of Traffic Meter. 

    • mini4mw's avatar
      mini4mw
      Guide

      DNS servers from the ISP are not the issue so setting the router DNS servers to specific ones doesnt help.  I would need the ability to change the DHCP DNS server given out so it is not the router/orbi which is causing internet outages when dnsmasq fails to respond to DNS queries.

      • elbrento's avatar
        elbrento
        Initiate

        I'm having this same issue.  I'm on the latest firmware (2.7.2.104), and the issue started last week.  Every few hours DNS stops working, so I telnet in and see something like this at the bottom of /tmp/dnsmasq.log:

         

        Mar 24 18:12:23 dnsmasq[30353]: overflow: 1 log entries lost

         

        I run "/etc/init.d/dnsmasq restart" and that fixes it, but it's obviously a pain to do that repeatedly.  I'm debating adding that command to the crontab so that it auto restarts every hour or so.

         

        I forget when I upgraded to the current firmware, but it definitely wasn't last week as I was out of town when the issues started occuring.

  • What is the status of a fix for the Orbi DNS/DST failure?

     

    Once a workaround was announced, there has been dead air as far as I can tell.