Problem with connectivity
-
Hi everyone,
I'm not sure if I'm posting this in the right place or not.
Anyway, my problem is concerning and internal FDQN. I have a NAS device I'm trying to connect to VIA SFTP. I can connect to it using the host name by itself but not with the FDQN. Not sure why this is. I just started with pfSense a few days ago. With my old router, it worked fine. Sometimes I work at other sites. I don't want to change the path every time I go to another site and then again when I get back. This is supposed to be automatic, not semi-automatic. Not sure if it's a NAT setting or a firewall setting, both, or neither. Other locations using the same settings work fine using the FDQN. Just the local internal issue.
If someone can point me in the right direction, I'd appreciate it very much. I can provide additional information if needed. Not sure what that would be yet.
On another note, why don't the arrow keys work?
Thanks, Jack
-
@makeitso well does your internal fqdn resolve to its internal IP?
My nas is on 192.168.9.10, it resolves via nas.home.arpa
$ dig nas.home.arpa +short
192.168.9.10What dns is your client using that is trying to access the nas via its fqdn?
As to arrow keys - what??
-
Thanks for the reply!
When I try to resolve the internal hostname.home.arpa, it does not resolve. When I try to resolve the external hostname, it comes back as my external IP address.
I think I need to add a virtual IP or something. Not sure. How did you get yours to resolve? I don't know why it isn't able to work using the external hostname. That's the way I want it to work. Not sure what's blocking it.
The DNS is set to use the provided DNS of my internet provider.
The arrow keys I mentioned are the arrow keys when I posted wouldn't move the cursor. Today, it works normally.
Thanks, Jack
-
@makeitso my nas has a static IP set on it, that 192.168.9.10 - I just set a host override. If your client is not pointing to pfsense IP for dns, then no its not going to be able to resolve your internal fqdn.
My other devices have dhcp reservations which are set to be registered in unbound.
-
@johnpoz I think it may have something to do with the certificate.
I’m not sure it matters if it resolves fully from inside the firewall. I really need it to from the external FQDN though.
I’m going to look into the certificate issue. I’ll post in here how that works out.
Thanks, Jack
-
@makeitso What error do you get? with sftp doesn't really matter if the cert has the name correct or not you can always just accept the cert.
if you are trying to use a home.arpa domain to get to it - what cert are you putting on it. You would need to create your own CA and sign them and then trust the CA.
How about some details of what issue your exactly having..
Hostname by itself wouldn't ever work via dns. That would be via some sort of discovery like mdns or something. For dns to work you would have to auto be adding a suffix, ie your home.arpa
If you want to access it externally you would have to have setup a port forward, etc. I personally would never open up my nas externally - why would you not just vpn to your network if you are remote..
How about some details of what exactly you are trying to do and from where - are you outside your network, or are you inside your network trying to use some external fqdn that points to your wan IP of pfsense?
Does some public fqdn work while your outside your network - and you want to use that internally? Just setup a host override to point host.publicdomain.tld to your internal IP..
-
@johnpoz So I have that working now. It was the certificate.
I’ve been down the rabbit hole of trying to gat a VPN working but now luck so far. Still working on it. I can’t really use one for this task. There are several different places connected in a few different ways so I don’t know how it would have to be setup.
Anyway, thanks for the help, Jack
Privacy Policy · Cookie Policy