>From the correct mail alias!
On Sat, 16 Sept 2023 at 21:50, Greg Choules
wrote:
> Hi Ged.
> 172.16/12 is not a special case. The whole problem (IMHO) stems from how
> humans have chosen to represent both IP addresses (v4; v6 are different and
> actually a little easier) AND DNS domain names;
On Sat, 16 Sep 2023 10:22:26 +0100 (BST)
"G.W. Haywood via bind-users" wrote:
> Hi there,
> ...
>I'd be surprised if the OP couldn't manage with 2^20 IPs in a segment -
> but then I guess he does work in the .gov domain.
^^^
The OP's contact
Hi there,
On Sat, 16 Sep 2023, Greg Choules wrote:
On Sat, 16 Sep 2023, G.W. Haywood wrote:
...
> Is there a reason not to split the /8 into two /9s or something like that?
...
Although it is technically possible to do reverses on non-octet boundaries
(for example, see
Hi.
Although it is technically possible to do reverses on non-octet boundaries
(for example, see https://www.ietf.org/rfc/rfc2317.txt) it is a
complete pita, in my experience. Personally I would not head down that
path. Stick to /8, /16 or /24.
Cheers, Greg
On Sat, 16 Sept 2023 at 09:20, G.W.
Hi there,
On Sat, 16 Sep 2023, John Thurston wrote:
A host which auto-registers in MS DNS, creates an A in foo.alaska.gov
and PTR in whatever.10.in-addr.arpa. MS DNS is happy to publish those.
But the DNS system running on BIND also has a whatever.10.in-addr.arpa
zone.
So if I want to
Hi John.
Sorry if this sounds picky, but a dot out of place in this game is the
difference between success and crash-n-burn.
Please can you show me EXACTLY what ...10.in-addra.arpa zones you have in
both sets of DNS?
>From previous work with AD clients I think that, if it doesn't already
exist,
6 matches
Mail list logo
