So something odd tonight.
Queen City uses the no-ip DDNS.NET domain for our forwarding and suddenly I get a message back when I try and log into my BBS that the
host can't be resolved.
Can't see that anything here has changed. I'm into the BBS locally via my VNCviewer connection.
But queencitybbs.ddns.net:607 seems unreachable tonight and I'm not
sure why.
Thought I'd pass along the anomaly.
Did you public IP address change??
Did you public IP address change??
I've got no evidence that it has changed but I have no idea what else it might be.
I've changed nothing to perhaps the ISP has?
I've got no evidence that it has changed but I have no idea what else it might be.
I've changed nothing to perhaps the ISP has?
So, for the fsx group as I'm also having this discussion on 20fb:
I did get back from news from no-ip and the IP address and port were reported ok from them, they were able to get into it.
I tried some experiments here. I used the IP vs using the domain and I was able to bring it right up from my SyncTERM on the office computer
when I can't do the same using the no-ip DNS domain.
I tried accessing it using cellular network on the phone with
ConnectBot app and that worked, I could get in. However, when in local Wi-Fi I can't resolve host again. When I switch to the actual IP
address, again fine business internal to the WLAN.
So, there's something about the no-ip host/domain is seems my local network doesn't like. I'm not really sure why thing is happening or what changed. Could a firewall on the RPI hosting the BBS be the hangup if
it's not my router? Practical upshot I have a path to get in and it would seem external traffic can still get into the BBS so no disruption
of service to the handful of individuals who stop by.
Still, I don't know what changed and I want to get back to where I was yesterday!
Thanks,
N2
Does this need to be said, does this need to be said right now, does this need to be said right now by me? 73 de ^ N2QFD AR SK
--- Mystic BBS v1.12 A48 (Linux/64)
* 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...
Do you have a VPN? Early on, I kept getting the same error because my
VPN had changed my IP (as it was supposed to) NO-IP thought my IP was my ISP provided IP Needless to say they weren't the same so my terminal couldn't connect.
So, for the fsx group as I'm also having this discussion on 20fb:
I tried some experiments here. I used the IP vs using the domain and I was able to bring it right up from my SyncTERM on the office computer
when I can't do the same using the no-ip DNS domain.
I tried accessing it using cellular network on the phone with
ConnectBot app and that worked, I could get in. However, when in local Wi-Fi I can't resolve host again. When I switch to the actual IP
address, again fine business internal to the WLAN.
Still, I don't know what changed and I want to get back to where I was yesterday!
Its always DNS.... :P
Its always DNS.... :P
Sounds like a good slogan for a T-Shirt :)
Its always DNS.... :PSounds like a good slogan for a T-Shirt :)
Its always DNS.... :PSounds like a good slogan for a T-Shirt :)
Funny you should mention that:
https://a.co/d/94YOpUq <--Amazon link
| Sysop: | Sarah |
|---|---|
| Location: | Portland, Oregon |
| Users: | 19 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 54:19:35 |
| Calls: | 126 |
| Calls today: | 126 |
| Files: | 84,009 |
| U/L today: |
5 files (318K bytes) |
| D/L today: |
33 files (8,385K bytes) |
| Messages: | 38,263 |
| Posted today: | 25 |