One curious thing about my proposal is that I called the new list-records option "--omit-up-to" instead of simply "--after". Some thinking did precede that. I thought: "If the option is called 'after' then that will suggest that if there is no record named like the argument then nothing will be printed, whereas list-records with that option prints the whole list if there is no record named like the argument; so I'll call it 'omit-up-to'."
But now I am thinking again. *Should* list-records print the whole list if there is no record named like the argument? Well, in the case of dnsmasq it doesn't make much difference. If lo.dnsmasq is absent then dnsmasq is out of the resolving chain and then it doesn't matter whether it has a (too) long or a (too) short list of forwarding addresses. After dnsmasq starts it adds a record 'lo.dnsmasq' and its resolvconf update hook script gets run and generates the correct forwarders list. Sooo... please find attached a patch which differs from the previous patch in that the option given to list-records is "--after" instead of "--omit-up-to". Sounds better. -- Thomas
dnsmasq-resolvconf-hook-script_20130718th1.patch
Description: Binary data