LAN to LAN pushed to WAN and forwarded to public web server IP address
-
I send traffic (rsync) from one NAS (192.168.1.x) to another NAS (192.168.1.y) and for some reason the traffic is pushed to the WAN and forwarded to the IP address of a web server that held the tld that I removed from pfsense. I cleared the state table a couple times and changed the domain to pfsense.remote.local.lan but it still routes to this IP address. I have no idea how it resolves to this IP address as I have never entered it into pfsense.
Hopefully someone can provide assistance as I am quite stumped.
Thank you in advance!!!
-
@neurotds
So I assume you use the private IP in rsync?
Check how it is resolved. Maybe there is still a DNS entry for it. -
Thank you for the reply. Yes, I use the private IPs in rsync. Are there DNS entries in other locations that the state table?
Thank you again.
-
@neurotds
The question is, how it is resolved on the NAS which is using it.
Check with dig or nslookup, whatever is available there.dig 192.168.1.yPresumably it resolves to a public hostname which itself is resolved to your WAN address.
-
Thank you again for the most recent reply. I did a packet capture on the LAN and it appears pfsense did not release and update its assigned domain. I initially had my public domain assigned to pfsense, but changed it to local. It reflects local on the header when I log in, but the packet capture shows it looking for the A record on the IP of my public server. Is there a specific way to make the pfsense box release and take the new domain?
I cannot understand why this does not affect my PC accessing the NAS boxes. Additionally, the NAS populates the setup box with the IP address of the other NAS - so I know it can see it. The NAS locator software also locates the boxes on the network with no issues.