DNS forwarder doesn't resolve static addresses

tsolrm · Mar 5, 2015, 9:42 AM

Could you please give me an explanation as to what the difference is between setting up a DHCP lease and just entering a host override in the DNS forwarder?

tsolrm · Mar 5, 2015, 11:26 AM

I'm still having issues with the pfsense resolving the name of the NAS device.

So I have added a host override for the host name and IP address of the nas.

Now I can do the following: nslookup 'NAS hostname' and that resolves ok.

However when I type in \hostname into the folder path - it doesn't resolve. But \nasIP works just fine

I'm doing this over OpenVPN

doktornotor · Mar 5, 2015, 11:27 AM

\hostname is WINS. Has nothing to do with the forwarder/resolver. Use FQDNs. Period.

tsolrm · Mar 5, 2015, 11:32 AM

How do I go about doing that please?

doktornotor · Mar 5, 2015, 11:38 AM

You use \hostname.example.com, not \hostname.

tsolrm · Mar 5, 2015, 11:51 AM

That does work. But why does \hostname work over LAN but not over VPN?

doktornotor · Mar 5, 2015, 12:05 PM

Because there's no NetBIOS/WINS over VPN normally. You should not use any such thing anyway.

tsolrm · Mar 5, 2015, 2:37 PM

Is there no way to get this to work?

2chemlud · Mar 5, 2015, 2:41 PM

I have links on my desktops (Win and Linux) to the NASs on the other sides of VPNs, all with the IPs. Doing fine! :D

muswellhillbilly · Mar 5, 2015, 3:58 PM

You need to have a WINS service running on your local server with an entry for the remote NAS device. Then you should be able to resolve \hostname and connect to it. Otherwise, you can just as easily use the FQDN (\hostname.example.com) if you want a quicker solution (assuming you've entered this address in your DNS settings, that is).