[Dnsmasq-discuss] Problems with SRV Queries

[Edson]

Yeap... it worked... thanks for the quick return...

But now I'm asking me why should I use "filterwin2k" parm... if it was
thinked to help on windows environment, but it blocks SRV request, it seams
that this is an undesired side-effect... with all SIP and VoIP stuff
around...

Shouldn't this behavior (SRV blocking) being a separate parm? 

Edson.

> -----Original Message-----
> From: Simon Kelley [mailto:simon at thekelleys.org.uk]
> Sent: quinta-feira, 1 de março de 2007 13:41
> To: Edson
> Cc: dnsmasq-discuss at lists.thekelleys.org.uk
> Subject: Re: [Dnsmasq-discuss] Problems with SRV Queries
> 
> Edson wrote:
> >
> >
> >
> >
> >> -----Original Message-----
> >
> >> From: Simon Kelley [mailto:simon at thekelleys.org.uk]
> >
> >> Sent: quinta-feira, 1 de março de 2007 11:21
> >
> >> To: Edson
> >
> >> Cc: dnsmasq-discuss at lists.thekelleys.org.uk
> >
> >> Subject: Re: [Dnsmasq-discuss] Problems with SRV Queries
> >
> >
> >> Edson wrote:
> >
> >>> Hi, All...
> >
> >
> >>> I'm facing some really wierd situation here...
> >
> >>> I have a Grandstream that depends on a SRV querie to resolve the SIP
> >
> >> server
> >
> >>> address. When I define a SRV clause in the DNSMasq config file, and
> >
> >>> configure the Grandstream to use it as DNS server, it works smoothly,
> >
> >> the
> >
> >>> registration is successful. But if I don't, I see the querie being
> >
> >> forwarded
> >
> >>> to the DNS upstream server, but the answer never hits the
> Grandestream.
> >
> >
> >> Small gotcha here: if you are relying on --log-queries for this data,
> >
> >> then you won't see the reply logged, only replies to A and AAAA queries
> >
> >> get logged.
> >
> >
> >
> > I'm getting such logs:
> >
> > Mar  1 12:53:27 repolho dnsmasq[25013]: query[SRV] _sip._udp.alta.com.br
> > from 192.168.100.26
> >
> > Mar  1 12:53:27 repolho dnsmasq[25013]: config _sip._udp.alta.com.br is
> > <NODATA>
> clue                                        ^^^
> 
> This says that the source of the reply is dnsmasq configuration, not a
> reply from an upstream server.
> 
> 
> You can see, the querie is present on the INTERNAL, but not on the
> > EXTERNAL.
> >
> >
> That's expected, given the log.
> 
> >
> > For simplicity I reduce the DNSmasq configuration to:
> >
> > filterwin2k
> 
> and here's the culprit: from dnsmasq(8), "--filterwin2k .... The
> requests  blocked  are  for records of types SOA and SRV"
> 
> Remove that, and it will all work. Apologies, I should have included
> --filterwin2k in my list of options which could intercept queries.
> 
> 
> Cheers,
> 
> Simon.