Bug 23943 - UDM-Nagios-Integration muss mit ARecord an der Domäne klar kommen
UDM-Nagios-Integration muss mit ARecord an der Domäne klar kommen
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Monitoring (Prometheus or Nagios)
UCS 3.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: Nagios maintainers
:
Depends on: 23554 23725
Blocks:
  Show dependency treegraph
 
Reported: 2011-10-05 14:11 CEST by Alexander Kläser
Modified: 2017-08-08 07:07 CEST (History)
3 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kläser univentionstaff 2011-10-05 14:11:50 CEST
Das funkioniert soweit, allerdings werden die IP-Adressen intern über LDAP-Host-Records aufgelöst. Das könnte durch die Verwendung der von UDM-Modulen mitgebrachten Techniken wahrscheinlich stark verbessert werden, bspw. über self.info['fqdn'] etc.

+++ This bug was initially created as a clone of Bug #23725 +++

Diese Änderung verwirrt die Nagios-Integration. Dies führt zu 
 univentionNagiosHostname: @.univention.qa
an den nagios/service Objekten.

+++ This bug was initially created as a clone of Bug #23554 +++

Für die Samba 4 Anmeldung und GPO Auswertung ist es erforderlich, dass die DNS
Forward Zone eine ARecord Eintrag bekommt. Das müsste per UDM Modul gesetzt
werden können.

root@master5:/usr/share/doc/bind9# univention-ldapsearch -LLL -b
cn=dns,dc=deadlock5,dc=local zoneName=deadlock5.local -s one
dn: zoneName=deadlock5.local,cn=dns,dc=deadlock5,dc=local
nSRecord: master5.deadlock5.local.
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/forward_zone
dNSTTL: 10800
relativeDomainName: @
zoneName: deadlock5.local
aRecord: 10.201.5.1
sOARecord: master5.deadlock5.local. root.deadlock5.local. 47 28800 7200 604800
  10800

root@master5:/usr/share/doc/bind9# head -n 20
/var/cache/bind/deadlock5.local.zone 
$ORIGIN .
$TTL 10800      ; 3 hours
deadlock5.local         IN SOA  master5.deadlock5.local. root.deadlock5.local.
(
                                47         ; serial
                                28800      ; refresh (8 hours)
                                7200       ; retry (2 hours)
                                604800     ; expire (1 week)
                                10800      ; minimum (3 hours)
                                )
                        NS      master5.deadlock5.local.
                        A       10.201.5.1
$ORIGIN deadlock5.local.
$TTL 80600      ; 22 hours 23 minutes 20 seconds
_kerberos               TXT     "DEADLOCK5.LOCAL"
$ORIGIN _msdcs.deadlock5.local.
67f44995-a9e7-436a-a82d-108df4e7b2b8 CNAME master5.deadlock5.local.
$ORIGIN _tcp.Default-First-Site-Name._sites.dc._msdcs.deadlock5.local.
$TTL 10800      ; 3 hours
_kerberos               SRV     0 100 88 master5.deadlock5.local.
_ldap                   SRV     0 100 389 master5.deadlock5.local.
root@master5:/usr/share/doc/bind9# host deadlock5.local
deadlock5.local has address 10.201.5.1
root@master5:/usr/share/doc/bind9# 

Siehe auch Bug #23481.
Comment 1 Stefan Gohmann univentionstaff 2017-06-16 20:39:25 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 2 Stefan Gohmann univentionstaff 2017-08-08 07:07:46 CEST
This issue has been filed against UCS 3.0.

UCS 3.0 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.