On Mon, 2022-11-21 at 17:52 -0800, Jay Hennigan via mailop wrote: > On 11/21/22 17:30, Jim Popovitch via mailop wrote: > > On Mon, 2022-11-21 at 17:10 -0800, Jay Hennigan via mailop wrote: > > > On 11/21/22 16:24, Jim Popovitch via mailop wrote: > > > > > > > I still think there's some weirdness going on. Firstly I'd be surprised > > > > if Wietse hung www off of 1 NS, and then the base domain off of 2 NSes > > > > on the same subnet. > > > > > > Unless they're anycast. As a mild example, 4.2.2.1 and 4.2.2.2 > > > > > > > Of course, but in this case simple testing says they aren't... unless > > all the anycast end-points are hanging off a HE node in NYC. > > Alternatively, if the resource that you're trying to reach is on the > same LAN (or machine) as both/all of its authoritative nameservers, it > doesn't matter in the larger scheme of things. > > If a resource isn't reachable because its subnet is unreachable, then > whether or not authoritative DNS on the same subnet is working really > becomes kind of moot. You're not going to reach that resource whether or > not it resolves until the underlying issue gets fixed. > > This doesn't seem to be the case with Postfix, however. >
I'm not really certain of what your point is, but do you realize why having a single NS server, or more than 1 NS servers all on the same subnet, is bad? -Jim P. _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
