Ok,

So for no repeatable/verifable reasons to share I have managed to overcome the host resolution issue.

I don't know what or why, I did try some of the advice proffered though there was little to check or change that I hadn't already.

It's quite possible that the magic simply occurred in the re-boot process, which oddly enough wasn't the 1st reboot in this session of madness.. however it's working again on my end as well so we'll mark it as a success and keep on trucking.

Thanks again for the comments. Something that was discussed off network was the positive attitudes and willingness to lend a though one finds here on fsx. I appreciate it and it's nice to be part of this network.

N2

N2QFD{Queen City BBS}:// "Does this need to be said? Does this need to be said by me? Does this need to be said by me right now?" - Craig Ferguson

--- Mystic BBS v1.12 A48 (Raspberry Pi/32)
* Origin: Queen City BBS (21:1/154)

So for no repeatable/verifable reasons to share I have managed to overcome the host resolution issue.
I don't know what or why, I did try some of the advice proffered though there was little to check or change that I hadn't already.

Good to hear that your issue has be resolved.

I had a similar probem with no-ip. What fixed it for me was going into the DUC program and then goto "FIle - Preferences" Go down to "IP Detection Method" and change it from whatever is checked to the other option. Don't know why it worked for me but It did. Worth a try if it ever happens again.

|02-=|10Cozmo|02=-

... This virus requires Microsoft Windows 3.x

--- Mystic BBS v1.12 A48 (Windows/32)
* Origin: Lunatics Unleashed BBS (21:3/135)

On 28 May 2024, n2qfd said the following...

Ok,

So for no repeatable/verifable reasons to share I have managed to overcome the host resolution issue.

Glad you got it going again.. That is all that matters...

Al

... Press SPACEBAR once to abort, or twice to save changes

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

I had a similar probem with no-ip. What fixed it for me was going into
the DUC program and then goto "FIle - Preferences" Go down to "IP

Don't get me started on the DUC... They have poor instructions for linux and even worse for raspberry pi users like myself. I think the DUC was updated and I don't know that it's available for me yet. They've disregarded that we're not all using RPI4/5 we're not all on 64 bit systems. And I get not wanting to support fringe or antique systems but the PiB3+ is hardly either of those.

Still we're back to the way we were and can't beat that. Outside users were still getting into the system so there was only a perception of outage on my part and it's not like anyone uses Queen City! I'm on 20fb now getting into fsxNet!

Thanks again for jumping into the conversation. Hope I can return the favor some time for someone else.

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)

n2qfd wrote to Cozmo <=-

I had a similar probem with no-ip. What fixed it for me was going into
the DUC program and then goto "FIle - Preferences" Go down to "IP

Don't get me started on the DUC... They have poor instructions
for linux and even worse for raspberry pi users like myself. I
think the DUC was updated and I don't know that it's available
for me yet. They've disregarded that we're not all using RPI4/5
we're not all on 64 bit systems. And I get not wanting to support
fringe or antique systems but the PiB3+ is hardly either of
those.

I've been using the no-ip DUC for years, on Pi2, Pi3, and Pi4, on both
32-bit and 64-bit. Nothing wrong with the instructions at all. You
simply have to compile it on the system you're going to use it on, as per
the instructions. Then set some permissions on the config file and executable, and configure it. All well documented and straightforward.
Once it's compiled/installed/configured, you start it and it does what
it's supposed to do. If you have any specific questions on this, and have followed the instructions, feel free to ask about it, and I'll help if I
can. Again, it's worked here for quite a few years.



... Internal Error: The system has been taken over by sheep at line 19960
=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)