Send Netdot-devel mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
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-devel digest..."
Today's Topics:
1. [Netdot - Bug #1799] (New) typo in lib/Netdot/Model.pm in
get_digest() ([email protected])
2. [Netdot - Bug #1800] (New) Fix NAPTR record requirements
([email protected])
3. [Netdot - Bug #1800] Fix NAPTR record requirements
([email protected])
4. Re: naptr record rejected (Carlos Vicente)
----------------------------------------------------------------------
Message: 1
Date: Wed, 16 Apr 2014 12:04:13 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1799] (New) typo in
lib/Netdot/Model.pm in get_digest()
To: [email protected], [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1799 has been reported by William Bulley.
----------------------------------------
Bug #1799: typo in lib/Netdot/Model.pm in get_digest()
https://osl.uoregon.edu/redmine/issues/1799
Author: William Bulley
Status: New
Priority: Low
Assignee: Carlos Vicente
Category: Documentation
Target version: 1.0.6
Resolution:
In get_digest() example there is a typo:
my %digest = $obj->get_state_digest;
s/_state_//
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://osl.uoregon.edu/redmine/my/account
------------------------------
Message: 2
Date: Wed, 16 Apr 2014 19:28:33 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1800] (New) Fix NAPTR record
requirements
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1800 has been reported by Carlos Vicente.
----------------------------------------
Bug #1800: Fix NAPTR record requirements
https://osl.uoregon.edu/redmine/issues/1800
Author: Carlos Vicente
Status: New
Priority: Normal
Assignee:
Category: DNS
Target version: 1.0.7
Resolution:
* Some fields are required unnecessarily.
* The service field requirement is too strict
See RFC2915
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://osl.uoregon.edu/redmine/my/account
------------------------------
Message: 3
Date: Wed, 16 Apr 2014 19:36:13 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1800] Fix NAPTR record
requirements
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1800 has been updated by Carlos Vicente.
Also, the record cannot be added to the zone apex ('@') because in host.html,
there is this condition:
<pre>
#####################################################################################################
#RRNAPTR
if ( !$o->a_records && !$o->ptr_records && !$o->ns_records ){
</pre>
----------------------------------------
Bug #1800: Fix NAPTR record requirements
https://osl.uoregon.edu/redmine/issues/1800#change-3170
Author: Carlos Vicente
Status: New
Priority: Normal
Assignee:
Category: DNS
Target version: 1.0.7
Resolution:
* Some fields are required unnecessarily.
* The service field requirement is too strict
See RFC2915
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://osl.uoregon.edu/redmine/my/account
------------------------------
Message: 4
Date: Wed, 16 Apr 2014 22:44:25 -0400
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-devel] naptr record rejected
To: Markus Wigge <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252
Hi Markus,
Your sample record was:
@ 86400 IN NAPTR 100 10 "s" "x-eduroam:radius.tls" ""
_radsec._tcp.eduroam.de.
RFC2915 specifies the order as:
Domain TTL Class Type Order Preference Flags Service Regexp
Replacement
As you can see, your domain is ?@?, which is the zone apex. You should be able
to see this record when browsing all records in your zone.
Also, your ?Replacement? field is "_radsec._tcp.eduroam.de?, so it?s not null
as you say.
In any case, you are right that there are several problems that need to be
corrected in Netdot.
I have just created a new ticket in Redmine to track those.
https://osl.uoregon.edu/redmine/issues/1800
Thanks,
cv
On Apr 15, 2014, at 1:34 PM, Markus Wigge <[email protected]> wrote:
> Hi Carlos,
>
> thank you for the hint but it seems to be more complicated.
>
> The only way to insert the NAPTR record I found, is the "Advanced->Add"
> function to inject it directly into the table.
> Unfortunately the GUI expects "Regexp" and "Replacement" as required
> fields which are not. (in my case "" for both)
>
> And the field "Resource Record" is a reference to a local record. But I
> just want to point to an external name for which I do not have a local
> zone in my database...
>
> Maybe that field should just be a string value instead of a reference? I
> don't know the drawbacks of that.
>
> Regards,
> Markus
>
------------------------------
_______________________________________________
Netdot-devel mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
End of Netdot-devel Digest, Vol 85, Issue 11
********************************************
