44net

44net@mailman.ampr.org

3194 discussions

Re: Update re: subdomains
by lleachii＠aol.com 13 Jun '24

13 Jun '24

There is no such thing. Maybe you misunderstand what I'm referring to. We are responsible for our own stations during an emergency in the US (hence why ARDC shouldn't mess with MY settings since I may be disconnected from them when discovering it). I assumed this was international at any given moment. If you have no clue or understanding, you should remain silent in that case. It's easier to be quiet and learn tan to be loud and wrong. -------- Original message --------From: pete M via 44net <44net(a)mailman.ampr.org> Date: 6/13/24 09:53 (GMT-05:00) To: Amprnet 44 Net <44net(a)mailman.ampr.org> Subject: [44net] Re: Update re: subdomains 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.PierreVE2PF________________________________________De : Chris via 44net <44net(a)mailman.ampr.org>Envoyé : 13 juin 2024 06:47À : lleachii(a)aol.comCc : Amprnet 44 NetObjet : [44net] Re: Update re: subdomainsHello 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 AdministratorWeb: https://www.ardc.net/On 13 Jun 2024, at 11:10, lleachii--- via 44net <44net(a)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,LynwoodKB3VWG(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(a)mailman.ampr.org> wrote:Lynwood,Please check your tickets, I replied 2 day ago, just waiting on your reply.73,Chris - G1FEFOn 12 Jun 2024, at 18:43, lleachii--- via 44net <44net(a)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(a)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.10In theory speedtest.ampr.org<http://speedtest.ampr.org/> could have a direct A record.. such asspeedtest.ampr.org<http://speedtest.ampr.org/>. 300 IN A 44.60.44.10But that is problematic.Just my 2 cents.On Wed, Jun 12, 2024 at 12:11 PM Rosy Schechter - KJ7RYV via 44net <44net(a)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 camewith, as you have seen, some major bumps. Today, ARDC is resolving, atleast temporarily, one of those hurdles: administrative access tosubdomains.As of today, anyone who had a subdomain with ampr.org<http://ampr.org/> before the launchof the new Portal on April 3, 2024, will, for now, have full access totheir DNS records. This includes subdomains that fall outside of ourpreferred 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 validamateur radio license. This step helps us ensure that the network isbeing used by valid amateur radio operators. During our recent work,we’ve found several bad actors, which is both unfair to the communityand a security risk.We’ve also made a functional change to the portal: once a call sign isverified, you are now automatically able to create a subdomain with theformat of callsign.ampr.org<http://callsign.ampr.org/>. All other new requests for subdomains thatfall outside of that format (e.g., foo.ampr.org<http://foo.ampr.org/>, which I’ll refer to asnonstandard subdomains for brevity) will require review and approval.Please note that we will be limiting the number of nonstandardsubdomains going forward. Thus, if you have one (or, in some cases, manymore), please consider it temporary. You can currently create as manysecond-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 usingampr.org<http://ampr.org/>. As promised at the recent regional coordinators' meeting, wewill ensure you can see this policy before officially implementing it.We will also provide a transition period, likely many months, for usersto edit their entries before official deprecation. This is, ultimately,what we should have done initially, and we take responsibility for notfollowing a better process and, instead, rolling out this change withouttaking proper preparatory steps.Some of you may be wondering why we are making this change in the firstplace. It is because, without doing so, we end up in our current andvery unwieldy situation: a database of over 51,000 DNS entries, mostwithout knowledge of who they belong to, accumulated over at least adecade, with very few entries currently in use. If we aim to increasethe usage of 44Net, then we need a system where we understand ownershipand are able to provide an efficient service where we can addressproblems as they arise.For now, we hope that this helps to unblock anyone that currently feelsblocked, while also providing an ample notice for changes that arecoming down the pipeline at a later, though likely not-so-distant date.If you have questions, please ask.Many thanks,Rosy--Rosy Schechter - KJ7RYVExecutive DirectorAmateur Radio Digital Communications (ARDC)ardc.net<http://ardc.net/>_______________________________________________44net mailing list -- 44net(a)mailman.ampr.org<mailto:44net@mailman.ampr.org>To unsubscribe send an email to 44net-leave(a)mailman.ampr.org<mailto:44net-leave@mailman.ampr.org>_______________________________________________44net mailing list -- 44net(a)mailman.ampr.org<mailto:44net@mailman.ampr.org>To unsubscribe send an email to 44net-leave(a)mailman.ampr.org<mailto:44net-leave@mailman.ampr.org>_______________________________________________44net mailing list -- 44net(a)mailman.ampr.orgTo unsubscribe send an email to 44net-leave@mailman.ampr.org_______________________________________________44net mailing list -- 44net(a)mailman.ampr.org<mailto:44net@mailman.ampr.org>To unsubscribe send an email to 44net-leave(a)mailman.ampr.org<mailto:44net-leave@mailman.ampr.org>_______________________________________________44net mailing list -- 44net(a)mailman.ampr.orgTo unsubscribe send an email to 44net-leave@mailman.ampr.org_______________________________________________44net mailing list -- 44net(a)mailman.ampr.orgTo unsubscribe send an email to 44net-leave(a)mailman.ampr.org

