• Another Outage (Thur 1 Aug)

    From Avon@21:1/101 to All on Wed Jul 31 08:51:21 2024
    It's round two for me at my home with more electrical work to be done, this means another outage of the fsxNet systems I am running.

    Expect things to close down from some time later tonight (my Wednesday) and be down for up to 24 hours.

    Impacted systems

    21:1/100
    21:4/100
    21:1/10
    news.bbs.nz
    ..also seems DNS for fsxnet.nz may be impacted although I'd thought the other name server would have picked up those duties... hmm

    I'll try and post here before I pull the plug this evening.

    it's now 8.50am Wed local time, I won't get to this until sometime after 6pm tonight.

    Best, Paul

    Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Vorlon@21:1/195 to Avon on Wed Jul 31 09:51:14 2024

    Hello Avon!

    31 Jul 24 08:51, you wrote to all:

    ..also seems DNS for fsxnet.nz may be impacted although I'd thought
    the other name server would have picked up those duties... hmm

    The secondary should handle them fine. It's up and running, and the zone file was updated at 7:50am local today with serial '2023004900'



    Vorlon


    --- GoldED+/LNX 1.1.5-b20240302
    * Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (21:1/195)
  • From Avon@21:1/101 to Vorlon on Wed Jul 31 13:46:52 2024
    On 31 Jul 2024 at 09:51a, Vorlon pondered and said...

    the other name server would have picked up those duties... hmm

    The secondary should handle them fine. It's up and running, and the zone file was updated at 7:50am local today with serial '2023004900'

    I'm glad you replied (thanks!)

    Interestingly the fsxnet.nz domain was not resolvable during the outage and I'd thought because of the second name server all would have been OK?

    I'm wondering if somewhere I may need to check I have the correct IP set up for NS2?

    From memory it changed at one stage...

    feel free to netmail/email further if you want to chat 1-1 but it would be good to understand what's up there.

    In about 7-9 hours we'll be back in my second (and hopefully) final power outage. So I'll guess we'll know then too :)

    Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Vorlon@21:1/195 to Avon on Wed Jul 31 13:03:54 2024

    Hello Avon!

    31 Jul 24 13:46, you wrote to me:

    The secondary should handle them fine. It's up and running, and
    the zone file was updated at 7:50am local today with serial
    '2023004900'

    Interestingly the fsxnet.nz domain was not resolvable during the
    outage and I'd thought because of the second name server all would
    have been OK?

    I would have though so as well.

    I'm wondering if somewhere I may need to check I have the correct IP
    set up for NS2?

    You have the correct IP.

    In about 7-9 hours we'll be back in my second (and hopefully) final
    power outage. So I'll guess we'll know then too :)

    My testing from three remote systems show's it's responding to requests and resolving host names.
    On both IPv4 & IPv6.


    admin@shadow:~/ $> host vger.fsxnet.nz ns2.fsxnet.nz
    Using domain server:
    Name: ns2.fsxnet.nz
    Address: 119.42.53.118#53

    vger.fsxnet.nz has IPv6 address 2a01:4f9:c010:1eca::1


    vorlon@emu68k:~/ host tfb.fsxnet.nz ns2.fsxnet.nz
    Using domain server:
    Name: ns2.fsxnet.nz
    Address: 2404:9400:325e:9e00:f1d0:3:633:280#53

    tfb.fsxnet.nz has address 14.201.8.172


    vk3heg@HP:~$ host agency.fsxnet.nz ns2.fsxnet.nz
    Using domain server:
    Name: ns2.fsxnet.nz
    Address: 119.42.53.118#53
    Aliases:

    agency.fsxnet.nz has address 103.193.138.76
    agency.fsxnet.nz has IPv6 address 2407:8b00:1169:900::100






    Vorlon


    --- GoldED+/LNX 1.1.5-b20240302
    * Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (21:1/195)
  • From deon@21:2/116 to Vorlon on Wed Jul 31 23:10:30 2024
    Re: Another Outage (Thur 1 Aug)
    By: Vorlon to Avon on Wed Jul 31 2024 09:51 am

    Howdy,

    ..also seems DNS for fsxnet.nz may be impacted although I'd thought
    the other name server would have picked up those duties... hmm

    The secondary should handle them fine. It's up and running, and the zone file was updated at 7:50am local today with serial '2023004900'

    Something is not happy...

    [deon@vps-7c13b6c6 ~]$ host ns2.fsxnet.nz
    ;; connection timed out; no servers could be reached
    [deon@vps-7c13b6c6 ~]$ host ns1.fsxnet.nz
    ;; connection timed out; no servers could be reached
    [deon@vps-7c13b6c6 ~]$ host -t ns fsxnet.nz
    ;; connection timed out; no servers could be reached



    ...δεσ∩
    --- SBBSecho 3.20-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
  • From Blue White@21:4/134 to Vorlon on Wed Jul 31 08:50:05 2024

    My testing from three remote systems show's it's responding to requests and resolving host names.
    On both IPv4 & IPv6.

    I don't know if you are checking it while he is up or while he is down but at this moment he is down and possumso.fsxnet.nz is not resolving.

    $$
    --- Noddy git-4716e54
    * Origin: possumso.fsxnet.nz * telnet:24/ssh:2122/ftelnet:80 (21:4/134)
  • From Avon@21:1/101 to deon on Thu Aug 1 18:18:23 2024
    On 31 Jul 2024 at 11:10p, deon pondered and said...

    Re: Another Outage (Thur 1 Aug)
    By: Vorlon to Avon on Wed Jul 31 2024 09:51 am

    Howdy,

    ..also seems DNS for fsxnet.nz may be impacted although I'd though the other name server would have picked up those duties... hmm

    The secondary should handle them fine. It's up and running, and the zon file was updated at 7:50am local today with serial '2023004900'

    Something is not happy...

    [deon@vps-7c13b6c6 ~]$ host ns2.fsxnet.nz
    ;; connection timed out; no servers could be reached
    [deon@vps-7c13b6c6 ~]$ host ns1.fsxnet.nz
    ;; connection timed out; no servers could be reached
    [deon@vps-7c13b6c6 ~]$ host -t ns fsxnet.nz
    ;; connection timed out; no servers could be reached

    I'm back up now but also could not resolve fsxnet.nz while I was down.. hmm

    Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to All on Thu Aug 1 18:19:08 2024
    On 31 Jul 2024 at 08:51a, Avon pondered and said...

    It's round two for me at my home with more electrical work to be done, this means another outage of the fsxNet systems I am running.

    Expect things to close down from some time later tonight (my Wednesday) and be down for up to 24 hours.

    Impacted systems

    21:1/100
    21:4/100
    21:1/10
    news.bbs.nz
    ..also seems DNS for fsxnet.nz may be impacted although I'd thought the other name server would have picked up those duties... hmm

    I'll try and post here before I pull the plug this evening.

    it's now 8.50am Wed local time, I won't get to this until sometime after 6pm tonight.

    Best, Paul

    the outage has ended and all systems should be back up..

    now 6.18pm Thur my local time

    Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Blue White@21:4/134 to Avon on Thu Aug 1 07:44:21 2024
    Welcome back. ;)


    --- Talisman v0.53-dev (Linux/armv7l)
    * Origin: possumso.fsxnet.nz * telnet:24/ssh:2122/ftelnet:80 (21:4/134)
  • From Floris van Unen@21:1/146 to Avon on Thu Aug 1 19:54:52 2024

    Hello Avon!

    01 Aug 24 18:18, you wrote to deon:

    as intodns.com sees it, either your glue records or NS records are not correct. Glue records are A records that the registrar hosts for you so that when they state 'your nameservers are ns1 and ns2 in your domain', the client is given the IP addresses for them, since they are in the same domain as the requested domain.

    Good luck,
    regards,
    Floris


    --- GoldED+/LNX 1.1.5--b20170303
    * Origin: ----> Fidian on Azure West-Europe (Holland) IPV6. (21:1/146)
  • From Avon@21:1/101 to Blue White on Fri Aug 2 09:06:12 2024
    On 01 Aug 2024 at 07:44a, Blue White pondered and said...

    Welcome back. ;)

    thanks nice to be here.

    The power cuts related to an electrician coming in to wire up new circuits for a new hot water supply to the house...

    It was just easier to shutter everything the night before and the restart when I got home the following day.

    We now have a new (non leaking and working) hot water cylinder which is always a good thing :)

    Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to Floris van Unen on Fri Aug 2 09:13:03 2024
    On 01 Aug 2024 at 07:54p, Floris van Unen pondered and said...

    as intodns.com sees it, either your glue records or NS records are not correct. Glue records are A records that the registrar hosts for you so that when they state 'your nameservers are ns1 and ns2 in your domain', the client is given the IP addresses for them, since they are in the
    same domain as the requested domain.

    Good luck,
    regards,
    Floris

    thanks Floris and thanks also to Deon and Vorlon... yep glue records for a NS were incorrect I am hopeful this may have now been fixed but it may take a few hours to promulgate and perhaps I should do a test and down the NS I run to make sure :)

    Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Nightfox@21:1/137 to Avon on Thu Aug 1 15:09:06 2024
    Re: Re: Another Outage (Thur 1 Aug)
    By: Avon to Blue White on Fri Aug 02 2024 09:06 am

    We now have a new (non leaking and working) hot water cylinder which is always a good thing :)

    Yep. :)
    Did you consider a tankless one? I think those look pretty cool - No need for a big tank/cylinder, and it heats water on-the-fly.

    Nightfox
    --- SBBSecho 3.20-Linux
    * Origin: Digital Distortion: digdist.synchro.net (21:1/137)
  • From Avon@21:1/101 to Nightfox on Sat Aug 3 17:16:20 2024
    On 01 Aug 2024 at 03:09p, Nightfox pondered and said...

    We now have a new (non leaking and working) hot water cylinder which always a good thing :)

    Yep. :)
    Did you consider a tankless one? I think those look pretty cool - No
    need for a big tank/cylinder, and it heats water on-the-fly.

    We ended up going for one with a heat pump that sits atop of the cylinder... the COP is around 4.5 so 1kw in generates around 4.5kw of heat. It was more expensive to get but should save $$ over the life of the unit.

    Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Vorlon@21:1/196 to Blue White on Sat Aug 3 17:27:40 2024
    Hi Blue white,

    On Wednesday July 31 2024, Blue White said to Vorlon:

    My testing from three remote systems show's it's responding to requests
    and resolving host names.
    On both IPv4 & IPv6.

    I don't know if you are checking it while he is up or while he is down
    but at this moment he is down and possumso.fsxnet.nz is not resolving.

    I was checking with ns2 directly. The issue of nothing resolving has now
    also been fixed!.. So on Avon's next outage, everything should (Fingers crossed) work. #-)

    \/orlon
    aka
    Stephen

    Rocking FSXnet with an Amiga 4000 and Zeus BBS.

    --- Zeus BBS 1.5
    * Origin: -:-- Dragon's Lair --:- dragon.vk3heg.net Prt: 6800 (21:1/196.0)
  • From Vorlon@21:1/196 to deon on Sat Aug 3 17:29:43 2024
    Hi Deon,

    On Wednesday July 31 2024, Deon said to Vorlon:

    The secondary should handle them fine. It's up and running, and the zone
    file was updated at 7:50am local today with serial '2023004900'

    Something is not happy...

    [deon@vps-7c13b6c6 ~]$ host ns2.fsxnet.nz
    ;; connection timed out; no servers could be reached [deon@vps-7c13b6c6
    ~]$ host ns1.fsxnet.nz
    ;; connection timed out; no servers could be reached [deon@vps-7c13b6c6

    As as you now know that something has been poked and probed into working.
    #-;


    \/orlon
    aka
    Stephen

    Rocking FSXnet with an Amiga 4000 and Zeus BBS.

    --- Zeus BBS 1.5
    * Origin: -:-- Dragon's Lair --:- dragon.vk3heg.net Prt: 6800 (21:1/196.0)
  • From Vorlon@21:1/196 to Floris van Unen on Sat Aug 3 17:46:58 2024
    Hi Floris,

    On Thursday August 01 2024, Floris Van Unen said to Avon:

    as intodns.com sees it, either your glue records or NS records are not correct. Glue records are A records that the registrar hosts for you
    so that when they state 'your nameservers are ns1 and ns2 in your domain', the client is given the IP addresses for them, since they are
    in the same domain as the requested domain.

    The ofending party has been put to bed, and given a stern talking to. They promis to keep better track of things in the future and the next outage shouldn't cause things to break and fall on the floor.

    But yes the glue records at the register had wrong data. #-;


    \/orlon
    aka
    Stephen

    Rocking FSXnet with an Amiga 4000 and Zeus BBS.

    --- Zeus BBS 1.5
    * Origin: -:-- Dragon's Lair --:- dragon.vk3heg.net Prt: 6800 (21:1/196.0)
  • From poindexter FORTRAN@21:4/122 to Nightfox on Sat Aug 3 08:39:51 2024
    Re: Re: Another Outage (Thur 1 Aug)
    By: Nightfox to Avon on Thu Aug 01 2024 03:09 pm

    Did you consider a tankless one? I think those look pretty cool - No need for a big tank/cylinder, and it heats water on-the-fly.

    When I remodeled my kitchen, I replaced an older tank heater (was taking up room in my kitchen cabinetry, which made no sense...) with a tankless heater.

    Pros: Lots of hot water

    Cons: Lots of hot water - my kids started taking longer showers when they didn't run out of hot water like they did with the tank heater.

    Needs flushing - my water is particularly hard, I flush my system every 6 months. The process isn't that difficult, you fill a bucket with cleaning solution (or vinegar in a pinch), insert an immersion pump in the bucket, flip two valves to isolate the water supply, then turn on the pump and let it run. After about 20 minutes, replace the solution with water and flush the system.

    It's easier than it sounds. If you have a full-house water filtration/softening system, you can do this once a year.
    They don't solve the issue of long waits for water to heat up at long pipe runs, but there is a way to make water recirculate through the hot water pipes to keep hot water at the tap. We have about a 90 second warm-up time on our downstairs bathroom, I'm considering it.
    --- SBBSecho 3.20-Win32
    * Origin: realitycheckBBS.org -- information is power. (21:4/122)
  • From Avon@21:1/101 to Vorlon on Mon Aug 5 11:05:58 2024
    On 03 Aug 2024 at 05:46p, Vorlon pondered and said...

    But yes the glue records at the register had wrong data. #-;

    Thanks everyone for spotting this, yep should be sorted now, a recent test saw things still running. phew :)

    Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Blue White@21:4/134 to Vorlon on Mon Aug 5 08:35:06 2024
    I was checking with ns2 directly. The issue of nothing resolving has
    now
    also been fixed!.. So on Avon's next outage, everything should
    (Fingers
    crossed) work. #-)

    Good deal! ;)



    --- Talisman v0.53-dev (Linux/armv7l)
    * Origin: possumso.fsxnet.nz * telnet:24/ssh:2122/ftelnet:80 (21:4/134)