Re: cache poisoning

2009-08-11 Thread Matus UHLAR - fantomas
On 11.08.09 13:27, Nelson Serafica wrote: I need to set bind to listen to all address. I'm using AMAZON EC2 no, you don't. you configure listening IPs/ports by using listen-on and listen-on-v6. query-source only configures from which IP/port will your requests come from. -- Matus UHLAR -

Re: cache poisoning

2009-08-10 Thread Mark Andrews
In message 4a80e783.4090...@gmail.com, Nelson Serafica writes: Last year, there was a global threat about cache poisoning so I updated immed iately my bind. I update it to BIND 9.5.0-P1 and did nothing to its named.conf You should have at least checked the query-source clauses

Re: cache poisoning

2009-08-10 Thread Nelson Serafica
Thanks Mark! it works. I change my query source to one of the entry below and it works. Mark Andrews wrote: query-source * port 53; // bad query-source 10.53.0.1; // ok query-source *; // ok (default) query-source-v6 * port 53; // bad

Re: cache poisoning

2009-08-10 Thread Bill Larson
On Aug 10, 2009, at 10:06 PM, Nelson Serafica wrote: Thanks Mark! it works. I change my query source to one of the entry below and it works. Maybe a strange question. Why did you have a query source statement in your configuration in the first place? Bill Larson Mark Andrews wrote:

Re: cache poisoning

2009-08-10 Thread Nelson Serafica
I need to set bind to listen to all address. I'm using AMAZON EC2 Maybe a strange question. Why did you have a query source statement in your configuration in the first place? ___ bind-users mailing list bind-users@lists.isc.org

Re: cache poisoning counter-measures

2009-01-05 Thread Matus UHLAR - fantomas
On 05.01.09 15:29, Chris Henderson wrote: I'm trying to implement some basic counter-measures against the Kaminsky bug. I have had to configure my switch to allow any incoming query to TCP and UDP port 53 on my slave DNS server. I was wondering if this is going to cause any problem as far as