On Wed, Feb 17, 2016 at 12:59:58PM +0100, Michal Privoznik wrote:
[..snip..]
> Nice. For a similar purpose I hacked up simplec a while ago:
>
>
https://github.com/agx/simplec
>
> it works by fetching domain IPs using our APIs and stores them in a file
> for a dnsmasq instance to read. This allows to even collect IPs from
> remote URIs.
>
Interesting. Esp. the remote URIs part. That's what I was wondering when
writing my module, whether I should actually open a libvirt connection
and use public API to retrieve IPs or parsing an internal file is just
enough. But I could not think of any useful use case where I'd need to
resolve remote IPs. I mean, either those IPs are in a private network so
they are useless, or they come from the same subnet as host ones and in
that case external DHCP server has assigned them and hopefully set DNS
records too. What's your use case?
The use case is IPv6 connections assigned via e.g. radvd. I'm not using
simplec for that yet (and it will need some minor tweaks to support AAAA) but
that was the reason for using dnsmasq instead of a new nss module that
proxies to another service.
The other reason is that I want it to handle more in the future like
settings up .ssh/config (for tab completion and jump hosts).
Cheers,
-- Guido
My argumentation for NSS module is that one does not need yet
another
dnsmasq process running just to do a name translation.
Michal