RE: Message parser reports malformed message packet

Continuing investigating the issue, I noticed the following lines: ;; Warning: Message parser reports malformed message packet. ;; Truncated, retrying in TCP mode. ;; Connection to 201.76.40.2#53(201.76.40.2) for www.sondait.tasker.com.br failed: connection refused. Even if m

RE: Message parser reports malformed message packet

Thank you, Mark. I'm gonna try to contact the domain owners as well, but I noticed my enterprise DNS can get a correct answer for that domain. Is there any way I can force different response from localweb servers until I got this permanently fixed? Like force UDP packet sizes or disable EDNS fo

Message parser reports malformed message packet

Hi,   I'm having issues trying to resolve www.sondait.tasker.com.br. The result from dig +trace is as follows: # dig www.sondait.tasker.com.br +trace ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6_4.6 <<>> www.sondait.tasker.com.br +trace ;; global options: +cmd .   516836

RE: rndc usage

> Date: Thu, 26 Sep 2013 11:35:04 -0400 > Subject: Re: rndc usage > From: wolfs...@gmail.com > To: flg...@hotmail.com > CC: bind-users@lists.isc.org > > On Thu, Sep 26, 2013 at 11:28 AM, Fábio Gomes wrote: >> Hi, >> >

rndc usage

Hi,   I'm trying to force a reload in my slave server using RNDC, but I receiving the following error: # rndc reload mydomain.com rndc: 'reload' failed: not found   Using only "rndc reload" works. But I can't use it pointing to a single domain. Thanks ___

Update from 9.2.1 to 9.8.2 rc1

Hi,   We are in a process to upgrade a really old server running an old Linux distro with Bind 9.2.1. The new server will be a Red Hat EL 6.4 which comes with Bind 9.8.2.   Will my old configuration files work with this new Bind version? Any tips regarding this update? Thank you for the help!