OK, thanks for the clarification. בתאריך יום ג׳, 22 בינו׳ 2019 ב-1:43 מאת Simon Kelley < si...@thekelleys.org.uk>: > > > On 21/01/2019 07:33, Yossi Boaron wrote: > > > > > Is this dnsmasq limitation is just due to lack of support in code/bug? > > or it requires massive architectural
On 21/01/2019 07:33, Yossi Boaron wrote: > > Is this dnsmasq limitation is just due to lack of support in code/bug? > or it requires massive architectural changes of dnsmasq? > If it's the first one, I can try to fix this issue. > It's the second, unfortunately. a DNS query can be answered
Hi Simon, Thanks a lot for a prompt response. Unfortunately, I can't have both (CNAME and host) entries in upstream neither in dnsmasq. I'll add a few words about what I need to do, As Openstack tenant, I run an application that composed of few VMs, the VMs communicate with other VMs using
It's a known limitation. The actual limitation is that a CNAME and it's target must both either originate from an upstream server, or both originate from the dnsmasq local configuration. Mixing sources (ie CNAME from upstream and target from dnsmasq, or vice-versa) is not allowed. The commonest
I run the same test with Dnsmasq 2.80 (2.80-32-g28cfe36) - and got the similiar results. 10.0.2.200 is the VM's IP address 10.46.4.43 - is the IP address of the external DNS server The dnsmasq log as response to ' dig +noedns ostest-etcd-5.shiftstack.com. A' Jan 20 12:54:37 dnsmasq:
Hi All, I have the following DNS topology (In my Openstack deployment): VM --> DNSMASQ --> external DNS server domain name= shiftstack.com, and Dnsmasq 2.76 is used at this Openstack deployment. I run the following test: 1. Define CNAME record at external DNS server ostest-etcd-5.shiftstack.com.