Jump to content
Reminder, starting today you will no longer be able to login to the forum using your display name, to login you must now use your email address. ×

I seem to keep losing DNS


wrighty338
 Share

Recommended Posts

I usually reboot my R2 daily before work but on the days i forget i seem to be getting about 36 hours since the previous reboot before DNS gives up.

My modem lights are staying on and my work VPN keeps functioning (wifi) but when i try load a page on my PC i cant get to anything without rebooting the R2 - post reboot everything comes back immediately  The network icon on the PC seems to think the connection is still up. I doubt its my provider going down so often but cannot rule it out.

Iv tried my providers DNS and iv manually entered different public DNS address' to try resolve.

The only message in event viewer seems to be: Name resolution for the name wpad timed out after none of the configured DNS servers responded.

This may mean i need to do some network adaptor troubleshooting - one of the suggested resolutions could be to turn off IPv6 - iv done that now and will see if i note an improvement

Has anyone reported anything similar? Any suggestions on any other settings i might be able to change on the R2 to try resolve?

The pc is about to be retired so for now a reboot will suffice and i wont spend too much time on it if the pc is at fault

Link to comment
Share on other sites

2 hours ago, wrighty338 said:

I usually reboot my R2 daily before work but on the days i forget i seem to be getting about 36 hours since the previous reboot before DNS gives up.

My modem lights are staying on and my work VPN keeps functioning (wifi) but when i try load a page on my PC i cant get to anything without rebooting the R2 - post reboot everything comes back immediately  The network icon on the PC seems to think the connection is still up. I doubt its my provider going down so often but cannot rule it out.

Iv tried my providers DNS and iv manually entered different public DNS address' to try resolve.

The only message in event viewer seems to be: Name resolution for the name wpad timed out after none of the configured DNS servers responded.

This may mean i need to do some network adaptor troubleshooting - one of the suggested resolutions could be to turn off IPv6 - iv done that now and will see if i note an improvement

Has anyone reported anything similar? Any suggestions on any other settings i might be able to change on the R2 to try resolve?

The pc is about to be retired so for now a reboot will suffice and i wont spend too much time on it if the pc is at fault

Are you able to get to the DumaOS interface when this happens? If so, would you mind downloading the log file from System Information and send the whole thing over? We can also get a dev to debug that to help with troubleshooting.

Link to comment
Share on other sites

Log attached, it happened again at 20:31 tonight. I tried to connect my phone to wifi at this time and browse but was unable to connect - seems R2 was not happy at this point. 

Iv moved onto google public dns servers now as opposed to the "fastest" servers suggested by Namebench

log-1647894969199.txt

Link to comment
Share on other sites

And again 9:35 this morning, log attached. Work VPN stayed up, PC could not connect to anything and phone could not connect to wifi.

Reverted to upstream DNS now, and also having read a few other threads iv increased the DHCP time to 168 hours. 

no problems found on my network adaptor following troubleshooting last night.

log-1647941791785.txt

Link to comment
Share on other sites

Il see how we get on Liam, Yes its back to default upstream now so im just guessing it points to my providers stuff if nothing is specified.

I was tempted to leave them both enabled and let upstream be the primary and google be the secondary - it seems more resilient that way but back to default for now. 

Link to comment
Share on other sites

1 hour ago, wrighty338 said:

Il see how we get on Liam, Yes its back to default upstream now so im just guessing it points to my providers stuff if nothing is specified.

I was tempted to leave them both enabled and let upstream be the primary and google be the secondary - it seems more resilient that way but back to default for now. 

Yeah it just uses whatever DNS the upstream router/modem uses. I'll let you know once I've heard back from devs! Could you just confirm that the PC is connected to the R2 via wired?

Link to comment
Share on other sites

35 minutes ago, wrighty338 said:

Done, specified google public dns on wired network adaptor

Do you think you could provide us with remote access to your R2 so we can take a look around? To do this, go to Network Settings -> WAN -> Enable remote access to tech support.

Once done, Save Settings and let us know, a dev will then take a look at what's happening.

Link to comment
Share on other sites

23 minutes ago, Netduma Liam said:

Do you think you could provide us with remote access to your R2 so we can take a look around? To do this, go to Network Settings -> WAN -> Enable remote access to tech support.

Once done, Save Settings and let us know, a dev will then take a look at what's happening.

Done, go ahead

Link to comment
Share on other sites

16 hours ago, wrighty338 said:

Solid day today no issues to report - can someone send me a message and let me know what was up or what was changed?

Cheers!

That's great to hear, it looked as though it was to do with how the DNS queries were handled. Let us know if you have any further issues.

Link to comment
Share on other sites

  • 1 month later...

Not sure if this was a one off upstream issue, but i got the same problem once again today. Not sure if iv lost any settings through power cycling the R2 that were applied to fix this last time around. My equipment is power cycled regularly so unsure if this the case but it was the exact same situation as before where my work machine continued on its VPN and i lost everything else.

Fri May  6 14:25:06 2022 daemon.err dnsmasq[3035]: failed to send packet: Resource temporarily unavailable
Fri May  6 14:25:16 2022 daemon.err dnsmasq[3035]: failed to send packet: Resource temporarily unavailable
Fri May  6 14:25:26 2022 daemon.err dnsmasq[3035]: failed to send packet: Resource temporarily unavaila

I came back to reboot the R2 and DNS has come back up while im in a meeting so really not sure but il keep an eye on things the next few days. Iv not touched any settings since last time when things were fixed so it could well have been my provider i guess. 

Link to comment
Share on other sites

  • Administrators

Thanks for that, if you disable it from LAN/WAN see if it makes any difference please as we've been testing that and had some unusual results that could have similar issues to this

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...