Securifi Community Forum

Securifi Products => Almond+ => Topic started by: pfworks on September 29, 2014, 01:48:16 pm

Title: R066 upgrade causes local dns to not work
Post by: pfworks on September 29, 2014, 01:48:16 pm
After updating to R066, local dns no longer works. DNS works on the router itself, and internect connectivity works from my connected clients, but dns resolution does not. Downgrading back to R065 does not fix the issue. I did not have time to log in and poke around. Does almod use dnsmasq or something else?
Title: Re: R066 upgrade causes local dns to not work
Post by: LGNilsson on September 30, 2014, 05:05:10 am
This is not a known issue or something we've ever come across for that matter. I'd suggest trying a reset to see if it solves it.
Title: Re: R066 upgrade causes local dns to not work
Post by: tt4me on September 30, 2014, 09:28:34 am
I have had this issue, and one of two things seems to fix it.  If I wait a while (honestly I don't know how long) it starts working again.  Or, if I reboot the client machine, it takes care of the issue.  I can still access each machine via IP, but to use the hostname requires time or a reboot.

This was frustrating at first, but now that I understand it, it's not as big of an issue, but I do use more IP's than hostnames in my scripts and config files.
Title: Re: R066 upgrade causes local dns to not work
Post by: tt4me on September 30, 2014, 09:30:34 am
Oh, and this was an issue for me on R065 as well.  Any time that I reboot the router I have this issue.  Fortunately the router is pretty damned stable, so rebooting has happened only when the power went out or the upgrades.
Title: Re: R066 upgrade causes local dns to not work
Post by: jjoepaulines on September 30, 2014, 10:23:29 am
Almond plus is using dnsmasq ..

Is this happening regularly ? ..

 
Title: Re: R066 upgrade causes local dns to not work
Post by: pfworks on September 30, 2014, 02:56:30 pm
I discovered the problem. After the update, I re-added my static leases, as they no longer showed up in the UI. dnsmasq really, really, hates duplicate entries, and thus wasn't starting. After clearing these out, everything is working normally.