DNS Issue

Discussion in 'Server Operation' started by Renegade, Sep 14, 2006.

  1. Renegade

    Renegade New Member

    Hello

    I got an issue with rndc. I've read a lot about it en there are many people with the same problem but i can't solve it. I generated a new key but that wasn't the solution. The key i use is the same in named.conf;rndc.conf and rndc.key

    on my first dns i use ubuntu 5.1o en my second dns ubuntu 6.0.6.

    The error i got is.

    rndc: connection to remote host closed
    This may indicate that the remote server is using an older version of
    the command protocol, this host is not authorized to connect,
    or the key is invalid.

    When i check the version with: rndc -V the first dns tells me that i'm using Version: 9.3.1 and the second dns is using Version: 9.3.2

    Could this be the problem and if it is how can i solved the problem?
     
  2. falko

    falko Super Moderator ISPConfig Developer

    What's in the logs? What's in your named.conf?
     
  3. Renegade

    Renegade New Member

    named.conf

    # cat /etc/bind/named.conf

    key "rndc-key" {
    algorithm hmac-md5;
    secret "5Zmlv/bRToWX6Ilr0lXjbw==";
    };

    controls {
    inet 127.0.0.1 port 953
    allow { 127.0.0.1; } keys { "rndc-key"; };
    };

    # cat /etc/bind/rndc.conf
    key "rndc-key" {
    algorithm hmac-md5;
    secret "5Zmlv/bRToWX6Ilr0lXjbw==";
    };

    options {
    default-key "rndc-key";
    default-server 127.0.0.1;
    default-port 953;

    # cat /etc/bind/rndc.key
    key "rndc-key" {
    algorithm hmac-md5;
    secret "5Zmlv/bRToWX6Ilr0lXjbw==";
    };


    And in my sylog:

    Sep 15 22:12:41 ns1 named[7935]: invalid command from 127.0.0.1#53907: bad auth
    Sep 15 22:12:44 ns1 named[16949]: starting BIND 9.3.1 -u bind -t /var/lib/named
    Sep 15 22:12:44 ns1 named[16949]: found 1 CPU, using 1 worker thread
    Sep 15 22:12:44 ns1 named[16949]: loading configuration from '/etc/bind/named.conf'
    Sep 15 22:12:44 ns1 named[16949]: listening on IPv4 interface lo, 127.0.0.1#53
    Sep 15 22:12:44 ns1 named[16949]: binding TCP socket: address in use
    Sep 15 22:12:44 ns1 named[16949]: listening on IPv4 interface eth2, 87.249.102.250#53
    Sep 15 22:12:44 ns1 named[16949]: binding TCP socket: address in use
    Sep 15 22:12:44 ns1 named[16949]: /etc/bind/named.conf:131: couldn't add command channel 127.0.0.1#953: address in use
    Sep 15 22:12:44 ns1 named[16949]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1

    I'll hope you can help me.
     
    Last edited: Sep 16, 2006
  4. falko

    falko Super Moderator ISPConfig Developer

    Did you kill all previous BIND processes before you tried to start it?
     
  5. Renegade

    Renegade New Member

    Thanks Falko

    I didn't know the solution was so easy. Thanks
     
  6. ilushkin

    ilushkin New Member

    what was the solution? can you help me please. I have this in my syslog:
    11:19:16 server1 named[5676]: binding TCP socket: address in use
    Nov 3 11:19:16 server1 named[5676]: listening on IPv4 interface eth0, 192.168.1.3#53
    Nov 3 11:19:16 server1 named[5676]: binding TCP socket: address in use
    Nov 3 11:19:16 server1 named[5676]: couldn't add command channel 127.0.0.1#953: address in use
    Nov 3 11:19:16 server1 named[5676]: couldn't add command channel ::1#953: address in use
    I have Ubuntu 6.10 server fresh install
     
  7. falko

    falko Super Moderator ISPConfig Developer

    What's the output of
    Code:
    netstat -tap
    ? Do you get any error messages when you restart BIND?
     
  8. jon

    jon Member HowtoForge Supporter

    This also helped me after an upgrade from Etch to Lenny, thanks!
     

Share This Page