There's more to the time required: it starts with
the original DNS update, then that may need to propagate to other servers. Then the DNS
name cache timer has to expire, and finally the 1 hour timeout in PyDECnet. So best case
is a minute or so, worst case might be well over an hour.
paul
On Jan 16, 2023, at 3:40 PM, Wilm Boerhout
<wboerhout(a)gmail.com> wrote:
I may have restarted before the one hour interval expired, never giving the software a
chance to recover. For analysis, I need to know the time the new address was put into
place at Mark’s end.
Groet,
Wilm
(Verstuurd vanaf mijn telefoon, dus wat korter dan gewoonlijk.)
(Sent from my phone, so a bit more compact than usual)
Op 16 jan. 2023 om 21:34 heeft Tomas Prybil
<tomas(a)prybil.se> het volgende geschreven:
cisco GRE tunnel to A34 connected and alive
/t
Den 2023-01-16 17:34 skrev "Mark Berryman" <mark(a)theberrymans.com>
följande:
I had a bit of a go-around with Comcast over the weekend. The end result is that my
addresses have changed. If you are one of my HECnet neighbors, my new addresses are:
IPv4: 73.95.34.4
IPv6: 2601:281:c100:6d0:3870:e9fa:b78e:abd2
These are also always available in DNS as
decnet.theberrymans.com.
Mark Berryman
Area 27
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se
To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se
To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se
To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se
To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se