Hi, first time posting to this list, and first time using NSD. I decided to install 1.4.0-Alpha1 and everything seemed to install ok, but I can't get it running correctly. I followed the instructions in the README to the letter. There were no errors while installing. The specific problem I have is when I try to dig test.rilextechnologies.com I get the error: ;; Got bad packet: bad compression pointer 88 bytes 34 5a 85 00 00 01 00 02 00 01 00 00 04 74 65 73 74 11 72 69 6c 65 78 74 65 63 68 6e 6f 6c 6f 67 69 65 73 03 63 6f 6d 00 00 01 00 01 c0 0c 00 05 00 01 00 01 51 80 00 02 c3 73 c3 73 00 01 00 01 00 01 51 80 00 04 42 c2 77 82 c0 11 00 02 00 01 00 01 51 80 00 02 ec 6f I was thinking that this might be an error in my configuration files, but am unsure. Let me know what you think or if you need more information. Thanks Dave
David Coursey wrote:> Hi, first time posting to this list, and first time using NSD. > > I decided to install 1.4.0-Alpha1 and everything seemed to install ok, > but I can't get it running correctly. I followed the instructions in > the README to the letter. There were no errors while installing. > > The specific problem I have is when I try to dig > test.rilextechnologies.com I get the error: > > ;; Got bad packet: bad compression pointer > 88 bytes > 34 5a 85 00 00 01 00 02 00 01 00 00 04 74 65 73 > 74 11 72 69 6c 65 78 74 65 63 68 6e 6f 6c 6f 67 > 69 65 73 03 63 6f 6d 00 00 01 00 01 c0 0c 00 05 > 00 01 00 01 51 80 00 02 c3 73 c3 73 00 01 00 01 > 00 01 51 80 00 04 42 c2 77 82 c0 11 00 02 00 01 > 00 01 51 80 00 02 ec 6f > > I was thinking that this might be an error in my configuration files, > but am unsure. > > Let me know what you think or if you need more information.Definitely an NSD bug (it should never respond with bad packets), even though it may be triggered by strange zone files. Could you send me a copy of the zone and configuration file as well as the dig command you used? Also, what platform are you running NSD on (OS, cpu, etc)? Thanks, Erik
I get that fairly often when I add a new domain. I have to restart nsd. It also happens when there is some bad info in the zone file. (I don't remember what triggers it, but I can try and duplicate it if people want me to.) On Tue, Dec 16, 2003 at 11:25:30AM -0500, David Coursey wrote: :Hi, first time posting to this list, and first time using NSD. : :I decided to install 1.4.0-Alpha1 and everything seemed to install ok, :but I can't get it running correctly. I followed the instructions in :the README to the letter. There were no errors while installing. : :The specific problem I have is when I try to dig :test.rilextechnologies.com I get the error: : :;; Got bad packet: bad compression pointer :88 bytes :34 5a 85 00 00 01 00 02 00 01 00 00 04 74 65 73 :74 11 72 69 6c 65 78 74 65 63 68 6e 6f 6c 6f 67 :69 65 73 03 63 6f 6d 00 00 01 00 01 c0 0c 00 05 :00 01 00 01 51 80 00 02 c3 73 c3 73 00 01 00 01 :00 01 51 80 00 04 42 c2 77 82 c0 11 00 02 00 01 :00 01 51 80 00 02 ec 6f : :I was thinking that this might be an error in my configuration files, :but am unsure. : :Let me know what you think or if you need more information. :Thanks : :Dave : :_______________________________________________ :nsd-users mailing list :nsd-users at NLnetLabs.nl :http://open.nlnetlabs.nl/mailman/listinfo/nsd-users
I did an 'nsdc restart' as shown on Peter's page here: http://theapt.org/nsd-compression.txt and I'm not getting the bad packet error anymore. Now it just shows: ; <<>> DiG 9.2.2-P3 <<>> www.rilextechnologies.com ;; global options: printcmd ;; connection timed out; no servers could be reached