Local domain and search domain not working
Hello,
Trying to setup my Gold SE and on the whole everything seems to be working great except for local domain name and search domain.
It defaults out of the box as 'lan' for both which is okay by me.
Except it doesn't work?
nslookup or ping for any of the devices with the listed local domain name shown is not found.
Except for with instead use ".local" on the end it works but that is not something I have put in anywhere in firewalla.
Just wondering if others encountered something similar or know of a fix?
Thank you
-
The unit is in router mode.
I don't believe any of my devices are using using DOH? and I'm not on any VPN. Essentially I'm doing a swap of my old router to new, I use to have a synology router.
Previously I could just resolve my local devices that I had (e.g. "raspberrypi", "shield") just by their host name
i.e. http://raspberrypi:8323
Those are no longer resolved. I thought maybe it now it has to be "raspberry.lan" but thats not the case either. Which is what the search domain is for right? Any unqualified names is tagged as ".lan" and then it is resolved against the local domain name. But it just seems like it's not working.
-
I am using Linux and Mac OS, both correctly absorb the default search domain from Firewalla.
I checked my raspberry pi units, they all have nothing in their /etc/resolv.conf except for the ip address of Firewalla
On Mac machines their wifi config automatically sets based on what Firewalla defines. I can see this under the DNS settings and viewing the default search domain. This correctly changes but it never worked when it was originally set as 'lan' that came from the firewalla unit.
In saying all that even if those OS(es?) appended .lan by themselves shouldn't this also resolve? Because the .lan local device was defined/registered in firewalla?
-
We are not able to reproduce this issue on MacOS or Linux. I created a case for you. Our engineer would like to take a look from inside. Please watch out for the upcoming email from help@firewalla.com.
Please sign in to leave a comment.
Comments
8 comments