Send Netdot-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-users
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-users digest..."
Today's Topics:
1. Re: ip6.arpa PTR records (Matt Zagrabelny)
2. Re: ip6.arpa PTR records (Matt Zagrabelny)
----------------------------------------------------------------------
Message: 1
Date: Wed, 4 Jan 2017 16:46:06 -0600
From: Matt Zagrabelny <[email protected]>
Subject: Re: [Netdot-users] ip6.arpa PTR records
To: Carlos Vicente <[email protected]>
Cc: "[email protected]" <[email protected]>
Message-ID:
<caolfk3uhdh3g+cbnmk5jo1nghewtpnhqo-8dh9ohzakmevp...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Hey Carlos,
On Wed, Jan 4, 2017 at 8:52 AM, Carlos Vicente <[email protected]> wrote:
> Hi Matt,
>
> It definitely works because I've been using the feature for years. The
> procedure you mention:
>
> "IP Block" -> Zones -> Reverse Zones -> add
>
> is the recommended one because Netdot will generate the right zone label for
> you based on the block.
>
> PTR records should be created/updated automatically each time you add/update
> a AAAA record.
We are being bit by:
https://osl.uoregon.edu/redmine/issues/1909
I've coded up the fix for the above, but we are still hitting an issue
somewhere. I'll keep digging.
Thanks!
-m
------------------------------
Message: 2
Date: Wed, 4 Jan 2017 21:06:13 -0600
From: Matt Zagrabelny <[email protected]>
Subject: Re: [Netdot-users] ip6.arpa PTR records
To: Carlos Vicente <[email protected]>
Cc: "[email protected]" <[email protected]>
Message-ID:
<caolfk3wvtwaq+fgn8-eyw3v0eh391wccoiepxshccqdt0ka...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
On Wed, Jan 4, 2017 at 4:46 PM, Matt Zagrabelny <[email protected]> wrote:
> Hey Carlos,
>
> On Wed, Jan 4, 2017 at 8:52 AM, Carlos Vicente <[email protected]> wrote:
>> Hi Matt,
>>
>> It definitely works because I've been using the feature for years. The
>> procedure you mention:
>>
>> "IP Block" -> Zones -> Reverse Zones -> add
>>
>> is the recommended one because Netdot will generate the right zone label for
>> you based on the block.
>>
>> PTR records should be created/updated automatically each time you add/update
>> a AAAA record.
>
> We are being bit by:
>
> https://osl.uoregon.edu/redmine/issues/1909
>
> I've coded up the fix for the above, but we are still hitting an issue
> somewhere. I'll keep digging.
Looks like there is some amount of case sensitiveness with v6 things
in Netdot. If I put a well placed lc() in the code I can get the PTR
records generated.
Our prefix was entered lowercase:
2607:ea00:200::/40
and the reverse zone was correctly calculated as:
2.0.0.0.a.e.7.0.6.2.ip6.arpa, but when Netdot looked for descendants
of our prefix and calculated their reverse names it used uppercase:
5.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.9.0.1.0.0.0.2.0.0.0.A.E.7.0.6.2.ip6.arpa
and the zone search fails for the uppercase version of the reverse
name - which is interesting because DNS is case insensitive.
Thus the lc hack helped illustrate the case sensitiveness - at least
for v6 reverse zone stuff.
-m
------------------------------
_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users
End of Netdot-users Digest, Vol 93, Issue 2
*******************************************