[Dnsmasq-discuss] 2.80 dnspooq v3 problem

2021-03-16 Thread sunil rathod
. Once it starts working if I change back to local dns server, it works fine. Any idea what's going wrong with this patch? Regards, Sunil Rathod. On Tue, Mar 16, 2021, 16:16 sunil rathod wrote: > > ___ Dnsmasq-discuss mailing list Dnsm

Re: [Dnsmasq-discuss] 2.80 dnspooq v3 problem

2021-03-30 Thread sunil rathod
With dnspooq patch dns resulation fails when I configure same server with two different interfaces as below, server 10.8.8.21@eth0 server 10.8.8.21@eth1, If remove the dnspooq patch, resulation happen properly. Is there any known issue with dnspooq patch? On Tue, Mar 16, 2021, 16:16 sunil rathod

[Dnsmasq-discuss] Dnsmasq replying with refuse without forwarding request to upstream server.

2021-07-22 Thread sunil rathod
Hi All, Any thoughts why dnsmasq is replying with REFUSE response without forwarding the query to upstream server? Nslookup always fails with refuse response from the external client. I have the upstream server configured on conf file as server=8.8.8.8@eth0 Regards, Sunil _

Re: [Dnsmasq-discuss] Dnsmasq replying with refuse without forwarding request to upstream server.

2021-07-22 Thread sunil rathod
Simon. > > > On 22/07/2021 18:21, sunil rathod wrote: > > Hi All, > > Any thoughts why dnsmasq is replying with REFUSE response without > > forwarding the query to upstream server? Nslookup always fails with > > refuse response from the external client. I have the upst

Re: [Dnsmasq-discuss] Dnsmasq replying with refuse without forwarding request to upstream server.

2021-07-23 Thread sunil rathod
I m using dnsmasq 2.80 On Fri, Jul 23, 2021, 14:05 sunil rathod wrote: > I get a warning message saying no upstream servers configured when I start > the dnsmasq. But in dnsmasq.conf file I have configured upstream server as > below > server=8.8.8.8@eth0. dnsmasq is running bu

Re: [Dnsmasq-discuss] Dnsmasq replying with refuse without forwarding request to upstream server.

2021-07-23 Thread sunil rathod
Jul 2021, at 18:21, sunil rathod wrote: > > Hi All, > > Any thoughts why dnsmasq is replying with REFUSE response without > > forwarding the query to upstream server? Nslookup always fails with > > refuse response from the external client. I have the upstream server >

Re: [Dnsmasq-discuss] Dnsmasq replying with refuse without forwarding request to upstream server.

2021-07-23 Thread sunil rathod
Forgot to mention that kernel has been upgraded on the system. On Fri, Jul 23, 2021, 15:18 sunil rathod wrote: > Hello Alex, > Thank you for your reply. How can I figure out if it's implemented on our > platform. I m using 2.80 version. Is there any work around for this? >

Re: [Dnsmasq-discuss] Dnsmasq replying with refuse without forwarding request to upstream server.

2021-07-23 Thread sunil rathod
Hello Alex, Thank you for your reply. How can I figure out if it's implemented on our platform. I m using 2.80 version. Is there any work around for this? On Fri, Jul 23, 2021, 14:59 Alex Morris wrote: > On Fri, 23 Jul 2021, at 09:35, sunil rathod wrote: > > > > I get a wa

Re: [Dnsmasq-discuss] Dnsmasq replying with refuse without forwarding request to upstream server.

2021-07-23 Thread sunil rathod
. > Your problem now is to work out why dnsmasq is not reading your > configuration. Note that it logs the configured servers ar start up, so > that should help debugging. > > Simon. > > On 23 July 2021 09:35:06 GMT+01:00, sunil rathod > wrote: >> >> I get

Re: [Dnsmasq-discuss] Dnsmasq replying with refuse without forwarding request to upstream server.

2021-07-25 Thread sunil rathod
2PM +0530, sunil rathod wrote: > > On Fri, Jul 23, 2021, 17:01 Simon Kelley > wrote: > > > On 23 July 2021 09:35:06 GMT+01:00, sunil rathod wrote: > > >> > > >> I get a warning message saying no upstream servers configured when I > > >> start the

Re: [Dnsmasq-discuss] 2.80 dnspooq v3 problem

2021-12-03 Thread sunil rathod
Hi Petr, I have used the following patches for 2.80 release along with dnspooq patch to resolve the bugs. Does this patch have any implications with the "SO_BINDTODEVICE" option in sockets. In my system, when DNS replies arrive on the interface, the kernel seems to drop these because of a mismat