primary nameserver has stopped working after upgrade

Discussion in 'HOWTO-Related Questions' started by john943, Jul 8, 2016.

  1. john943

    john943 New Member

    Hello,
    I have had my multiserver setup running for a while on debian squeeze with ispconfig 3.0.5.4p8, every thing was fine until my primary nameserver crashed. The hard drive was removed and put into an identical machine. And reconnected to the network. After that I found that I could no longer ssh the machine from putty using the hostname or public ip, how ever putty can connect using the private ip. I can ssh to the server from all other servers on the network with no problem. I have run dig @81.174.238.218 kooga.com and get :
    Code:
    ; <<>> DiG 9.7.3 <<>> @81.174.238.218 kooga.com
    ; (1 server found)
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63907
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
    ;; WARNING: Messages has 2 extra bytes at end
    
    ;; QUESTION SECTION:
    ;kooga.com.                  IN      A
    
    ;; ANSWER SECTION:
    kooga.com.           60      IN      A       81.174.238.220
    
    ;; Query time: 0 msec
    ;; SERVER: 81.174.238.218#53(81.174.238.218)
    ;; WHEN: Thu Feb 10 02:30:50 2005
    ;; MSG SIZE  rcvd: 48
    
    dig @localhost kooga.com returns :

    Code:
    ; <<>> DiG 9.7.3 <<>> @localhost kooga.com
    ; (1 server found)
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36490
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
    
    ;; QUESTION SECTION:
    ;kooga.com.                  IN      A
    
    ;; ANSWER SECTION:
    kooga.com.           3600    IN      A       81.174.238.220
    
    ;; AUTHORITY SECTION:
    kooga.com.           3600    IN      NS      ns1.kooga.com.
    kooga.com.           3600    IN      NS      ns0.kooga.com.
    
    ;; ADDITIONAL SECTION:
    ns0.kooga.com.       3600    IN      A       81.174.238.218
    ns1.kooga.com.       3600    IN      A       81.174.238.219
    
    ;; Query time: 0 msec
    ;; SERVER: 127.0.0.1#53(127.0.0.1)
    ;; WHEN: Thu Feb 10 02:44:05 2005
    ;; MSG SIZE  rcvd: 114
    
    I have also checked the domain at intodns and get back :

    Could I get some advice as to how to rectify the problem. Thanks!
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Check the syslog on the 218 server for named / bind errors and try to restart bind. And check the /etc/hosts files on the system to see if it contains the correct IP addresses.
     
  3. john943

    john943 New Member

    Hi Till,
    I have looked in the var/log/syslog for named / bind errors but couldn't make much sense of it, would you mind looking at it for me?, if so please see syslog.txt

    I have looked at /etc/hosts file and it seems ok :

    Code:
    127.0.0.1       localhost
    192.168.1.11    ns0.kooga.com
    192.168.1.12    ns1.kooga.com
    192.168.1.13    web.kooga.com
    192.168.1.17    db.kooga.com
    192.168.1.15    mail.kooga.com
    
    # The following lines are desirable for IPv6 capable hosts
    ::1     ip6-localhost ip6-loopback
    fe00::0 ip6-localnet
    ff00::0 ip6-mcastprefix
    ff02::1 ip6-allnodes
    ff02::2 ip6-allrouters
    I can restart bind without any errors. Thank you very much for your time!
     

    Attached Files:

  4. john943

    john943 New Member

    problem solved, it was the router,

    thanks for the advice Till:)
     

Share This Page