Out-of-Bailiwick DNS? (Was: HE.net problem)

> On 4 Jul 2024, at 23:22, Paul Ebersman wrote: > > cjc> On the other side of this, we all may be learning the value of not > cjc> having all of you NS records in a single zone with a domain under a > cjc> single registrar. > > From some trainings I did on how to be sure your DNS was robust:

Re: Out-of-Bailiwick DNS? (Was: HE.net problem)

> On Jul 5, 2024, at 09:53, Jeroen Massar via NANOG wrote: > Please note that: > - Markmonitor is owned by Newfold Digital / Endurance International [1] > - Network Solutions is owned by Web.com [2] > - Web.com is... owned by Newfold Digital [3] > > And... we

[Event] Our Networks: Does not (cloud) compute, July 27, Vancouver, BC

Hello all, sharing an event coming up at the end of the month in Vancouver, BC just after the IETF120 meeting-- It's a mix of community networks, local-first software, solar servers, right to repair, and more! --- *Our Networks 2024: Does not (cloud) compute* July 27, 2024 312 Main, Vancouve

Re: Out-of-Bailiwick DNS? (Was: HE.net problem)

ebersman> - don't have all your business critical domains under the same ebersman> registrar (unless it's of the CSC/markmonitor class) jeroen> There is always going to be single point of failures in a jeroen> hierarchical tree like that. Everything in internet/infrastructure is risk tradeoffs

Re: Out-of-Bailiwick DNS? (Was: HE.net problem)

On Jul 5, 2024, at 12:53 AM, Jeroen Massar via NANOG wrote: > Thus one only increases the risk by having multiple TLDs. That's not the case if you provide DNS servers for others, though. It is true that if he.net has nameservers of "ns1.he.net" and "ns2.he.net", making the second of those be

Weekly Global IPv4 Routing Table Report

This is an automated weekly mailing describing the state of the Global IPv4 Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG UKNOF, TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG. Daily listings are sent to bg

Re: TLD jingle mail, Out-of-Bailiwick DNS? (Was: HE.net problem)

It appears that Bill Woodcock said: >ICANN’s going to open another round of TLD applications, and I expect a lot of >companies to go into that with their eyes more >open than last time, knowing why they’re doing it. It’s not about brand >protection, it’s about disintermediating the root >of tru

Re: TLD jingle mail, Out-of-Bailiwick DNS? (Was: HE.net problem)

On Fri, Jul 5, 2024 at 6:25 PM John Levine wrote: > > Also, getting your own TLD doesn't necessarily make your risks less, it just > makes them different. You now have a direct relationship with the registry > back end provider that you have to not screw up, and due to ICANN's rules, > there is

Re: Out-of-Bailiwick DNS? (Was: HE.net problem)

- Original Message - > From: "Robert L Mathews" > > However, if "example.com" uses "ns1.he.net" and "ns2.he.net" as its > nameservers, > having the second of those instead be "ns2.he.org" will keep "www.example.com" > reachable if he.net is placed on clientHold. > > That was presumably