..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 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'
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'm wondering if somewhere I may need to check I have the correct IP
set up for NS2?
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.
..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'
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
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
Welcome back. ;)
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
We now have a new (non leaking and working) hot water cylinder which is always a good thing :)
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.
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.
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 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.
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.
But yes the glue records at the register had wrong data. #-;
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. #-)
| Sysop: | Saxainden |
|---|---|
| Location: | Littleton, CO |
| Users: | 30 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 05:35:21 |
| Calls: | 350 |
| Messages: | 36,669 |