testing bind-dlz

Adam Tkac atkac at redhat.com
Wed Dec 12 11:16:31 UTC 2007

On Wed, Dec 12, 2007 at 04:23:46PM +0530, Agnello George wrote:
> > This is not BIND related but you will try something like:
> >
> > $ tcpdump -ni <interface> port <port>
> >
> > where interface is name of network interface which is used for
> > communication between named <-> mysql and port is number of port where
> > mysql listens. You could also use -w <filename> option and capture
> > trafic to file which is viewable with ethereal or wireshark utilities.
> >
> > Adam
> >
> I did as per you instruction ( i am using a virtual private server {VPS} )  :
>  [root at TestDNS i386]# tcpdump -ni venet0:0 port 53

Are you sure that mysql server listens on port 53? Use port where
mysqld listens, not where named listens. If you're using virtual
machine I think venet0:0 is virtual interface (network bridge).
tcpdump has sometimes problem with that. Please use physical interface
on where is that virtual one created (eth0 etc..)

> tcpdump: WARNING: arptype 65535 not supported by libpcap - falling
> back to cooked socket
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on venet0:0, link-type LINUX_SLL (Linux cooked), capture size 96 bytes
> then i had to do a ctl+c as i was not getting any out put ....

Because you specified bad port.

> is there a way to connect to the database on command line ?

It should exist but I don't know it because I don't work with mysql.


Adam Tkac, Red Hat, Inc.

More information about the bind-users mailing list