Maybe this: "Do not use 'local' as a domain name. It will cause local hosts running mDNS (avahi, bonjour, etc.) to be unable to resolve local hosts not running mDNS.”
> On May 13, 2017, at 9:08 AM, Stefan Baur <newsgroups.ma...@stefanbaur.de> > wrote: > > Hi, > > I'm seeing this on 2.3.3-RELEASE and 2.3.4-RELEASE, not sure if older > versions are affected as well. > > I have multiple entries in the Services/DNS Forwarder/Host Overrides > section, all looking similar to this one: > > |wpad|office.local|192.168.2.3|Microsoft Proxy Autoconfiguration| > > When I attach a Client computer to any of the downstream interfaces of > this pfSense installation (it has two), I get: > > nslookup wpad.office.local > Server: 192.168.134.1 > Address: 192.168.134.1#53 > > ** server can't find wpad.office.local: NXDOMAIN > > (192.168.134.1 is the pfSense IP on that network) > > As soon as I log in to the pfSense WebGUI, go to Services/DNS Forwarder, > and hit the "circle arrow" that says "Restart Service", DNS lookups from > the clients start to work. > > Upstream DNS resolving is not affected, though - trying > > nslookup www.google.com > > will give the correct result from the start. > > This somehow doesn't look right. > > Any insights? Bug in pfSense or misconfiguration on my side? > > Kind Regards, > Stefan Baur > _______________________________________________ > pfSense mailing list > https://lists.pfsense.org/mailman/listinfo/list > Support the project with Gold! https://pfsense.org/gold _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
