Re: [Dnsmasq-discuss] dnsmasq cname limitations
> Hi, why does dnsmasq cname require an entry on /etc/hosts? From the dnsmasq man page: --cname=,[,][,] Return a CNAME record which indicates that is really . There is a significant limitation on the target; it must be a DNS record which is known to dnsmasq and NOT a DNS record which comes from an upstream server. A potential workaround would be to recreate the A/ records for the CNAME target within dnsmasq. Of course, that's only viable if the respective IPs are both known and not subject to change. ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Multiple interfaces responding to DHCP requests
According to dnsmasq documentation, it would seem neither dhcp-option nor dhcp-range (at least for IPv4) would accept an interface: -O, --dhcp-option=[tag:,[tag:,]][encap:,][vi-encap:,][vendor:[],][|option:|option6:|option6:],[[,]] -F, --dhcp-range=[tag:[,tag:],][set:,][,|][,[,]][,time>] However, dnsmasq would auto-tag DHCP requests with "a tag whose name is the name of the interface on which the request arrived". Did you try to prefix your interface names with the 'tag:' keyword? E.g. dhcp-option=tag:enp2s0,1,255.255.255.0 dhcp-range=tag:enp2s0,192.168.1.100,192.168.1.199,infinite ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] multiple upstream servers
On 7/30/20, wkitt...@gmail.com wrote: On 7/29/20 7:59 PM, Dan Schaper wrote: You've told dnsmasq to send a lease with option 6 (DNS) set to 10.88.13.3. Where dnsmasq forwards the queries to is not relevant to your issue, you only have one upstream server configured. are you saying that this dhcp-option=tag:red,option:dns-server,10.88.13.3 dhcp-option=tag:green,option:dns-server,10.88.13.4 is not defining two upstream servers? If you'd expect dnsmasq's DNS server to switch its upstream DNS based on those options, that expectation would be entirely unjustified: Those lines configure DHCP, not DNS. That first line instructs the DHCP server to hand out 10.88.13.3 as DNS server when a red DHCP client is requesting that DHCP information, e.g. during initial DHCP lease negotiation - likewise the second with 10.88.13.4 for green clients. A client will then send its DNS queries to that respective DNS server. S Irlapati, you did force your client to request a new DHCP lease to put those options into effect, didn't you? ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
