[snip] > Perhaps, you could implement (instead of tags for PTR, CNAME, etc.) > > <dns> > <host ip="192.168.122.1"> > <hostname>host1</hostname> > <hostname>host2</hostname> > <hostname>host3</hostname> > </host> > </dns> > > instead, which would write a file > > 192.168.122.1 host1 host2 host3 > > and pass it to dnsmasq via --addn-hosts. But every feature should be > added as a separate patch. Paolo, I'm having interesting results on this matter. I was unable to see it working now whereas I saw it working fine yesterday so I've been investigating this further. Results of my investigation were obtained when running it manually and they are: 1) /usr/sbin/dnsmasq --strict-order --bind-interfaces --pid-file=/var/run/libvirt/network/default.pid --conf-file= --except-interface lo --txt-record="txt-record","some value, which is something" --addn-hosts=/var/run/libvirt/network/default.hosts --listen-address 192.168.122.1 --dhcp-range 192.168.122.2,192.168.122.254 --dhcp-leasefile=/var/lib/libvirt/dnsmasq/default.leases --dhcp-lease-max=253 --dhcp-no-override -> the guest was unable to access the records from --addn-hosts (tested using nslookup) 2) /usr/sbin/dnsmasq --strict-order --bind-interfaces --pid-file=/var/run/libvirt/network/default.pid --conf-file= --except-interface lo --txt-record="txt-record","some value, which is something" --addn-hosts=/var/run/libvirt/network/default.hosts --listen-address 192.168.122.1 --dhcp-range 192.168.122.2,192.168.122.254 --dhcp-leasefile=/var/lib/libvirt/dnsmasq/default.leases --dhcp-lease-max=253 --dhcp-no-override --no-daemon -> the --no-daemon option made it working for the --addn-hosts but it was not working without it, i.e. in the daemon mode. Based on this I guess this is the bug in Fedora-14 DNSMasq (which is the same as the one for Fedora-14 since I'm unable to get any update and the version I'm having is dnsmasq-2.52-1.fc13.i686). Should I file a bug against DNSMasq about this? Also, I've been testing the --txt-record once again and not grabbed it with wireshark and I had to query the "txt-record" TXT record for this and the wireshark was showing the quotes there as well now. Should I disable it then and use the working syntax for record name which (according to my testing) is to use *--txt-record=txt-record,"some value, which is something"* instead, i.e. to not use quotes in the name? Thanks, Michal -- Michal Novotny <minovotn@xxxxxxxxxx>, RHCE Virtualization Team (xen userspace), Red Hat -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list