1 0

Re: Update re: subdomains
by lleachii＠aol.com 13 Jun '24

13 Jun '24

Lastly, I guess it was forgotten we all can access the DNS records. I want to highlight something of major concern.I'm begging Rosy to stop doing this misquote of the original count or records to make it seem as if there's today an issue under a new portal system that now handles DNS records. I have no clue why this falsehood keeps being perpetuated to the 44net family. Again if they can be handled post-policy, they take utlization the same resources/CPU/skill to identify and handle now.- KB3VWG -------- Original message --------From: lleachii--- via 44net <44net(a)mailman.ampr.org> Date: 6/13/24 06:33 (GMT-05:00) To: Chris <chris(a)ardc.net> Cc: Steve L <kb9mwr(a)gmail.com>, Amprnet 44 Net <44net(a)mailman.ampr.org> Subject: [44net] Re: Update re: subdomains 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 plansI need to schedule thisOur 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 setYou 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(a)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,LynwoodKB3VWG(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(a)mailman.ampr.org> wrote: Lynwood,Please check your tickets, I replied 2 day ago, just waiting on your reply.73,Chris - G1FEFOn 12 Jun 2024, at 18:43, lleachii--- via 44net <44net(a)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(a)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.10In theory speedtest.ampr.org could have a direct A record.. such asspeedtest.ampr.org. 300 IN A 44.60.44.10But that is problematic.Just my 2 cents.On Wed, Jun 12, 2024 at 12:11 PM Rosy Schechter - KJ7RYV via 44net <44net(a)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(a)mailman.ampr.org To unsubscribe send an email to 44net-leave(a)mailman.ampr.org _______________________________________________44net mailing list -- 44net(a)mailman.ampr.orgTo unsubscribe send an email to 44net-leave(a)mailman.ampr.org _______________________________________________44net mailing list -- 44net(a)mailman.ampr.orgTo unsubscribe send an email to 44net-leave@mailman.ampr.org_______________________________________________44net mailing list -- 44net(a)mailman.ampr.orgTo unsubscribe send an email to 44net-leave(a)mailman.ampr.org _______________________________________________44net mailing list -- 44net(a)mailman.ampr.orgTo unsubscribe send an email to 44net-leave(a)mailman.ampr.org

1 0

Assistance with Configuring rDNS Records for 44Net Subnets
by Razvan YO6RZV 11 Jun '24

11 Jun '24

Hello everyone, I have a question for those of you who have BGP announced subnets from 44Net, specifically regarding the configuration of rDNS (PTR) records for each IP address within the subnet. Recently, I received an allocation of a /24 subnet, which is announced via my Data Center's ASN. Everything is functioning correctly, but I need to configure rDNS for each IP address. This configuration is essential for hosting email servers to prevent potential issues. Here is a dlint output for my gateway's IP address: root@eye:~# dlint 1.77.32.44.in-addr.arpa ;; dlint version 1.4.0, Copyright (C) 1998 Paul A. Balyoz <pab(a)domtools.com> ;; Dlint comes with ABSOLUTELY NO WARRANTY. ;; This is free software, and you are welcome to redistribute it ;; under certain conditions. Type 'man dlint' for details. ;; command line: /usr/bin/dlint 1.77.32.44.in-addr.arpa ;; flags: inaddr-domain recursive. ;; using dig version 9.9.5 ;; run starting: Fri Jun 7 15:10:37 EEST 2024 ;; ============================================================ ;; Now linting 1.77.32.44.in-addr.arpa ERROR: no name servers found for domain 1.77.32.44.in-addr.arpa === ;; Now linting 32.44.in-addr.arpa ;; Checking serial numbers per nameserver ;; 2024060700 ns1.de.ardc.net. ;; 2024060700 ns.ardc.net. ;; 2024060700 a.gw4.uk. ;; 2024060700 ns2.us.ardc.net. === Based on this output, I believe that the rDNS setup needs to be handled by the ARDC staff. However, I wanted to confirm this to ensure I proceed correctly. I reached out to Chris off-list and received the following response: "You already have the subdomain yo6rzv.ampr.org setup; you can add DNS records under there. For each A record, a PTR record is automatically added in the reverse zone." From my understanding, this does not fully address my requirements, since for example, if IP Address 44.32.77.2 needs to have the rDNS set to -> something.yo44.net, this will not help. I am aware that Chris and the ARDC staff are currently handling a high volume of tickets and requests through the portal. Therefore, I am turning to the community for assistance to avoid adding more to their workload. I appreciate any guidance you can provide and apologize in advance if this question has been addressed previously. I could not find relevant information in my email archive. Thank you for your assistance. Best regards, Razvan - YO6RZV

3 4

git.ampr.org admins?
by kc8qba＠wildtky.com 09 Jun '24

09 Jun '24

Does anyone know who has admin permissions on the git.ampr.org instance? I tried to create a new account but accidentally entered the wrong email address & would like to get it fixed. Best, -Steve kc8qba

3 2

44Net Update, June 7, 2024
by Rebecca Key 07 Jun '24

07 Jun '24

** *Hey Everyone,* *** Below are some updates from this week regarding the 44Net Portal: ** As of today, about 30 new portal tickets remain (40% decrease from last week), and about 266 tickets are open and awaiting response (5% decrease from last week). Since April 3, we have closed 634 tickets (12% increase from last week). For those of you interested in being a beta tester for the 44Net VPN, reach out to Adam at adam(a)ardc.net <mailto:adam@ardc.net>to get set up! Finally, as many of you have asked about ways to help with the portal (https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-… you come across something in the docs that’s not clear or intuitive, or if you have other feedback, please let us know at newportal(a)ardc.net <mailto:newportal@ardc.net>. As always, let us know if you have any questions! 73 and have a great weekend, Rebecca KO4KVG * -- Rebecca Key - KO4KVG Communicaions Manager Amateur Radio Digital Communications (ARDC) ardc.net

1 0

Users Complaining About Domains Failing and No Instructions
by Charles J. Hargrove 07 Jun '24

07 Jun '24

If you go through the list of domain records, you will see many that have not been claimed. Match them up to users who have yet to start or finish the LoT/Trust verification steps and it is still a headache in the making with many more unnecessary tickets that have not even hit yet. As I said many times in the past, get the coordinators on-board so that we can clear the tickets of those who are in our areas. We have acted as mentors and point of contact for many years and know these users quite well. I have one user in NY that is a trustee for two different club calls as well as his own. He finally got his verification tickets through, but now the routing to the two club calls are failing because he did not know what to do about them. Taking this whole process out of the hands of the coordinators has taken my normally less than 30 minute time out of my hands and tossed these users into a faceless mosh pit. Two phone conferences within 10 days last month and there does not seem to be any movement in including the coordinators to make this move quickly. Comments and mea culpas of the April 3rd surprise has not really corrected itself over 60 days later. -- 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

1 0

encap txt file unobtainable
by vk1kw＠netspace.net.au 07 Jun '24

07 Jun '24

Hello Kun, Sunce around May 3 I have been unable to get a copy of the full encap file. I can access the HTML portal ok. My four sources are not working. What am I missing? Mail - no encap file from the portal. Jnos2 wget ftp script I have used for several years has now failed. Unable to manually download encap from the portal as there seems to be no obvious link supplied. Ampr-rip2 is not working and there is very little configuration on the net. I have downloaded the file, installed it and run it but nothing happens. (var/lib/encap.txt file is there empty) Any info from the group on ampr-rip2 setup would be appreciated please. (it is behind a firewall and all other JNOS2 functions are working) Many thanks Rob vk1kw(a)netspace.net.au <mailto:vk1kw@netspace.net.au>

2 1

Re: DNS PTR record
by KUN LIN 03 Jun '24

03 Jun '24

I am thinking about update rDNS for an assigned IP. Kun ________________________________ From: Chris <chris(a)ardc.net> Sent: Monday, June 3, 2024 13:05 To: KUN LIN <dnwk(a)linkun.info> Subject: Re: [44net] DNS PTR record Hello Kun, Yes the PTR record option is fully functional, as are all the record types listed. What are you trying to achieve though? Kind Regards, Chris - G1FEF — ARDC Administrator Web: https://www.ardc.net On 3 Jun 2024, at 18:41, KUN LIN via 44net <44net(a)mailman.ampr.org> wrote: I saw on the portal there is an option to add PTR record in DNS. Is it functional? How do I add PTR records? I am not sure how to construct it that will be accepted by the portal. Kun _______________________________________________ 44net mailing list -- 44net(a)mailman.ampr.org<mailto:44net@mailman.ampr.org> To unsubscribe send an email to 44net-leave(a)mailman.ampr.org<mailto:44net-leave@mailman.ampr.org>

2 1

DNS PTR record
by KUN LIN 03 Jun '24

03 Jun '24

I saw on the portal there is an option to add PTR record in DNS. Is it functional? How do I add PTR records? I am not sure how to construct it that will be accepted by the portal. Kun

1 0

DNS claims on the new portal
by Chris 01 Jun '24

01 Jun '24

Hello 44Net, If you have made a DNS claim on the new portal please read this email as you may need to make a change… If you are logged in and navigate to this page on the new portal: https://portal.ampr.org/domain/records/1 You are able to view all the 51,000+ DNS records that are currently in the zonefile for ampr.org If you click the “Claim” icon next to a DNS record, you are able to claim the record as belonging to you, however this may not be the best method for doing this. If you have multiple DNS records you wish to claim under a common subdomain, or you plan on adding additional records under a subdomain, then you should instead do the following: Select “My subdomains” from the “DNS” menu, then click the “Request a subdomain” button. On the next page select “ampr.org” as the domain and enter the subdomain you wish to create. When you click the “Create request” button, this will create a ticket requesting creation of the subdomain. Once approved, your subdomain will be created and (importantly) any existing DNS records under the subdomain will be automatically pulled in. Here is an example: Say the following DNS records exist, unclaimed in the database: xyz.ampr.org A 44.45.46.47 www.xyz.ampr.org CNAME xyz.ampr.org. mail.xyz.ampr.org MX 10 mail.myservers.com. a.b.c.xyz.ampr.org A 44.43.42.41 You request the subdomain “xyz.ampr.org”, when it is approved, the subdomain is created and will appear on your account under the “DNS” menu “My subdomains”. All the above records will automatically be pulled into the subdomain and if you click on the “Resource records” icon under the “Actions” column you will see them all listed, along with an “Add a resource record” button so you can add additional records under the subdomain. For those that have already created multiple DNS claim requests, please navigate to “View my tickets” from the “Tickets” menu and delete all these tickets, then follow the instructions above to create a subdomain (or subdomains if you have records under more than one subdomain). The DNS claim button is really so that individual records, not under a common subdomain, can be claimed and there is no requirement to add additional records. If any of the above is not clear, or you have any questions, please do ask, either here or by creating a support ticket on the portal. 73, Chris - G1FEF — ARDC Administrator Web: https://www.ardc.net

1 0

← Newer
1
...
7
8
9
10
11
12
13
...
320
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net