44.88.0.1 is available as well for a 44-net DNS server, and it's dual stacked. --- Pardon my brevity, I'm on a Samsung Galaxy Note 3. Sent via the axMail-FAX suite. On April 2, 2018 8:04:05 PM lleachii--- via 44Net <44net(a)mailman.ampr.org> wrote:

Le 03/04/2018 à 02:15, Brian a écrit : Hi, Is there any information or wiki article about how DNS works in ampr-net ? We've been operating an island-wide network in Corsica for some years. We are currently using 10.44.x.y internal addressing, and we are now thinking about migrating to AMPR addressing with BGP. We planned to have our own DNS servers attached to our domain name (radioamateur.tk). I was not aware of a hierarchical DNS structure inside AMPR network. Is it possible to know more about it, so that we can add it in our design ? 73 de TK1BI

Hi, Le 04/04/2018 à 21:44, lleachii(a)aol.com a écrit : Not much details there. I see DNS updates are to be done by the coordinators. As they are volunteers, and as they may be very busy, this may not be compatible with a quick update required by a growing network Our plans were to get a subnet large enough for our island, and to manage the "internal" subnetting locally. We also planned to install our own DNS servers hosted in our 2 data centers (in fact, they are already running, with private addressing; we just have to migrate them to ampr addressing, and move them to the DMZ). I'm wondering about what would be the best solution : - Use an independant domain name (ie, "radioamateur.tk") - Use a subdomain of ampr.org (ie, "corsica.ampr.org"), with a sub-delegation from the parent "ampr.org" domain In both solutions, we would have immediate access for local updates, on our local DNS servers. Comments and advices from similar situations are welcome. 73 de TK1BI

Le 05/04/2018 à 11:12, Brian Kantor a écrit : Thank you for your info. We'll investigate all that, among the many things we still have to do ;-)

It will break stuff that was broken anyway. Anyone who decides to use a valid IP address that’s not RFC1918 for their own internal use deserves what’s coming to them. RFC1918 was specifically to set aside IP address space that is guaranteed not to be globally routable. If 17,891,328 IP addresses set aside for your own personal use isn’t good enough, you’ve engineered a bad network :) Ian VE7BST

1.1.1.1 was never a valid address. It’s always been labelled as a research prefix and never publicly routed — remarks: + Address blocks listed with this contact remarks: + are withheld from general use and are remarks: + only routed briefly for passive testing. remarks: + remarks: + If you are receiving unwanted traffic remarks: + it is almost certainly spoofed source remarks: + or hijacked address usage. — Ruben - ON3RVH On 1 Apr 2018, at 21:36, Ian McLaughlin <ian@platinum.net<mailto:ian@platinum.net>> wrote: It will break stuff that was broken anyway. Anyone who decides to use a valid IP address that’s not RFC1918 for their own internal use deserves what’s coming to them. RFC1918 was specifically to set aside IP address space that is guaranteed not to be globally routable. If 17,891,328 IP addresses set aside for your own personal use isn’t good enough, you’ve engineered a bad network :) Ian VE7BST On Apr 1, 2018, at 12:23 PM, Ruben ON3RVH <on3rvh@on3rvh.be<mailto:on3rvh@on3rvh.be>> wrote: That is gonna break a lot of stuff because 1.1.1.1 is used a lot as a blackhole address on border routers And also as a dns blackhole ip for unwanted dns domains.. Lots of networks will need remodelling to allow access to this service Ruben - ON3RVH On 1 Apr 2018, at 20:46, Brian Kantor <Brian@BKantor.net<mailto:Brian@BKantor.net>> wrote: Cloudflare has announced a new internet-wide DNS resolution service. There's a good writeup on it at https://blog.cloudflare.com/dns-resolver-1-1-1-1/ This bit of news isn't much advantage to people on the tunneled AMPRNet, but the writeup is nonetheless interesting. - Brian _________________________________________ 44Net mailing list 44Net@mailman.ampr.org<mailto:44Net@mailman.ampr.org> https://mailman.ampr.org/mailman/listinfo/44net _________________________________________ 44Net mailing list 44Net@mailman.ampr.org<mailto:44Net@mailman.ampr.org> https://mailman.ampr.org/mailman/listinfo/44net --- Filter service subscribers can train this email as spam or not-spam here: http://my.email-as.net/spamham/cgi-bin/learn.pl?messageid=8142CC5435E211E89… _________________________________________ 44Net mailing list 44Net@mailman.ampr.org<mailto:44Net@mailman.ampr.org> https://mailman.ampr.org/mailman/listinfo/44net

Yes that is because 1.1.1.1 was never meant to be publicly routed. In fact if it was routed or appeared in the global routing tables it was because someone spoofed/hijacked it or accidentally routed it. Or that the APNIC was performing some passive tests. Ruben - ON3RVH > On 1 Apr 2018, at 22:44, Darcy Buskermolen &lt;darcyb(a)gmail.com&gt; wrote: > > Tell that to Cisco that uses 1.1.1.1 as part of their default config for the wireless access points. > > > > > Sent on the go, from somewhere other than here. > -------- Original message --------From: Ian McLaughlin &lt;ian(a)platinum.net&gt; Date: 2018-04-01 12:34 (GMT-08:00) To: AMPRNet working group &lt;44net(a)mailman.ampr.org&gt; Subject: Re: [44net] New Global DNS server > It will break stuff that was broken anyway. Anyone who decides to use a valid IP address that’s not RFC1918 for their own internal use deserves what’s coming to them. RFC1918 was specifically to set aside IP address space that is guaranteed not to be globally routable. If 17,891,328 IP addresses set aside for your own personal use isn’t good enough, you’ve engineered a bad network :) > > Ian VE7BST > > >> On Apr 1, 2018, at 12:23 PM, Ruben ON3RVH &lt;on3rvh(a)on3rvh.be&gt; wrote: >> >> That is gonna break a lot of stuff because 1.1.1.1 is used a lot as a blackhole address on border routers >> And also as a dns blackhole ip for unwanted dns domains.. >> Lots of networks will need remodelling to allow access to this service >> >> Ruben - ON3RVH >> >>> On 1 Apr 2018, at 20:46, Brian Kantor &lt;Brian(a)BKantor.net&gt; wrote: >>> >>> Cloudflare has announced a new internet-wide DNS resolution >>> service. There's a good writeup on it at >>> >>> https://blog.cloudflare.com/dns-resolver-1-1-1-1/ >>> >>> This bit of news isn't much advantage to people on the tunneled >>> AMPRNet, but the writeup is nonetheless interesting. >>> - Brian >>> >>> _________________________________________ >>> 44Net mailing list >>> 44Net(a)mailman.ampr.org >>> https://mailman.ampr.org/mailman/listinfo/44net >> >> _________________________________________ >> 44Net mailing list >> 44Net(a)mailman.ampr.org >> https://mailman.ampr.org/mailman/listinfo/44net >> >> >> --- >> Filter service subscribers can train this email as spam or not-spam here: http://my.email-as.net/spamham/cgi-bin/learn.pl?messageid=8142CC5435E211E89… > > > _________________________________________ > 44Net mailing list > 44Net(a)mailman.ampr.org > https://mailman.ampr.org/mailman/listinfo/44net >