Re: lame-servers: error (FORMERR) resolving [something]

2013-01-11 Thread Lyle Giese
On 01/11/13 03:05, Daniele wrote: Port 53 is open, I can also telnet it from another box in the same network. Now I think the problem can be on the packets size, because I'm trying every solution but nothing works. 2013/1/9 Lyle Giese mailto:l...@lcrcomputer.net>> On 01/09/13 08:39, Dani

Re: Logging

2013-01-11 Thread Dave Sparro
On 1/8/2013 8:19 AM, Timothe Litt wrote: What I think would be more useful is if named actually reported the issues to where they'd do some good. Perhaps a DNS extension "I got an invalid message from you" - so it shows up in the log of the server (and administrator) with the problem. (I'd wo

Re: Noisy messages from BIND about root hints change

2013-01-11 Thread Cathy Almond
On 07/01/13 17:14, Chris Thompson wrote: > One (but only one) of our recursive nameservers, running BIND 9.8.3-P4 > we got a whole lot of messages in the log as a result of last week's change > of address for d.root-servers.net: > > Jan 4 06:24:08 recdns1.csx.cam.ac.uk named[9496]: general: warni

Re: lame-servers: error (FORMERR) resolving [something]

2013-01-11 Thread Daniele
Port 53 is open, I can also telnet it from another box in the same network. Now I think the problem can be on the packets size, because I'm trying every solution but nothing works. 2013/1/9 Lyle Giese > On 01/09/13 08:39, Daniele wrote: > > 2013/1/9 Phil Mayers > >> On 09/01/13 13:53, Daniele