Dear 44Net community,
It’s been just over two months since we launched the new Portal. It came with, as you have seen, some major bumps. Today, ARDC is resolving, at least temporarily, one of those hurdles: administrative access to subdomains.
As of today, anyone who had a subdomain with ampr.org before the launch of the new Portal on April 3, 2024, will, for now, have full access to their DNS records. This includes subdomains that fall outside of our preferred format of callsign.ampr.org.
This administrative access still depends on call sign verification, which requires confirming given name, family name, email, and valid amateur radio license. This step helps us ensure that the network is being used by valid amateur radio operators. During our recent work, we’ve found several bad actors, which is both unfair to the community and a security risk.
We’ve also made a functional change to the portal: once a call sign is verified, you are now automatically able to create a subdomain with the format of callsign.ampr.org. All other new requests for subdomains that fall outside of that format (e.g., foo.ampr.org, which I’ll refer to as nonstandard subdomains for brevity) will require review and approval.
Please note that we will be limiting the number of nonstandard subdomains going forward. Thus, if you have one (or, in some cases, many more), please consider it temporary. You can currently create as many second-level subdomains as you want—e.g., foo.callsign.ampr.org, bar.callsign.ampr.org, etc.
We are working on a more official policy around subdomains using ampr.org. As promised at the recent regional coordinators' meeting, we will ensure you can see this policy before officially implementing it. We will also provide a transition period, likely many months, for users to edit their entries before official deprecation. This is, ultimately, what we should have done initially, and we take responsibility for not following a better process and, instead, rolling out this change without taking proper preparatory steps.
Some of you may be wondering why we are making this change in the first place. It is because, without doing so, we end up in our current and very unwieldy situation: a database of over 51,000 DNS entries, most without knowledge of who they belong to, accumulated over at least a decade, with very few entries currently in use. If we aim to increase the usage of 44Net, then we need a system where we understand ownership and are able to provide an efficient service where we can address problems as they arise.
For now, we hope that this helps to unblock anyone that currently feels blocked, while also providing an ample notice for changes that are coming down the pipeline at a later, though likely not-so-distant date.
If you have questions, please ask.
Many thanks, Rosy
In my opinion for the purposes of tracking ownership, nonstandard subdomains should only exist via a cname record.
Example of Lynwood (doing it correctly in my opinion)
speedtest.ampr.org. 300 IN CNAME kb3vwg-010.ampr.org. kb3vwg-010.ampr.org. 300 IN A 44.60.44.10
In theory speedtest.ampr.org could have a direct A record.. such as speedtest.ampr.org. 300 IN A 44.60.44.10 But that is problematic.
Just my 2 cents.
On Wed, Jun 12, 2024 at 12:11 PM Rosy Schechter - KJ7RYV via 44net < 44net@mailman.ampr.org> wrote:
Dear 44Net community,
It’s been just over two months since we launched the new Portal. It came with, as you have seen, some major bumps. Today, ARDC is resolving, at least temporarily, one of those hurdles: administrative access to subdomains.
As of today, anyone who had a subdomain with ampr.org before the launch of the new Portal on April 3, 2024, will, for now, have full access to their DNS records. This includes subdomains that fall outside of our preferred format of callsign.ampr.org.
This administrative access still depends on call sign verification, which requires confirming given name, family name, email, and valid amateur radio license. This step helps us ensure that the network is being used by valid amateur radio operators. During our recent work, we’ve found several bad actors, which is both unfair to the community and a security risk.
We’ve also made a functional change to the portal: once a call sign is verified, you are now automatically able to create a subdomain with the format of callsign.ampr.org. All other new requests for subdomains that fall outside of that format (e.g., foo.ampr.org, which I’ll refer to as nonstandard subdomains for brevity) will require review and approval.
Please note that we will be limiting the number of nonstandard subdomains going forward. Thus, if you have one (or, in some cases, many more), please consider it temporary. You can currently create as many second-level subdomains as you want—e.g., foo.callsign.ampr.org, bar.callsign.ampr.org, etc.
We are working on a more official policy around subdomains using ampr.org. As promised at the recent regional coordinators' meeting, we will ensure you can see this policy before officially implementing it. We will also provide a transition period, likely many months, for users to edit their entries before official deprecation. This is, ultimately, what we should have done initially, and we take responsibility for not following a better process and, instead, rolling out this change without taking proper preparatory steps.
Some of you may be wondering why we are making this change in the first place. It is because, without doing so, we end up in our current and very unwieldy situation: a database of over 51,000 DNS entries, most without knowledge of who they belong to, accumulated over at least a decade, with very few entries currently in use. If we aim to increase the usage of 44Net, then we need a system where we understand ownership and are able to provide an efficient service where we can address problems as they arise.
For now, we hope that this helps to unblock anyone that currently feels blocked, while also providing an ample notice for changes that are coming down the pipeline at a later, though likely not-so-distant date.
If you have questions, please ask.
Many thanks, Rosy
-- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ardc.net _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
I have not been allowed to make those edits. On Wednesday, June 12, 2024 at 01:36:45 PM EDT, Steve L via 44net 44net@mailman.ampr.org wrote:
In my opinion for the purposes of tracking ownership, nonstandard subdomains should only exist via a cname record. Example of Lynwood (doing it correctly in my opinion) speedtest.ampr.org. 300 IN CNAME kb3vwg-010.ampr.org. kb3vwg-010.ampr.org. 300 IN A 44.60.44.10
In theory speedtest.ampr.org could have a direct A record.. such asspeedtest.ampr.org. 300 IN A 44.60.44.10 But that is problematic.
Just my 2 cents.
On Wed, Jun 12, 2024 at 12:11 PM Rosy Schechter - KJ7RYV via 44net 44net@mailman.ampr.org wrote:
Dear 44Net community,
It’s been just over two months since we launched the new Portal. It came with, as you have seen, some major bumps. Today, ARDC is resolving, at least temporarily, one of those hurdles: administrative access to subdomains.
As of today, anyone who had a subdomain with ampr.org before the launch of the new Portal on April 3, 2024, will, for now, have full access to their DNS records. This includes subdomains that fall outside of our preferred format of callsign.ampr.org.
This administrative access still depends on call sign verification, which requires confirming given name, family name, email, and valid amateur radio license. This step helps us ensure that the network is being used by valid amateur radio operators. During our recent work, we’ve found several bad actors, which is both unfair to the community and a security risk.
We’ve also made a functional change to the portal: once a call sign is verified, you are now automatically able to create a subdomain with the format of callsign.ampr.org. All other new requests for subdomains that fall outside of that format (e.g., foo.ampr.org, which I’ll refer to as nonstandard subdomains for brevity) will require review and approval.
Please note that we will be limiting the number of nonstandard subdomains going forward. Thus, if you have one (or, in some cases, many more), please consider it temporary. You can currently create as many second-level subdomains as you want—e.g., foo.callsign.ampr.org, bar.callsign.ampr.org, etc.
We are working on a more official policy around subdomains using ampr.org. As promised at the recent regional coordinators' meeting, we will ensure you can see this policy before officially implementing it. We will also provide a transition period, likely many months, for users to edit their entries before official deprecation. This is, ultimately, what we should have done initially, and we take responsibility for not following a better process and, instead, rolling out this change without taking proper preparatory steps.
Some of you may be wondering why we are making this change in the first place. It is because, without doing so, we end up in our current and very unwieldy situation: a database of over 51,000 DNS entries, most without knowledge of who they belong to, accumulated over at least a decade, with very few entries currently in use. If we aim to increase the usage of 44Net, then we need a system where we understand ownership and are able to provide an efficient service where we can address problems as they arise.
For now, we hope that this helps to unblock anyone that currently feels blocked, while also providing an ample notice for changes that are coming down the pipeline at a later, though likely not-so-distant date.
If you have questions, please ask.
Many thanks, Rosy
Lynwood,
Please check your tickets, I replied 2 day ago, just waiting on your reply.
73, Chris - G1FEF
On 12 Jun 2024, at 18:43, lleachii--- via 44net 44net@mailman.ampr.org wrote:
I have not been allowed to make those edits.
On Wednesday, June 12, 2024 at 01:36:45 PM EDT, Steve L via 44net 44net@mailman.ampr.org wrote:
In my opinion for the purposes of tracking ownership, nonstandard subdomains should only exist via a cname record.
Example of Lynwood (doing it correctly in my opinion)
speedtest.ampr.org http://speedtest.ampr.org/. 300 IN CNAME kb3vwg-010.ampr.org http://kb3vwg-010.ampr.org/. kb3vwg-010.ampr.org http://kb3vwg-010.ampr.org/. 300 IN A 44.60.44.10
In theory speedtest.ampr.org http://speedtest.ampr.org/ could have a direct A record.. such as speedtest.ampr.org http://speedtest.ampr.org/. 300 IN A 44.60.44.10 But that is problematic.
Just my 2 cents.
On Wed, Jun 12, 2024 at 12:11 PM Rosy Schechter - KJ7RYV via 44net <44net@mailman.ampr.org mailto:44net@mailman.ampr.org> wrote: Dear 44Net community,
It’s been just over two months since we launched the new Portal. It came with, as you have seen, some major bumps. Today, ARDC is resolving, at least temporarily, one of those hurdles: administrative access to subdomains.
As of today, anyone who had a subdomain with ampr.org http://ampr.org/ before the launch of the new Portal on April 3, 2024, will, for now, have full access to their DNS records. This includes subdomains that fall outside of our preferred format of callsign.ampr.org http://callsign.ampr.org/.
This administrative access still depends on call sign verification, which requires confirming given name, family name, email, and valid amateur radio license. This step helps us ensure that the network is being used by valid amateur radio operators. During our recent work, we’ve found several bad actors, which is both unfair to the community and a security risk.
We’ve also made a functional change to the portal: once a call sign is verified, you are now automatically able to create a subdomain with the format of callsign.ampr.org http://callsign.ampr.org/. All other new requests for subdomains that fall outside of that format (e.g., foo.ampr.org http://foo.ampr.org/, which I’ll refer to as nonstandard subdomains for brevity) will require review and approval.
Please note that we will be limiting the number of nonstandard subdomains going forward. Thus, if you have one (or, in some cases, many more), please consider it temporary. You can currently create as many second-level subdomains as you want—e.g., foo.callsign.ampr.org http://foo.callsign.ampr.org/, bar.callsign.ampr.org http://bar.callsign.ampr.org/, etc.
We are working on a more official policy around subdomains using ampr.org http://ampr.org/. As promised at the recent regional coordinators' meeting, we will ensure you can see this policy before officially implementing it. We will also provide a transition period, likely many months, for users to edit their entries before official deprecation. This is, ultimately, what we should have done initially, and we take responsibility for not following a better process and, instead, rolling out this change without taking proper preparatory steps.
Some of you may be wondering why we are making this change in the first place. It is because, without doing so, we end up in our current and very unwieldy situation: a database of over 51,000 DNS entries, most without knowledge of who they belong to, accumulated over at least a decade, with very few entries currently in use. If we aim to increase the usage of 44Net, then we need a system where we understand ownership and are able to provide an efficient service where we can address problems as they arise.
For now, we hope that this helps to unblock anyone that currently feels blocked, while also providing an ample notice for changes that are coming down the pipeline at a later, though likely not-so-distant date.
If you have questions, please ask.
Many thanks, Rosy
-- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ardc.net http://ardc.net/ _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org mailto:44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org mailto:44net-leave@mailman.ampr.org _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org mailto:44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org mailto:44net-leave@mailman.ampr.org _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
How about changing the emails sent out from the ticketing system to actually tell us what the action is about? Nebulous "your ticket has been worked on" type messages is wasting time. Allocation request emails used to include the data about the requester and the actual text of the note that they submitted. Now the email just notifies me that a ticket is waiting.
On 6/12/2024 3:16 PM, Chris via 44net wrote:
Lynwood,
Please check your tickets, I replied 2 day ago, just waiting on your reply.
73, Chris - G1FEF
The average user will only have a very small number of tickets open, most likely only 1 or 2 so you would know what it is about, also the email has a link that will take you straight to the ticket, couldn’t be easier!
I personally don't like putting too much information in an insecure format such as emails. Ticket updates may often contain PII which would be inappropriate to include in an email.
73, Chris - G1FEF — ARDC Administrator
Web: https://www.ardc.net
On 12 Jun 2024, at 20:34, Charles J. Hargrove via 44net 44net@mailman.ampr.org wrote:
How about changing the emails sent out from the ticketing system to actually tell us what the action is about? Nebulous "your ticket has been worked on" type messages is wasting time. Allocation request emails used to include the data about the requester and the actual text of the note that they submitted. Now the email just notifies me that a ticket is waiting.
On 6/12/2024 3:16 PM, Chris via 44net wrote:
Lynwood, Please check your tickets, I replied 2 day ago, just waiting on your reply. 73, Chris - G1FEF
-- Charles J. Hargrove - N2NOV NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord.
NYC-ARECS/RACES Nets 441.100/136.5 PL ARnewsline Broadcast Mon. @ 8:00PM NYC-ARECS Weekly Net Mon. @ 8:30PM http://www.nyc-arecs.org
NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32
"Information is the oxygen of the modern age. It seeps through the walls topped by barbed wire, it wafts across the electrified borders." - Ronald Reagan
"The more corrupt the state, the more it legislates." - Tacitus
"Molann an obair an fear" - Irish Saying (The work praises the man.)
"No matter how big and powerful government gets, and the many services it provides, it can never take the place of volunteers." - Ronald Reagan _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
I'm also one who finds generic "your ticket status email has been updated" almost useless, because for a whole host of reasons I may not be in a position to go through the context switch of clicking on a link to check (among other things that can start a journey down a rabbit hole :) ). A bit more information would help, such as:
Title/subject - this helps to re-establish the context of the ticket, especially if one has a couple open.
Status - Is it still open or closed? Nothing worse than going through the motions just to see it's closed, especially if you've indicated the issue is resolved. A status update could be a confirmation that the ticket is closed or ARDC actually does need more information (see below).
Waiting for response/Action required (if ARDC needs you to do something) - Is the ARDC team waiting for a response from you, so the ticket can be progressed? This is probably the most important piece of information for obvious reasons.
No PII there, but enough information to triage the response from the ticketing system from the email alone.
And of course, if that isn't enough, there is always the link to the ticket for further information as you say.
Just a suggestion, in the interests of better accessibility.
On 13/6/24 5:59 am, Chris via 44net wrote:
The average user will only have a very small number of tickets open, most likely only 1 or 2 so you would know what it is about, also the email has a link that will take you straight to the ticket, couldn’t be easier!
I personally don't like putting too much information in an insecure format such as emails. Ticket updates may often contain PII which would be inappropriate to include in an email.
73, Chris - G1FEF — ARDC Administrator
Web: https://www.ardc.net
On 12 Jun 2024, at 20:34, Charles J. Hargrove via 44net 44net@mailman.ampr.org wrote:
How about changing the emails sent out from the ticketing system to actually tell us what the action is about? Nebulous "your ticket has been worked on" type messages is wasting time. Allocation request emails used to include the data about the requester and the actual text of the note that they submitted. Now the email just notifies me that a ticket is waiting.
On 6/12/2024 3:16 PM, Chris via 44net wrote:
Lynwood, Please check your tickets, I replied 2 day ago, just waiting on your reply. 73, Chris - G1FEF
-- Charles J. Hargrove - N2NOV NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord.
NYC-ARECS/RACES Nets 441.100/136.5 PL ARnewsline Broadcast Mon. @ 8:00PM NYC-ARECS Weekly Net Mon. @ 8:30PM http://www.nyc-arecs.org
NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32
"Information is the oxygen of the modern age. It seeps through the walls topped by barbed wire, it wafts across the electrified borders." - Ronald Reagan
"The more corrupt the state, the more it legislates." - Tacitus
"Molann an obair an fear" - Irish Saying (The work praises the man.)
"No matter how big and powerful government gets, and the many services it provides, it can never take the place of volunteers." - Ronald Reagan _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
Chris,
I have logged in and understand that the portal system says "with user". What I do not understand is this - - Is there a policy in place? - Will you then proceed to delete these "non callsign" entries once one it is implemented?
You all may not have noticed, but I'm being very particular NOT to agree to new DNS terms, IP record changes, etc. (i.e. stuff that preexisted your control of this domain and space). Before I post the text (since it's quite similar to what I read posted by an ARDC employee), I will not quote it at this time. Please offer clarity (publicly, because you have said some derogatory things to me before in private which you seem uncourageous to say publicly - so I'm uncomfortable) before I proceed.
I also need ARDC to understand that there will be concerns if you then proceed to delete entries I've made very clear I wish to continue use of (as well as my GOVERNMENTAL RACES SPONSOR). I've explained the nature of your inheritance, but somehow - I need to clarify this seemingly contrary policy before I agree. Please note, my records also show and indicate this "policy" is not because of the numerous amount of DNS records - I will not discuss this further here. Anyone seeing the updates on portal ticket clearing statistics can see that. And if your answer is YES to the latter question above - common sense also provides that you can just as well identify and handle them, as you would need to do so to accomplish that task. Yet, a hassle for records I'm in fact attempting to claim (over and over - obviously I'm making records that I'm clamming them)? Since I pray common scene now prevails - I simply ask you not hold my records "hostage" in this commercialization game.
Thanks and 73,
Lynwood KB3VWG (reviewed by a Sensitivity Expert, please be courageous and secretly report the entire text as a Code of Conduct violation if you desire, including this disclaimer to show your ignorance - yes this portion was reviewed as well)
On Wednesday, June 12, 2024 at 03:17:04 PM EDT, Chris via 44net 44net@mailman.ampr.org wrote:
Lynwood, Please check your tickets, I replied 2 day ago, just waiting on your reply. 73,Chris - G1FEF
On 12 Jun 2024, at 18:43, lleachii--- via 44net 44net@mailman.ampr.org wrote: I have not been allowed to make those edits. On Wednesday, June 12, 2024 at 01:36:45 PM EDT, Steve L via 44net 44net@mailman.ampr.org wrote:
In my opinion for the purposes of tracking ownership, nonstandard subdomains should only exist via a cname record. Example of Lynwood (doing it correctly in my opinion) speedtest.ampr.org. 300 IN CNAME kb3vwg-010.ampr.org. kb3vwg-010.ampr.org. 300 IN A 44.60.44.10
In theory speedtest.ampr.org could have a direct A record.. such asspeedtest.ampr.org. 300 IN A 44.60.44.10 But that is problematic.
Just my 2 cents.
On Wed, Jun 12, 2024 at 12:11 PM Rosy Schechter - KJ7RYV via 44net 44net@mailman.ampr.org wrote:
Dear 44Net community,
It’s been just over two months since we launched the new Portal. It came with, as you have seen, some major bumps. Today, ARDC is resolving, at least temporarily, one of those hurdles: administrative access to subdomains.
As of today, anyone who had a subdomain with ampr.org before the launch of the new Portal on April 3, 2024, will, for now, have full access to their DNS records. This includes subdomains that fall outside of our preferred format of callsign.ampr.org.
This administrative access still depends on call sign verification, which requires confirming given name, family name, email, and valid amateur radio license. This step helps us ensure that the network is being used by valid amateur radio operators. During our recent work, we’ve found several bad actors, which is both unfair to the community and a security risk.
We’ve also made a functional change to the portal: once a call sign is verified, you are now automatically able to create a subdomain with the format of callsign.ampr.org. All other new requests for subdomains that fall outside of that format (e.g., foo.ampr.org, which I’ll refer to as nonstandard subdomains for brevity) will require review and approval.
Please note that we will be limiting the number of nonstandard subdomains going forward. Thus, if you have one (or, in some cases, many more), please consider it temporary. You can currently create as many second-level subdomains as you want—e.g., foo.callsign.ampr.org, bar.callsign.ampr.org, etc.
We are working on a more official policy around subdomains using ampr.org. As promised at the recent regional coordinators' meeting, we will ensure you can see this policy before officially implementing it. We will also provide a transition period, likely many months, for users to edit their entries before official deprecation. This is, ultimately, what we should have done initially, and we take responsibility for not following a better process and, instead, rolling out this change without taking proper preparatory steps.
Some of you may be wondering why we are making this change in the first place. It is because, without doing so, we end up in our current and very unwieldy situation: a database of over 51,000 DNS entries, most without knowledge of who they belong to, accumulated over at least a decade, with very few entries currently in use. If we aim to increase the usage of 44Net, then we need a system where we understand ownership and are able to provide an efficient service where we can address problems as they arise.
For now, we hope that this helps to unblock anyone that currently feels blocked, while also providing an ample notice for changes that are coming down the pipeline at a later, though likely not-so-distant date.
If you have questions, please ask.
Many thanks, Rosy
As I've already explained, after a 4-year process, we have been approved for governmental installation. Your so-called "policy" is causing concerns where we actually use RF for emergencies.
- I would need to know when I need to notify organizations that this policy affect their emergency communications plans - I need to schedule this - Our sponsor's approval process may be canceled anyway (i.e. your network seems to just make arbitrary changes without even considering the infrastructure, users, usage, DOWNTIME, etc.) - for something like DNS that usually remains untouched once set
You can just imagine other logistics particular to those points. I'm not sure if you think people merely "play radio" or what infrastructure, but please keep in mind people who really have concerns when you send these emails from California (or whatever radio vacation spot foundation funds accommodate communication). Til this date, nobody has once said when changes may actually affect the users, which I find scary for folks who claim to work professionally in the IT field. Most times, we only find out after issues have occurred/discovered. Why am I the only person who finds that odd?
- KB3VWG
- KB3VWG
On Thursday, June 13, 2024 at 06:11:09 AM EDT, lleachii--- via 44net 44net@mailman.ampr.org wrote:
Chris,
I have logged in and understand that the portal system says "with user". What I do not understand is this - - Is there a policy in place? - Will you then proceed to delete these "non callsign" entries once one it is implemented?
You all may not have noticed, but I'm being very particular NOT to agree to new DNS terms, IP record changes, etc. (i.e. stuff that preexisted your control of this domain and space). Before I post the text (since it's quite similar to what I read posted by an ARDC employee), I will not quote it at this time. Please offer clarity (publicly, because you have said some derogatory things to me before in private which you seem uncourageous to say publicly - so I'm uncomfortable) before I proceed.
I also need ARDC to understand that there will be concerns if you then proceed to delete entries I've made very clear I wish to continue use of (as well as my GOVERNMENTAL RACES SPONSOR). I've explained the nature of your inheritance, but somehow - I need to clarify this seemingly contrary policy before I agree. Please note, my records also show and indicate this "policy" is not because of the numerous amount of DNS records - I will not discuss this further here. Anyone seeing the updates on portal ticket clearing statistics can see that. And if your answer is YES to the latter question above - common sense also provides that you can just as well identify and handle them, as you would need to do so to accomplish that task. Yet, a hassle for records I'm in fact attempting to claim (over and over - obviously I'm making records that I'm clamming them)? Since I pray common scene now prevails - I simply ask you not hold my records "hostage" in this commercialization game.
Thanks and 73,
Lynwood KB3VWG (reviewed by a Sensitivity Expert, please be courageous and secretly report the entire text as a Code of Conduct violation if you desire, including this disclaimer to show your ignorance - yes this portion was reviewed as well)
On Wednesday, June 12, 2024 at 03:17:04 PM EDT, Chris via 44net 44net@mailman.ampr.org wrote:
Lynwood, Please check your tickets, I replied 2 day ago, just waiting on your reply. 73,Chris - G1FEF
On 12 Jun 2024, at 18:43, lleachii--- via 44net 44net@mailman.ampr.org wrote: I have not been allowed to make those edits. On Wednesday, June 12, 2024 at 01:36:45 PM EDT, Steve L via 44net 44net@mailman.ampr.org wrote:
In my opinion for the purposes of tracking ownership, nonstandard subdomains should only exist via a cname record. Example of Lynwood (doing it correctly in my opinion) speedtest.ampr.org. 300 IN CNAME kb3vwg-010.ampr.org. kb3vwg-010.ampr.org. 300 IN A 44.60.44.10
In theory speedtest.ampr.org could have a direct A record.. such asspeedtest.ampr.org. 300 IN A 44.60.44.10 But that is problematic.
Just my 2 cents.
On Wed, Jun 12, 2024 at 12:11 PM Rosy Schechter - KJ7RYV via 44net 44net@mailman.ampr.org wrote:
Dear 44Net community,
It’s been just over two months since we launched the new Portal. It came with, as you have seen, some major bumps. Today, ARDC is resolving, at least temporarily, one of those hurdles: administrative access to subdomains.
As of today, anyone who had a subdomain with ampr.org before the launch of the new Portal on April 3, 2024, will, for now, have full access to their DNS records. This includes subdomains that fall outside of our preferred format of callsign.ampr.org.
This administrative access still depends on call sign verification, which requires confirming given name, family name, email, and valid amateur radio license. This step helps us ensure that the network is being used by valid amateur radio operators. During our recent work, we’ve found several bad actors, which is both unfair to the community and a security risk.
We’ve also made a functional change to the portal: once a call sign is verified, you are now automatically able to create a subdomain with the format of callsign.ampr.org. All other new requests for subdomains that fall outside of that format (e.g., foo.ampr.org, which I’ll refer to as nonstandard subdomains for brevity) will require review and approval.
Please note that we will be limiting the number of nonstandard subdomains going forward. Thus, if you have one (or, in some cases, many more), please consider it temporary. You can currently create as many second-level subdomains as you want—e.g., foo.callsign.ampr.org, bar.callsign.ampr.org, etc.
We are working on a more official policy around subdomains using ampr.org. As promised at the recent regional coordinators' meeting, we will ensure you can see this policy before officially implementing it. We will also provide a transition period, likely many months, for users to edit their entries before official deprecation. This is, ultimately, what we should have done initially, and we take responsibility for not following a better process and, instead, rolling out this change without taking proper preparatory steps.
Some of you may be wondering why we are making this change in the first place. It is because, without doing so, we end up in our current and very unwieldy situation: a database of over 51,000 DNS entries, most without knowledge of who they belong to, accumulated over at least a decade, with very few entries currently in use. If we aim to increase the usage of 44Net, then we need a system where we understand ownership and are able to provide an efficient service where we can address problems as they arise.
For now, we hope that this helps to unblock anyone that currently feels blocked, while also providing an ample notice for changes that are coming down the pipeline at a later, though likely not-so-distant date.
If you have questions, please ask.
Many thanks, Rosy
Hello Lynwood,
For the record, I have never made any derogatory remarks to you publicly or in private, you completely misconstrued an offer of help I made for reasons I still do not understand. If you wish to discuss this then I am more than happy to, as I would like to clear up any misunderstandings. Please feel free to contact me off-list as this is not the appropriate place for such discussions.
With regards to the rest of your email, I refer you to Rosy’s email to this list which explains the current situation. I am sure she would be more than happy to answer any questions you may have.
Kind Regards, Chris - G1FEF — ARDC Administrator
Web: https://www.ardc.net
On 13 Jun 2024, at 11:10, lleachii--- via 44net 44net@mailman.ampr.org wrote:
Chris,
I have logged in and understand that the portal system says "with user".
What I do not understand is this - Is there a policy in place? Will you then proceed to delete these "non callsign" entries once one it is implemented?
You all may not have noticed, but I'm being very particular NOT to agree to new DNS terms, IP record changes, etc. (i.e. stuff that preexisted your control of this domain and space). Before I post the text (since it's quite similar to what I read posted by an ARDC employee), I will not quote it at this time. Please offer clarity (publicly, because you have said some derogatory things to me before in private which you seem uncourageous to say publicly - so I'm uncomfortable) before I proceed.
I also need ARDC to understand that there will be concerns if you then proceed to delete entries I've made very clear I wish to continue use of (as well as my GOVERNMENTAL RACES SPONSOR). I've explained the nature of your inheritance, but somehow - I need to clarify this seemingly contrary policy before I agree.
Please note, my records also show and indicate this "policy" is not because of the numerous amount of DNS records - I will not discuss this further here. Anyone seeing the updates on portal ticket clearing statistics can see that. And if your answer is YES to the latter question above - common sense also provides that you can just as well identify and handle them, as you would need to do so to accomplish that task. Yet, a hassle for records I'm in fact attempting to claim (over and over - obviously I'm making records that I'm clamming them)?
Since I pray common scene now prevails - I simply ask you not hold my records "hostage" in this commercialization game.
Thanks and 73,
Lynwood
KB3VWG
(reviewed by a Sensitivity Expert, please be courageous and secretly report the entire text as a Code of Conduct violation if you desire, including this disclaimer to show your ignorance - yes this portion was reviewed as well)
On Wednesday, June 12, 2024 at 03:17:04 PM EDT, Chris via 44net 44net@mailman.ampr.org wrote:
Lynwood,
Please check your tickets, I replied 2 day ago, just waiting on your reply.
73, Chris - G1FEF
On 12 Jun 2024, at 18:43, lleachii--- via 44net 44net@mailman.ampr.org wrote:
I have not been allowed to make those edits.
On Wednesday, June 12, 2024 at 01:36:45 PM EDT, Steve L via 44net 44net@mailman.ampr.org wrote:
In my opinion for the purposes of tracking ownership, nonstandard subdomains should only exist via a cname record.
Example of Lynwood (doing it correctly in my opinion)
speedtest.ampr.org http://speedtest.ampr.org/. 300 IN CNAME kb3vwg-010.ampr.org http://kb3vwg-010.ampr.org/. kb3vwg-010.ampr.org http://kb3vwg-010.ampr.org/. 300 IN A 44.60.44.10
In theory speedtest.ampr.org http://speedtest.ampr.org/ could have a direct A record.. such as speedtest.ampr.org http://speedtest.ampr.org/. 300 IN A 44.60.44.10 But that is problematic.
Just my 2 cents.
On Wed, Jun 12, 2024 at 12:11 PM Rosy Schechter - KJ7RYV via 44net <44net@mailman.ampr.org mailto:44net@mailman.ampr.org> wrote: Dear 44Net community,
It’s been just over two months since we launched the new Portal. It came with, as you have seen, some major bumps. Today, ARDC is resolving, at least temporarily, one of those hurdles: administrative access to subdomains.
As of today, anyone who had a subdomain with ampr.org http://ampr.org/ before the launch of the new Portal on April 3, 2024, will, for now, have full access to their DNS records. This includes subdomains that fall outside of our preferred format of callsign.ampr.org http://callsign.ampr.org/.
This administrative access still depends on call sign verification, which requires confirming given name, family name, email, and valid amateur radio license. This step helps us ensure that the network is being used by valid amateur radio operators. During our recent work, we’ve found several bad actors, which is both unfair to the community and a security risk.
We’ve also made a functional change to the portal: once a call sign is verified, you are now automatically able to create a subdomain with the format of callsign.ampr.org http://callsign.ampr.org/. All other new requests for subdomains that fall outside of that format (e.g., foo.ampr.org http://foo.ampr.org/, which I’ll refer to as nonstandard subdomains for brevity) will require review and approval.
Please note that we will be limiting the number of nonstandard subdomains going forward. Thus, if you have one (or, in some cases, many more), please consider it temporary. You can currently create as many second-level subdomains as you want—e.g., foo.callsign.ampr.org http://foo.callsign.ampr.org/, bar.callsign.ampr.org http://bar.callsign.ampr.org/, etc.
We are working on a more official policy around subdomains using ampr.org http://ampr.org/. As promised at the recent regional coordinators' meeting, we will ensure you can see this policy before officially implementing it. We will also provide a transition period, likely many months, for users to edit their entries before official deprecation. This is, ultimately, what we should have done initially, and we take responsibility for not following a better process and, instead, rolling out this change without taking proper preparatory steps.
Some of you may be wondering why we are making this change in the first place. It is because, without doing so, we end up in our current and very unwieldy situation: a database of over 51,000 DNS entries, most without knowledge of who they belong to, accumulated over at least a decade, with very few entries currently in use. If we aim to increase the usage of 44Net, then we need a system where we understand ownership and are able to provide an efficient service where we can address problems as they arise.
For now, we hope that this helps to unblock anyone that currently feels blocked, while also providing an ample notice for changes that are coming down the pipeline at a later, though likely not-so-distant date.
If you have questions, please ask.
Many thanks, Rosy
-- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ardc.net http://ardc.net/ _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org mailto:44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org mailto:44net-leave@mailman.ampr.org _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org mailto:44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org mailto:44net-leave@mailman.ampr.org _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
44net mailing list -- 44net@mailman.ampr.org mailto:44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org mailto:44net-leave@mailman.ampr.org _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
Since when is it OK to use 44net for any other use than ham experimentation on that IP address space?
If you use a network for experimentation as a primary link for emergency you miss understood the use of the 44net.
Yes it is appealing to do so. But be aware that this network can and will change over the time. Some stuff will break. Some will cease to exist. And new stuff will appear.
ARDC is not a ISP nor a commercial entity that provide professional services for commercial grade networking. If the network infrastructure you use is primary for life safety, better go the commercial route. If you are a BACKUP in case everything else is gone. That is not the same thing, and the authority dealing with ham should better know about it.
This is my opinion of the situation and note ARDC view. I am not talking for them.
Pierre
VE2PF
________________________________________ De : Chris via 44net 44net@mailman.ampr.org Envoyé : 13 juin 2024 06:47 À : lleachii@aol.com Cc : Amprnet 44 Net Objet : [44net] Re: Update re: subdomains
Hello Lynwood,
For the record, I have never made any derogatory remarks to you publicly or in private, you completely misconstrued an offer of help I made for reasons I still do not understand. If you wish to discuss this then I am more than happy to, as I would like to clear up any misunderstandings. Please feel free to contact me off-list as this is not the appropriate place for such discussions.
With regards to the rest of your email, I refer you to Rosy’s email to this list which explains the current situation. I am sure she would be more than happy to answer any questions you may have.
Kind Regards, Chris - G1FEF — ARDC Administrator
On 13 Jun 2024, at 11:10, lleachii--- via 44net 44net@mailman.ampr.org wrote:
Chris,
I have logged in and understand that the portal system says "with user".
What I do not understand is this -
* Is there a policy in place? * Will you then proceed to delete these "non callsign" entries once one it is implemented?
You all may not have noticed, but I'm being very particular NOT to agree to new DNS terms, IP record changes, etc. (i.e. stuff that preexisted your control of this domain and space). Before I post the text (since it's quite similar to what I read posted by an ARDC employee), I will not quote it at this time. Please offer clarity (publicly, because you have said some derogatory things to me before in private which you seem uncourageous to say publicly - so I'm uncomfortable) before I proceed.
I also need ARDC to understand that there will be concerns if you then proceed to delete entries I've made very clear I wish to continue use of (as well as my GOVERNMENTAL RACES SPONSOR). I've explained the nature of your inheritance, but somehow - I need to clarify this seemingly contrary policy before I agree.
Please note, my records also show and indicate this "policy" is not because of the numerous amount of DNS records - I will not discuss this further here. Anyone seeing the updates on portal ticket clearing statistics can see that. And if your answer is YES to the latter question above - common sense also provides that you can just as well identify and handle them, as you would need to do so to accomplish that task. Yet, a hassle for records I'm in fact attempting to claim (over and over - obviously I'm making records that I'm clamming them)?
Since I pray common scene now prevails - I simply ask you not hold my records "hostage" in this commercialization game.
Thanks and 73,
Lynwood
KB3VWG
(reviewed by a Sensitivity Expert, please be courageous and secretly report the entire text as a Code of Conduct violation if you desire, including this disclaimer to show your ignorance - yes this portion was reviewed as well)
On Wednesday, June 12, 2024 at 03:17:04 PM EDT, Chris via 44net 44net@mailman.ampr.org wrote:
Lynwood,
Please check your tickets, I replied 2 day ago, just waiting on your reply.
73, Chris - G1FEF
On 12 Jun 2024, at 18:43, lleachii--- via 44net 44net@mailman.ampr.org wrote:
I have not been allowed to make those edits.
On Wednesday, June 12, 2024 at 01:36:45 PM EDT, Steve L via 44net 44net@mailman.ampr.org wrote:
In my opinion for the purposes of tracking ownership, nonstandard subdomains should only exist via a cname record.
Example of Lynwood (doing it correctly in my opinion)
speedtest.ampr.orghttp://speedtest.ampr.org/. 300 IN CNAME kb3vwg-010.ampr.orghttp://kb3vwg-010.ampr.org/. kb3vwg-010.ampr.orghttp://kb3vwg-010.ampr.org/. 300 IN A 44.60.44.10
In theory speedtest.ampr.orghttp://speedtest.ampr.org/ could have a direct A record.. such as speedtest.ampr.orghttp://speedtest.ampr.org/. 300 IN A 44.60.44.10 But that is problematic.
Just my 2 cents.
On Wed, Jun 12, 2024 at 12:11 PM Rosy Schechter - KJ7RYV via 44net <44net@mailman.ampr.orgmailto:44net@mailman.ampr.org> wrote: Dear 44Net community,
It’s been just over two months since we launched the new Portal. It came with, as you have seen, some major bumps. Today, ARDC is resolving, at least temporarily, one of those hurdles: administrative access to subdomains.
As of today, anyone who had a subdomain with ampr.orghttp://ampr.org/ before the launch of the new Portal on April 3, 2024, will, for now, have full access to their DNS records. This includes subdomains that fall outside of our preferred format of callsign.ampr.orghttp://callsign.ampr.org/.
This administrative access still depends on call sign verification, which requires confirming given name, family name, email, and valid amateur radio license. This step helps us ensure that the network is being used by valid amateur radio operators. During our recent work, we’ve found several bad actors, which is both unfair to the community and a security risk.
We’ve also made a functional change to the portal: once a call sign is verified, you are now automatically able to create a subdomain with the format of callsign.ampr.orghttp://callsign.ampr.org/. All other new requests for subdomains that fall outside of that format (e.g., foo.ampr.orghttp://foo.ampr.org/, which I’ll refer to as nonstandard subdomains for brevity) will require review and approval.
Please note that we will be limiting the number of nonstandard subdomains going forward. Thus, if you have one (or, in some cases, many more), please consider it temporary. You can currently create as many second-level subdomains as you want—e.g., foo.callsign.ampr.orghttp://foo.callsign.ampr.org/, bar.callsign.ampr.orghttp://bar.callsign.ampr.org/, etc.
We are working on a more official policy around subdomains using ampr.orghttp://ampr.org/. As promised at the recent regional coordinators' meeting, we will ensure you can see this policy before officially implementing it. We will also provide a transition period, likely many months, for users to edit their entries before official deprecation. This is, ultimately, what we should have done initially, and we take responsibility for not following a better process and, instead, rolling out this change without taking proper preparatory steps.
Some of you may be wondering why we are making this change in the first place. It is because, without doing so, we end up in our current and very unwieldy situation: a database of over 51,000 DNS entries, most without knowledge of who they belong to, accumulated over at least a decade, with very few entries currently in use. If we aim to increase the usage of 44Net, then we need a system where we understand ownership and are able to provide an efficient service where we can address problems as they arise.
For now, we hope that this helps to unblock anyone that currently feels blocked, while also providing an ample notice for changes that are coming down the pipeline at a later, though likely not-so-distant date.
If you have questions, please ask.
Many thanks, Rosy
-- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ardc.nethttp://ardc.net/ _______________________________________________ 44net mailing list -- 44net@mailman.ampr.orgmailto:44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.orgmailto:44net-leave@mailman.ampr.org _______________________________________________ 44net mailing list -- 44net@mailman.ampr.orgmailto:44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.orgmailto:44net-leave@mailman.ampr.org _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
_______________________________________________ 44net mailing list -- 44net@mailman.ampr.orgmailto:44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.orgmailto:44net-leave@mailman.ampr.org _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
Hello,
here are my practical questions: . How can a French radio amateur request for an IP 44.151 /32 for example ? . Until now, as administrator, I managed the numbering, but I don't know how to do it now. . I used to create DNS in this sub-domain with direct-to-server commands, but now I don't know how.
It's still a big mystery.
Thank's.
Ludovic - F5PBG - Subnet 44.151 in distress... 😉
Hello,
here are my practical questions: . How can a French radio amateur request for an IP 44.151 /32 for example ? . Until now, as administrator, I managed the numbering, but I don't know how to do it now. . I used to create DNS in this sub-domain with direct-to-server commands, but now I don't know how.
It's still a big mystery.
Thank's.
Ludovic - F5PBG - Subnet 44.151 in distress... 😉
If anyone is looking for it, Here is a link to the Portal Guide.
https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-v... portal-2.0-technical-documentation-v3.3-20240401 PDF Document · 2.4 MB
Some of the setup info, like DNS, is in there.
For allowing others to request IP’s from your prefix, you will need to change its “Mode” from “private” to “open”
I’ll make a quick how-to for making that mode change and upload.
Here are a couple of other DNS how-tos

Adam kc7gdy
On Jun 26, 2024, at 11:53 AM, f5pbg--- via 44net 44net@mailman.ampr.org wrote:
Hello,
here are my practical questions: . How can a French radio amateur request for an IP 44.151 /32 for example ? . Until now, as administrator, I managed the numbering, but I don't know how to do it now. . I used to create DNS in this sub-domain with direct-to-server commands, but now I don't know how.
It's still a big mystery.
Thank's.
Ludovic - F5PBG - Subnet 44.151 in distress... 😉 _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
-
Charles J. Hargrove -
Chris -
f5pbg＠free.fr -
lleachii＠aol.com -
Main -
pete M -
Rosy Schechter - KJ7RYV -
Steve L -
Tony Langdon