Re: how do I get a slave to send NOTIFY messages?

2010-01-31 Thread Mark Andrews
In message <20100131220833.a16...@gwyn.tux.org>, Joseph S D Yao writes: > The ARM, in Chapter 6, under Boolean Options [for some value of the word > "Boolean", I guess ;-)], says: Well it started out as a Boolean Option. :-) Boolean/Enumerated Options would be a more accurate description these da

Re: how do I get a slave to send NOTIFY messages?

2010-01-31 Thread Joseph S D Yao
On Fri, Jan 29, 2010 at 10:11:43PM -0500, Frank Cusack wrote: ... > hosts. zytrax does say that also-notify only applies to type master > servers however I can't find confirmation of that anywhere else. ... I don't believe that this is the case - I'm using them on servers serving copies of the z

Re: how do I get a slave to send NOTIFY messages?

2010-01-31 Thread Matus UHLAR - fantomas
On 29.01.10 22:11, Frank Cusack wrote: > I have also-notify configured for a slave zone. The real master is a > so-called stealth master and all other slaves must consult this slave > nameserver that has also-notify configured. > > The slave doesn't appear to be sending NOTIFY messages to the also

Re: NOTIFY logging problem

2010-01-31 Thread Mark Andrews
In message , Frank Cusack writes: > On February 1, 2010 11:35:15 AM +1100 Mark Andrews wrote: > > You need to be looking a debug 3. > > > > notify_log(notify->zone, ISC_LOG_DEBUG(3), "sending notify to %s", > >addrbuf); > > ouch, debug 3 is probably way TMI. I guess

Re: NOTIFY logging problem

2010-01-31 Thread Frank Cusack
On February 1, 2010 11:35:15 AM +1100 Mark Andrews wrote: You need to be looking a debug 3. notify_log(notify->zone, ISC_LOG_DEBUG(3), "sending notify to %s", addrbuf); ouch, debug 3 is probably way TMI. I guess I'll just patch the above to log at info. Why isn't

Re: NOTIFY logging problem

2010-01-31 Thread Mark Andrews
In message , Frank Cusack writes: > How can I get logs of all NOTIFY messages sent? > > logging { > // use local0 instead of daemon > channel local0_syslog { > syslog local0; > severity info; > }; > category notify{ local0_syslog; default_debug; }; > }; > > The above only ge

Re: Deny MX queries for dynamic IP pools

2010-01-31 Thread Noel Butler
Firstly, I feel this really belongs on mailops not bind list :) secondly... On Mon, 2010-02-01 at 00:00 +0300, Wael Shaheen wrote: > Blocking port 25 is much worse IMHO because it forces users out of the > service, by restricting their ability to use their own mail servers that can > be hosted e

Re: Deny MX queries for dynamic IP pools

2010-01-31 Thread Mark Andrews
In message , Wael Shaheen writes: > Dear DNS Experts, > > This post is intended for discussion. > > The ISP I work for has HUGE dynamic IP pools that are full of spammers (of > course). This huge volume of spam is actually influencing the decision for > some of the international provider=B9s whe

Re: Deny MX queries for dynamic IP pools

2010-01-31 Thread Jason W.
On Sun, Jan 31, 2010 at 8:25 AM, Wael Shaheen wrote: > As a solution the routing team was thinking to block port 25 for outgoing as > some ISPs do. However, I do not see this to be a valid solution for many > reasons such as clients that have email servers outside, or if decided to be > redirecte

Re: Deny MX queries for dynamic IP pools

2010-01-31 Thread SM
At 05:25 31-01-10, Wael Shaheen wrote: As a solution the routing team was thinking to block port 25 for outgoing as some ISPs do. However, I do not see this to be a valid solution for many reasons such as clients that have email servers outside, or if decided to be redirected to spam filters then

Re: Deny MX queries for dynamic IP pools

2010-01-31 Thread Wael Shaheen
Hi, On 1/31/10 5:28 PM, "Sten Carlsen" wrote: > To me this seems to be a firewall/routing issue. If you know for sure > that some IP is sending spam, if you can not stop them, then at least > you can block their outgoing access to port 25. Most of the RBLs list dynamic IP addresses for they sh

Re: Deny MX queries for dynamic IP pools

2010-01-31 Thread Wael Shaheen
Hi, On 1/31/10 5:17 PM, "Sven Eschenberg" wrote: > Dear Wael, > > In what way is blocking Port 25 any worse than blocking MX/root queries > for clients? Both solutions neglect the fact, that spam is not a technical > problem. This spam issue is major for DSPs and large ISPs. Their reputation

Re: Deny MX queries for dynamic IP pools

2010-01-31 Thread Sten Carlsen
To me this seems to be a firewall/routing issue. If you know for sure that some IP is sending spam, if you can not stop them, then at least you can block their outgoing access to port 25. Alternatively and maybe better arrange for a proxy server to do filtering and discard spam. The proxy solution

Re: Deny MX queries for dynamic IP pools

2010-01-31 Thread Sven Eschenberg
Dear Wael, In what way is blocking Port 25 any worse than blocking MX/root queries for clients? Both solutions neglect the fact, that spam is not a technical problem. Some ISPs think it is a good idea to forward you to a search web page, when you mispell some URL, this is done via DNS. Obviously,

Deny MX queries for dynamic IP pools

2010-01-31 Thread Wael Shaheen
Dear DNS Experts, This post is intended for discussion. The ISP I work for has HUGE dynamic IP pools that are full of spammers (of course). This huge volume of spam is actually influencing the decision for some of the international providerĀ¹s whether to give us links or not let alone the bad repu