Just an idea. Maybe allow for multiple node labels per node. When you have a cname or multiple A records in DNS, some times the wrong name can be applied to the server (DNS server admin error). Not a big deal to search on either or, but if the names switch, it can get confusing. Tho an Event triggering when this happens can help.
I understand it's the first one/only one on a reverse lookup is used, but if the DNS server reports back more then one, why not?
Just an idea. Maybe allow for multiple node labels per node. When you have a cname or multiple A records in DNS, some times the wrong name can be applied to the server (DNS server admin error). Not a big deal to search on either or, but if the names switch, it can get confusing. Tho an Event triggering when this happens can help.
I understand it's the first one/only one on a reverse lookup is used, but if the DNS server reports back more then one, why not?
/usr/local/share/snmp # nslookup galileo1
Server: 172.16.93.61
Address: 172.16.93.61#53
Name: galileo1.domain.com
Address: 172.16.81.100
/usr/local/share/snmp # nslookup 172.16.81.100
Server: 172.16.93.61
Address: 172.16.93.61#53
100.81.16.172.in-addr.arpa name = opennms1.domain.com.
100.81.16.172.in-addr.arpa name = galileo1.domain.com.
C:\Documents and Settings\czerak>nslookup 172.16.81.100
Server: bidhcp1.domain.com
Address: 172.16.93.15
Name: opennms1.domain.com
Address: 172.16.81.100