After an update, nameserver became a mess

Discussion in 'Installation/Configuration' started by pg001, Jul 21, 2008.

  1. pg001

    pg001 New Member

    After I did an apt-get update, apt-get upgrade on perfect debian etch server, when I tried looking up my DNS records from network-tools.com:

    mydomain.us is just a representation of my true domain.

    It used to be running smoothly and displaying correct records, not it's displaying this:

    Retrieving DNS records for mydomain.us...

    what went wrong, and what did I do wrong?
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Please try to restart the nameserver and then look into syslog for errors.
     
  3. pg001

    pg001 New Member

    I don't see no error till, here's the result when I restart bind9

    Code:
    Jul 22 07:05:29 server1 named[27566]: shutting down: flushing changes
    Jul 22 07:05:29 server1 named[27566]: stopping command channel on 127.0.0.1#953
    Jul 22 07:05:29 server1 named[27566]: stopping command channel on ::1#953
    Jul 22 07:05:29 server1 named[27566]: no longer listening on 127.0.0.1#53
    Jul 22 07:05:29 server1 named[27566]: no longer listening on 192.168.1.101#53
    Jul 22 07:05:29 server1 named[27566]: exiting
    Jul 22 07:05:31 server1 named[1435]: starting BIND 9.3.4-P1.1 -u bind -t /var/lib/named
    Jul 22 07:05:31 server1 named[1435]: found 1 CPU, using 1 worker thread
    Jul 22 07:05:31 server1 named[1435]: loading configuration from '/etc/bind/named.conf'
    Jul 22 07:05:31 server1 named[1435]: listening on IPv4 interface lo, 127.0.0.1#53
    Jul 22 07:05:31 server1 named[1435]: listening on IPv4 interface eth0, 192.168.1.101#53
    Jul 22 07:05:31 server1 named[1435]: command channel listening on 127.0.0.1#953
    Jul 22 07:05:31 server1 named[1435]: command channel listening on ::1#953
    Jul 22 07:05:31 server1 named[1435]: zone 198.3.122.in-addr.arpa/IN: loaded serial 2008070903
    Jul 22 07:05:31 server1 named[1435]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1
    Jul 22 07:05:31 server1 named[1435]: zone myotherdomain1.com/IN: loaded serial 2008070904
    Jul 22 07:05:31 server1 named[1435]: zone myotherdomain2.com/IN: loaded serial 2008070902
    Jul 22 07:05:31 server1 named[1435]: zone myotherdomain3.net/IN: loaded serial 2008070903
    Jul 22 07:05:31 server1 named[1435]: zone mydomain.us/IN: loaded serial 2008070905
    Jul 22 07:05:31 server1 named[1435]: running
    Jul 22 07:05:31 server1 named[1435]: zone myotherdomain4.com/IN: sending notifies (serial 2008070902)
    Jul 22 07:05:31 server1 named[1435]: zone 198.3.122.in-addr.arpa/IN: sending notifies (serial 2008070903)
    Jul 22 07:05:31 server1 named[1435]: zone mydomain.us/IN: sending notifies (serial 2008070905)
    Jul 22 07:05:31 server1 named[1435]: zone myotherdomain1.net/IN: sending notifies (serial 2008070903)
    Jul 22 07:05:31 server1 named[1435]: zone myotherdomain2.com/IN: sending notifies (serial 2008070904)
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    Ok, this means that bind is started. Please check with:

    netstat -tap

    if bind is really running. If it is running, query the local server for your domain:

    dig @localhost mydomain.us
     

Share This Page