Subj : Re: Can't Resolve Host To : n2qfd From : Bucko Date : Mon May 27 2024 09:37 pm On 27 May 2024, n2qfd said the following... n2> So, for the fsx group as I'm also having this discussion on 20fb: n2> n2> I did get back from news from no-ip and the IP address and port were n2> reported ok from them, they were able to get into it. n2> n2> I tried some experiments here. I used the IP vs using the domain and I n2> was able to bring it right up from my SyncTERM on the office computer n2> when I can't do the same using the no-ip DNS domain. n2> I tried accessing it using cellular network on the phone with n2> ConnectBot app and that worked, I could get in. However, when in local n2> Wi-Fi I can't resolve host again. When I switch to the actual IP n2> address, again fine business internal to the WLAN. n2> So, there's something about the no-ip host/domain is seems my local n2> network doesn't like. I'm not really sure why thing is happening or what n2> changed. Could a firewall on the RPI hosting the BBS be the hangup if n2> it's not my router? Practical upshot I have a path to get in and it n2> would seem external traffic can still get into the BBS so no disruption n2> of service to the handful of individuals who stop by. n2> Still, I don't know what changed and I want to get back to where I was n2> yesterday! n2> n2> Thanks, n2> n2> N2 n2> n2> Does this need to be said, does this need to be said right now, does this n2> need to be said right now by me? 73 de ^ N2QFD AR SK n2> n2> --- Mystic BBS v1.12 A48 (Linux/64) n2> * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150) Something just dawned on me... We might be trying to fix something that isn't broken.. In the Mystic settings check the blacklisted IP's and make sure yours is not blacklisted.. If it is, put it on the whitelist so it doesn't happen again... Al .... The caterpillar does all the work but the butterfly gets all the publicity --- Mystic BBS v1.12 A48 (Linux/64) * Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131) .