On Sat, Nov 17, 2007 at 04:01:51PM +0100, Rolf Sommerhalder wrote:
relay dnsRelay {
listen on $yellow port 53
protocol dnsProto
forward to $white port 53
#forward to $dnsHost port 53
timeout 60
}
as theo mentioned, the problem is related to the use of the bind()
call for the
On Nov 19, 2007 6:35 PM, Reyk Floeter [EMAIL PROTECTED] wrote:
please try to configure the following:
...
so the proposed solution is to always use listen on 0.0.0.0 port 53
with DNS relays for now.
Your proposal indeed solves the problem in my multi-homed setup, and
makes my work-around with
On Nov 17, 2007 4:01 PM, Rolf Sommerhalder
[EMAIL PROTECTED] wrote:
This unexpected behaviuor of the DNS/UDP relay then causes routing
problems as the white server is by default unaware of a route for
the source address (yellow.fxp3). So DNS responses from white do not
get routed back to
On Nov 17, 2007 4:58 PM, Rolf Sommerhalder
[EMAIL PROTECTED] wrote:
Still, I am unsure if the DNS/UDP relay actually behaves correctly,
and if this work-around does make sense.
After a deep dive into the sources of hoststated, my current
understanding is that this is not a problem caused by
On Nov 17, 2007 4:58 PM, Rolf Sommerhalder
[EMAIL PROTECTED] wrote:
Still, I am unsure if the DNS/UDP relay actually behaves correctly,
and if this work-around does make sense.
After a deep dive into the sources of hoststated, my current
understanding is that this is not a problem
On Nov 18, 2007 8:04 AM, Theo de Raadt [EMAIL PROTECTED] wrote:
Oh, one does that by calling bind() beforehands, with the specific
local address one which uses use, instead of 0.0.0.0. With udp this
Thanks Theo for your hint. I look into this in the context of hoststated.
What still puzzles
6 matches
Mail list logo
