Good evening,
it's been a while since I had to add/change/delete DNS entries in the ampr.org DNS zone. The email robot I've used in the past seems to have gone. Could someone please point me into the right direction how this is done nowadays?
vy 73 de Marc, LX1DUC
Hi Mark,
Contact me off list for information.
73 Chris - G1FEF
On 22 Sep 2020, at 20:10, Marc, LX1DUC via 44Net 44net@mailman.ampr.org wrote:
Good evening,
it's been a while since I had to add/change/delete DNS entries in the ampr.org DNS zone. The email robot I've used in the past seems to have gone. Could someone please point me into the right direction how this is done nowadays?
vy 73 de Marc, LX1DUC _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Or contact your AMPR coordinator who can make the DNS changes for you.
--David KI6ZHD
On 09/22/2020 12:43 PM, G1FEF via 44Net wrote:
Hi Mark,
Contact me off list for information.
73 Chris - G1FEF
On 22 Sep 2020, at 20:10, Marc, LX1DUC via 44Net 44net@mailman.ampr.org wrote:
Good evening,
it's been a while since I had to add/change/delete DNS entries in the ampr.org DNS zone. The email robot I've used in the past seems to have gone. Could someone please point me into the right direction how this is done nowadays?
vy 73 de Marc, LX1DUC _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Has something changed? I was told 5 years ago when I was allocated my 44-net /24 that we *can't* have rDNS on them?
Though it's something of a moot point now that it's all becoming unusable anyway with rPKI coming in and the whole /8 is being unrouted from the internet :( That was a bit of a surprise at the start of the month when things started going unreachable - Have had to beg more normal IP's from work and start moving all the ham radio projects I host (dstar, aprs, etc here in .au) to 'real' IP space :/ What are others doing to handle the loss of routability of 44-net space? Is there any plan to sort out rPKI for 44-net at some point? I imagine it'd be a crazy job to try and do though..
Cheers,
DG
On Wed, 23 Sep 2020 at 06:21, David Ranch via 44Net 44net@mailman.ampr.org wrote:
Or contact your AMPR coordinator who can make the DNS changes for you.
--David KI6ZHD
On 09/22/2020 12:43 PM, G1FEF via 44Net wrote:
Hi Mark,
Contact me off list for information.
73 Chris - G1FEF
On 22 Sep 2020, at 20:10, Marc, LX1DUC via 44Net <
44net@mailman.ampr.org> wrote:
Good evening,
it's been a while since I had to add/change/delete DNS entries in the
ampr.org DNS zone. The email robot I've used in the past seems to have gone. Could someone please point me into the right direction how this is done nowadays?
vy 73 de Marc, LX1DUC _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
On 24 Sep 2020, at 21:37, Damien Gardner via 44Net 44net@mailman.ampr.org wrote:
Has something changed? I was told 5 years ago when I was allocated my 44-net /24 that we *can't* have rDNS on them?
If you have a BGP announced subnet allocated then we are now allowing delegation of reverse DNS to your own servers. Contact me off list if you want to arrange this.
Though it's something of a moot point now that it's all becoming unusable anyway with rPKI coming in and the whole /8 is being unrouted from the internet :( That was a bit of a surprise at the start of the month when things started going unreachable - Have had to beg more normal IP's from work and start moving all the ham radio projects I host (dstar, aprs, etc here in .au) to 'real' IP space :/ What are others doing to handle the loss of routability of 44-net space? Is there any plan to sort out rPKI for 44-net at some point? I imagine it'd be a crazy job to try and do though..
Perhaps this is specific to your subnet? The subnet I have announced over BGP is reaching far and wide last time I checked.
Cheers, Chris
Cheers,
DG
On Wed, 23 Sep 2020 at 06:21, David Ranch via 44Net 44net@mailman.ampr.org wrote:
Or contact your AMPR coordinator who can make the DNS changes for you.
--David KI6ZHD
On 09/22/2020 12:43 PM, G1FEF via 44Net wrote:
Hi Mark,
Contact me off list for information.
73 Chris - G1FEF
On 22 Sep 2020, at 20:10, Marc, LX1DUC via 44Net <
44net@mailman.ampr.org> wrote:
Good evening,
it's been a while since I had to add/change/delete DNS entries in the
ampr.org DNS zone. The email robot I've used in the past seems to have gone. Could someone please point me into the right direction how this is done nowadays?
vy 73 de Marc, LX1DUC _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
I'm not having any issues neither with my /24, nor do any of the others in Belgium from what I've heard. I know of several that have their /24 routed via vultr and others and haven't heard of any issues as of yet..
73
Ruben ON3RVH
-----Original Message----- From: 44Net 44net-bounces+on3rvh=on3rvh.be@mailman.ampr.org On Behalf Of G1FEF via 44Net Sent: Saturday, September 26, 2020 13:43 To: AMPRNet working group 44net@mailman.ampr.org Cc: G1FEF chris@g1fef.co.uk Subject: Re: [44net] ampr.org DNS and rDNS entries
On 24 Sep 2020, at 21:37, Damien Gardner via 44Net 44net@mailman.ampr.org wrote:
Has something changed? I was told 5 years ago when I was allocated my 44-net /24 that we *can't* have rDNS on them?
If you have a BGP announced subnet allocated then we are now allowing delegation of reverse DNS to your own servers. Contact me off list if you want to arrange this.
Though it's something of a moot point now that it's all becoming unusable anyway with rPKI coming in and the whole /8 is being unrouted from the internet :( That was a bit of a surprise at the start of the month when things started going unreachable - Have had to beg more normal IP's from work and start moving all the ham radio projects I host (dstar, aprs, etc here in .au) to 'real' IP space :/ What are others doing to handle the loss of routability of 44-net space? Is there any plan to sort out rPKI for 44-net at some point? I imagine it'd be a crazy job to try and do though..
Perhaps this is specific to your subnet? The subnet I have announced over BGP is reaching far and wide last time I checked.
Cheers, Chris
Cheers,
DG
On Wed, 23 Sep 2020 at 06:21, David Ranch via 44Net 44net@mailman.ampr.org wrote:
Or contact your AMPR coordinator who can make the DNS changes for you.
--David KI6ZHD
On 09/22/2020 12:43 PM, G1FEF via 44Net wrote:
Hi Mark,
Contact me off list for information.
73 Chris - G1FEF
On 22 Sep 2020, at 20:10, Marc, LX1DUC via 44Net <
44net@mailman.ampr.org> wrote:
Good evening,
it's been a while since I had to add/change/delete DNS entries in the
ampr.org DNS zone. The email robot I've used in the past seems to have gone. Could someone please point me into the right direction how this is done nowadays?
vy 73 de Marc, LX1DUC _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
On Sat, 26 Sep 2020 at 9:44 pm, G1FEF via 44Net 44net@mailman.ampr.org wrote:
If you have a BGP announced subnet allocated then we are now allowing delegation of reverse DNS to your own servers. Contact me off list if you want to arrange this.
oooh, that would be very cool! Although maybe not a lot of point..
Perhaps this is specific to your subnet? The subnet I have announced over BGP is reaching far and wide last time I checked.
Hmm I’m told it’s world wide. All peering exchanges and transit carriers (at least in the APNIC controlled section of the world.) have started enforcing rPKI route signing at the registries at the start of September, though some are doing a soft start with warning emails sent weekly rather than just hard blocking invalid prefixes.
My /24 is no longer accepted on any peering exchange in .au, and only accepted at one of our four transit carriers here. I’m told that on 1st October that carrier will cease accepting the ‘invalid’ prefix, and then 44-net will be no more? :(
Hi,
44-net space is not RPKI invalid, since there is no 44net RPKI. So unless your upstreams require RPKI valid rather than the more normal only drop RPKI invalids, this shouldn't be an issue.
Thanks, Q
On Sat, 26 Sep 2020 at 13:16, Damien Gardner via 44Net < 44net@mailman.ampr.org> wrote:
On Sat, 26 Sep 2020 at 9:44 pm, G1FEF via 44Net 44net@mailman.ampr.org wrote:
If you have a BGP announced subnet allocated then we are now allowing delegation of reverse DNS to your own servers. Contact me off list if you want to arrange this.
oooh, that would be very cool! Although maybe not a lot of point..
Perhaps this is specific to your subnet? The subnet I have announced over BGP is reaching far and wide last time I checked.
Hmm I’m told it’s world wide. All peering exchanges and transit carriers (at least in the APNIC controlled section of the world.) have started enforcing rPKI route signing at the registries at the start of September, though some are doing a soft start with warning emails sent weekly rather than just hard blocking invalid prefixes.
My /24 is no longer accepted on any peering exchange in .au, and only accepted at one of our four transit carriers here. I’m told that on 1st October that carrier will cease accepting the ‘invalid’ prefix, and then 44-net will be no more? :(
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Damien.. I don’t think your prefix will be INVALID as there won’t be another signed VALID object, so will likely be UNKOWN which should continue to be accepted. At lest that’s my understanding.
On 26 Sep 2020, at 13:14, Damien Gardner via 44Net 44net@mailman.ampr.org wrote:
On Sat, 26 Sep 2020 at 9:44 pm, G1FEF via 44Net 44net@mailman.ampr.org wrote:
If you have a BGP announced subnet allocated then we are now allowing delegation of reverse DNS to your own servers. Contact me off list if you want to arrange this.
oooh, that would be very cool! Although maybe not a lot of point..
Perhaps this is specific to your subnet? The subnet I have announced over BGP is reaching far and wide last time I checked.
Hmm I’m told it’s world wide. All peering exchanges and transit carriers (at least in the APNIC controlled section of the world.) have started enforcing rPKI route signing at the registries at the start of September, though some are doing a soft start with warning emails sent weekly rather than just hard blocking invalid prefixes.
My /24 is no longer accepted on any peering exchange in .au, and only accepted at one of our four transit carriers here. I’m told that on 1st October that carrier will cease accepting the ‘invalid’ prefix, and then 44-net will be no more? :(
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
I'm a bit confused. There are several major providers blocking RPKI invalids but not unknowns, and your 44 routes will have the "unknown" state. Do you have any reference to the exact wording that your providers are using?
Zhaofeng / AJ6IA
On Sat, Sep 26, 2020, at 5:14 AM, Damien Gardner via 44Net wrote:
On Sat, 26 Sep 2020 at 9:44 pm, G1FEF via 44Net 44net@mailman.ampr.org wrote:
If you have a BGP announced subnet allocated then we are now allowing delegation of reverse DNS to your own servers. Contact me off list if you want to arrange this.
oooh, that would be very cool! Although maybe not a lot of point..
Perhaps this is specific to your subnet? The subnet I have announced over BGP is reaching far and wide last time I checked.
Hmm I’m told it’s world wide. All peering exchanges and transit carriers (at least in the APNIC controlled section of the world.) have started enforcing rPKI route signing at the registries at the start of September, though some are doing a soft start with warning emails sent weekly rather than just hard blocking invalid prefixes.
My /24 is no longer accepted on any peering exchange in .au, and only accepted at one of our four transit carriers here. I’m told that on 1st October that carrier will cease accepting the ‘invalid’ prefix, and then 44-net will be no more? :(
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Thanks everyone,
From all the replies I got here, I got in touch with all our upstreams and
peering providers before I headed to bed last night, and basically they all came back with the same response - ‘Blocking unknowns would be madness, less than 25% of routes are currently signed, we are NOT going to do that!’. So I will be having a ‘talk’ with our NOC when I get back to work on Tuesday, and find out why exactly my /24 isn’t being propogated to all the places it’s not making it right now. Someone would appear to have messed something up, and is giving the wrong explanation for it!
73’s
Damien / VK2TDG
On Sat, 26 Sep 2020 at 10:29 pm, Zhaofeng Li via 44Net < 44net@mailman.ampr.org> wrote:
I'm a bit confused. There are several major providers blocking RPKI invalids but not unknowns, and your 44 routes will have the "unknown" state. Do you have any reference to the exact wording that your providers are using?
Zhaofeng / AJ6IA
On Sat, Sep 26, 2020, at 5:14 AM, Damien Gardner via 44Net wrote:
On Sat, 26 Sep 2020 at 9:44 pm, G1FEF via 44Net 44net@mailman.ampr.org
wrote:
If you have a BGP announced subnet allocated then we are now allowing
delegation of reverse DNS to your own servers. Contact me off list if
you
want to arrange this.
oooh, that would be very cool! Although maybe not a lot of point..
Perhaps this is specific to your subnet? The subnet I have announced
over
BGP is reaching far and wide last time I checked.
Hmm I’m told it’s world wide. All peering exchanges and transit carriers
(at least in the APNIC controlled section of the world.) have started
enforcing rPKI route signing at the registries at the start of September,
though some are doing a soft start with warning emails sent weekly rather
than just hard blocking invalid prefixes.
My /24 is no longer accepted on any peering exchange in .au, and only
accepted at one of our four transit carriers here. I’m told that on 1st
October that carrier will cease accepting the ‘invalid’ prefix, and then
44-net will be no more? :(
44Net mailing list
44Net@mailman.ampr.org
44Net mailing list
44Net@mailman.ampr.org
On 26/9/20 10:14 pm, Damien Gardner via 44Net wrote:
My /24 is no longer accepted on any peering exchange in .au, and only accepted at one of our four transit carriers here. I’m told that on 1st October that carrier will cease accepting the ‘invalid’ prefix, and then 44-net will be no more? :(
I'm in .au (/24 is hosted in Melbourne), and everything is still working here. My NSP hasn't advised me of any routing issues, present or future.
If you can connect to IRLP reflector 955x, Echolink conferences *VK3JED*. *AUSSIE*, *ALARA* or *HAM*, or D-STAR REF023, then my /24 is being routed correctly. :)
Try doing a reverse on 44.136.33.1 I’ve been doing this for my two /23 and a /24 in .AU
-k9dc
On Sep 26, 2020, at 18:20, Tony Langdon via 44Net 44net@mailman.ampr.org wrote:
On 26/9/20 10:14 pm, Damien Gardner via 44Net wrote:
My /24 is no longer accepted on any peering exchange in .au, and only accepted at one of our four transit carriers here. I’m told that on 1st October that carrier will cease accepting the ‘invalid’ prefix, and then 44-net will be no more? :(
I'm in .au (/24 is hosted in Melbourne), and everything is still working here. My NSP hasn't advised me of any routing issues, present or future.
If you can connect to IRLP reflector 955x, Echolink conferences *VK3JED*. *AUSSIE*, *ALARA* or *HAM*, or D-STAR REF023, then my /24 is being routed correctly. :)
-- 73 de Tony VK3JED/VK3IRL http://vkradio.com
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
On 26/9/20 9:43 pm, G1FEF via 44Net wrote:
On 24 Sep 2020, at 21:37, Damien Gardner via 44Net 44net@mailman.ampr.org wrote:
Has something changed? I was told 5 years ago when I was allocated my 44-net /24 that we *can't* have rDNS on them?
If you have a BGP announced subnet allocated then we are now allowing delegation of reverse DNS to your own servers. Contact me off list if you want to arrange this.
You might hear from me at some stage on this, will have to do a little planning and setting up first.
Though it's something of a moot point now that it's all becoming unusable anyway with rPKI coming in and the whole /8 is being unrouted from the internet :( That was a bit of a surprise at the start of the month when things started going unreachable - Have had to beg more normal IP's from work and start moving all the ham radio projects I host (dstar, aprs, etc here in .au) to 'real' IP space :/ What are others doing to handle the loss of routability of 44-net space? Is there any plan to sort out rPKI for 44-net at some point? I imagine it'd be a crazy job to try and do though..
Perhaps this is specific to your subnet? The subnet I have announced over BGP is reaching far and wide last time I checked.
So is mine. I'd have a lot of hams contacting me if it became unrouteable, given what it hosts (a major IRLP reflector, several Echolink conferences and a bunch of Echolink proxies, to name a few).
I haven’t noticed a loss of connectivity or reachability with my assigned /24. This past week I was running my 44/net hosts a good bit, with package and OS software updates.
On Sat, Sep 26, 2020 at 6:33 AM Damien Gardner via 44Net < 44net@mailman.ampr.org> wrote:
Has something changed? I was told 5 years ago when I was allocated my
44-net /24 that we *can't* have rDNS on them?
Though it's something of a moot point now that it's all becoming unusable
anyway with rPKI coming in and the whole /8 is being unrouted from the
internet :( That was a bit of a surprise at the start of the month when
things started going unreachable - Have had to beg more normal IP's from
work and start moving all the ham radio projects I host (dstar, aprs, etc
here in .au) to 'real' IP space :/ What are others doing to handle the
loss of routability of 44-net space? Is there any plan to sort out rPKI
for 44-net at some point? I imagine it'd be a crazy job to try and do
though..
Cheers,
DG
On Wed, 23 Sep 2020 at 06:21, David Ranch via 44Net < 44net@mailman.ampr.org>
wrote:
Or contact your AMPR coordinator who can make the DNS changes for you.
--David
KI6ZHD
On 09/22/2020 12:43 PM, G1FEF via 44Net wrote:
Hi Mark,
Contact me off list for information.
73
Chris - G1FEF
On 22 Sep 2020, at 20:10, Marc, LX1DUC via 44Net <
44net@mailman.ampr.org> wrote:
Good evening,
it's been a while since I had to add/change/delete DNS entries in the
ampr.org DNS zone. The email robot I've used in the past seems to have
gone. Could someone please point me into the right direction how this is
done nowadays?
vy 73 de Marc, LX1DUC
44Net mailing list
44Net@mailman.ampr.org
44Net mailing list
44Net@mailman.ampr.org
44Net mailing list
44Net@mailman.ampr.org
44Net mailing list
44Net@mailman.ampr.org
-
Chris Lawrence -
Damien Gardner -
Dave Gingrich -
David Ranch -
G1FEF -
Graham Wooden -
Marc, LX1DUC -
Q -
Ruben ON3RVH -
Tony Langdon -
Zhaofeng Li