Hi,
I'm writing a DNSSD service, it works different than Avahi.
It does dns discovery, and writes the records to a backend. At this moment the following I want to be supported:
- ldap - sqlite - filesystem
With the first, which scheme/attribute is there? It is about:
- network host dns names - ip address (ipv4 and/or ipv6) - services like SMB, CUPS, SSH etc. with port I see a lot of good attributes like ipServicePort, ipProtocolNumber and ipHostNumber, in schema NIS, but I miss the hostname (==string) and servicename, and the original dnssd type (_ssh_tcp etc)
Can you give and advice which attributes (or objectclass) to take? The following I have so far:
- network hostname: nisObject (I don't know) - ip address: ipHostNumber - service name: ipServiceProtocol and ipServicePort
So is nisObject a good candidate for a dns hostname?
Stef
Stef Bon wrote:
Hi,
I'm writing a DNSSD service, it works different than Avahi.
It does dns discovery, and writes the records to a backend. At this moment the following I want to be supported:
- ldap
- sqlite
- filesystem
With the first, which scheme/attribute is there? It is about:
- network host dns names
- ip address (ipv4 and/or ipv6)
- services like SMB, CUPS, SSH etc. with port
I see a lot of good attributes like ipServicePort, ipProtocolNumber and ipHostNumber, in schema NIS, but I miss the hostname (==string) and servicename, and the original dnssd type (_ssh_tcp etc)
hostname is a domainComponent, dc. servicename is probably ipServiceProtocol or just use cn, see the ipService objectclass.
Can you give and advice which attributes (or objectclass) to take? The following I have so far:
- network hostname: nisObject (I don't know)
- ip address: ipHostNumber
- service name: ipServiceProtocol and ipServicePort
So is nisObject a good candidate for a dns hostname?
Stef
Thanks a lot Howard. I have to get used to the ldap protocol. Right now I'm building the fs backend, next will be the sqlite backend, and then ldap.
Stef
openldap-technical@openldap.org