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

2013-01-22 Thread Mark Andrews
In message <20130122142136.ga21...@fantomas.sk>, Matus UHLAR - fantomas writes: > On 22.01.13 11:18, Daniele wrote: > >My router doesn't maintain a DNS cache, so it must be my IPS's fault. > > > >The last questions, if it's possible: what happens when my 'named' starts > >an iterative query? Does

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

2013-01-22 Thread Warren Kumari
On Jan 22, 2013, at 5:18 AM, Daniele wrote: > Ok! Thank you all! > > My router doesn't maintain a DNS cache, And what are you basing this upon? W > so it must be my IPS's fault. > > The last questions, if it's possible: what happens when my 'named' starts an > iterative query? Does it arri

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

2013-01-22 Thread Matus UHLAR - fantomas
On 22.01.13 11:18, Daniele wrote: My router doesn't maintain a DNS cache, so it must be my IPS's fault. The last questions, if it's possible: what happens when my 'named' starts an iterative query? Does it arrive to the real root-server (first of all), it should, but it appears that it does no

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

2013-01-22 Thread Daniele
Ok! Thank you all! My router doesn't maintain a DNS cache, so it must be my IPS's fault. The last questions, if it's possible: what happens when my 'named' starts an iterative query? Does it arrive to the real root-server (first of all), or is it processed by some other cache-server on the path?

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

2013-01-18 Thread Mark Andrews
In message , Daniele writes: > These are the outputs. I also attach the file containing them. > > > ; <<>> DiG 9.8.1-P1 <<>> ns . +norec +noedns @198.41.0.4 > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25625 > ;; flags: qr ra; QUERY: 1, ANSWE

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

2013-01-18 Thread Warren Kumari
On Jan 18, 2013, at 9:44 AM, Daniele wrote: > These are the outputs. I also attach the file containing them. > > [ SNIP ] Weird…. Do things work well enough for: dig +short rs.dns-oarc.net txt ? Can you also do: the following queries starting with the slightly less plain DNS query

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

2013-01-18 Thread Daniele
These are the outputs. I also attach the file containing them. ; <<>> DiG 9.8.1-P1 <<>> ns . +norec +noedns @198.41.0.4 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25625 ;; flags: qr ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 14 ;; QUESTION

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

2013-01-17 Thread Mark Andrews
What are the answers to the following queries starting with the very basic plain DNS query dig ns . +norec +noedns @198.41.0.4 Now add in EDNS support dig ns . +norec +edns @198.41.0.4 Now add in DNSEC support dig ns . +norec +dnssec @198.41.0.4 Please post the respon

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

2013-01-17 Thread Daniele
For example, also a `dig a.root-servers.net` fails with SERVFAIL, but in Wireshark I can see the packet with the correct response that arrives at my network interface. 2013/1/17 Daniele > Output for `dig NS .` > ; <<>> DiG 9.8.1-P1 <<>> @127.0.0.1 NS . > ; (1 server found) > ;; global options:

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

2013-01-17 Thread Daniele
Output for `dig NS .` ; <<>> DiG 9.8.1-P1 <<>> @127.0.0.1 NS . ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 37032 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;.INNS

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

2013-01-17 Thread Warren Kumari
On Jan 17, 2013, at 9:04 AM, Daniele wrote: > I'm going crazy. > > This is my named.conf > > logging { > > channel default_logfile { > file "/var/cache/bind/logs/default.log"; > severity info; > print-category yes; > prin

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

2013-01-17 Thread Daniele
I'm going crazy. This is my named.conf logging { channel default_logfile { file "/var/cache/bind/logs/default.log"; severity info; print-category yes; print-severity yes; print-time yes; }; c

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

2013-01-15 Thread Chris Thompson
On Jan 14 2013, Shane Kerr wrote: [...] You may want to try: dig +trace www.isc.org [...] The next step may be to try: dig +trace +dnssec www.isc.org Beware that if you have a dig(1) from BIND 9.9.x, +dnssec has become the default with +trace. In that case replace the first attempt with

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

2013-01-14 Thread Leonard Mills
e: lame-servers: error (FORMERR) resolving [something] > > >What tests should I do? >If I query directly an external name-server (one of the root ones or 8.8.8.8 >for example) I receive the correct response. >For this reason I'm inclined to think that the router doesn&#

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

2013-01-14 Thread Shane Kerr
Daniele, It may be a simple case of your firewall not allowing any DNS queries that do not request recursion. Difficult to know. You may want to try: dig +trace www.isc.org This will follow the referrals from the root, and you can verify that this works. The next step may be to try: dig +trac

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

2013-01-14 Thread Daniele
What tests should I do? If I query directly an external name-server (one of the root ones or 8.8.8.8 for example) I receive the correct response. For this reason I'm inclined to think that the router doesn't block packets to/from port 53. Why should it block packets generated by BIND9? 2013/1/12

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: 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

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

2013-01-09 Thread Lyle Giese
On 01/09/13 08:39, Daniele wrote: 2013/1/9 Phil Mayers > On 09/01/13 13:53, Daniele wrote: This is the scenario. I installed BIND9 via `apt-get` on a newly installed UBUNTU 12.04, virtualized on VirtualBox. The network works p

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

2013-01-09 Thread Daniele
2013/1/9 Phil Mayers > On 09/01/13 13:53, Daniele wrote: > >> This is the scenario. >> >> I installed BIND9 via `apt-get` on a newly installed UBUNTU 12.04, >> virtualized on VirtualBox. >> The network works properly because if I indicate a different server from >> my own BIND9 (the first line of

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

2013-01-09 Thread Phil Mayers
On 09/01/13 13:53, Daniele wrote: This is the scenario. I installed BIND9 via `apt-get` on a newly installed UBUNTU 12.04, virtualized on VirtualBox. The network works properly because if I indicate a different server from my own BIND9 (the first line of '/etc/resolv.conf' is, for example, `name

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

2013-01-09 Thread Daniele
the presence of “dnssec-validaton“ line? 2013/1/8 Matus UHLAR - fantomas > > Sometimes I can't resolve some addresses and, in the logs, I can find >>> > the message in the title: >>> >lame-servers: error (FORMERR) resolving [something] >>> > (

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

2013-01-08 Thread Matus UHLAR - fantomas
> Sometimes I can't resolve some addresses and, in the logs, I can find > the message in the title: > lame-servers: error (FORMERR) resolving [something] > (where `something` is the address I'm trying to resolve). > > What does it means? 2013/1/8 Shane Kerr

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

2013-01-08 Thread Daniele
57 +0100, > Daniele wrote: > > Hi all. > > > > Sometimes I can't resolve some addresses and, in the logs, I can find > > the message in the title: > >lame-servers: error (FORMERR) resolving [something] > > (where `something` is the address I'm

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

2013-01-08 Thread Shane Kerr
Daniele, On Tuesday, 2013-01-08 09:49:57 +0100, Daniele wrote: > Hi all. > > Sometimes I can't resolve some addresses and, in the logs, I can find > the message in the title: > lame-servers: error (FORMERR) resolving [something] > (where `something` is the addres

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

2013-01-08 Thread Daniele
Hi all. Sometimes I can't resolve some addresses and, in the logs, I can find the message in the title: lame-servers: error (FORMERR) resolving [something] (where `something` is the address I'm trying to resolve). What does it means? And how can I resolve this problem?