nach i-MSCP installation keine DNS Auflösung mehr möglich

**Nuxwin** · Jul 31st 2014

Please, give me an SSH access to the server (also the SQL root password).

**FISA4** · Jul 31st 2014

i´ve installed it 2 minutes ago fresh. SSH comes with PM

**Nuxwin** · Jul 31st 2014

Ok. I wait for credential I'll process some tests. I'll check the status of the DNS server after update and also after a reboot.

**Nuxwin** · Jul 31st 2014

@FISA4

In ~ 3 seconds, I've found the reason of your problem:

Shell-Script

root@green:~# service bind9 status
[FAIL] bind9 is not running ... failed!
root@green:~#

Here, your DNS server (which is the local resolver) is down. This explain why you cannot resolve any external domain name such as google.com. Even worse, you cannot resolve any sites (including those which are created through i-MSCP). I'll now check why your DNS is down

**FISA4** · Jul 31st 2014

Quote from Nuxwin

@FISA4

In ~ 3 seconds, I've found the reason of your problem:

Code

root@green:~# service bind9 status

[FAIL] bind9 is not running ... failed!

root@green:~#

Here, your DNS server (which is the local resolver) is down. This explain why you cannot resolve any external domain name such as google.com. Even worse, you cannot resolve any sites (including those which are created through i-MSCP). I'll now check why your DNS is down

Display More

it´s normal on a fresh installed linux.

**Nuxwin** · Jul 31st 2014

@FISA4

Ok, I'll so install i-MSCP and see

**Nuxwin** · Jul 31st 2014

@FISA4

I've installed i-MSCP (All goes fine)
ping, dig on google.fr (All goes fine)
Reboot
ping, dig on google.fr Nothing is working...)
service bind9 status:

Shell-Script

root@green:~# service bind9 status[FAIL] bind9 is not running ... failed!root@green:~#

I'll so now check why bind9 (your local resolver) is down after reboot.

Edit: After starting bind9 manually, all goes fine. I'll so check the lsb headers to make sure bind9 start before the imscp_network service.

Shell-Script

root@green:~# service bind9 start[ ok ] Starting domain name service...: bind9.root@green:~# dig google.fr; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> google.fr;; global options: +cmd;; Got answer:;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55013;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0;; QUESTION SECTION:;google.fr. IN A;; ANSWER SECTION:google.fr. 300 IN A 173.194.113.24google.fr. 300 IN A 173.194.113.31google.fr. 300 IN A 173.194.113.15google.fr. 300 IN A 173.194.113.23;; Query time: 315 msec;; SERVER: 127.0.0.1#53(127.0.0.1);; WHEN: Thu Jul 31 02:02:11 2014;; MSG SIZE rcvd: 91root@green:~#

Shell-Script

root@green:~# cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1
root@green:~#

**Nuxwin** · Jul 31st 2014

@FISA4

It's really strange because after a reboot, bind9 is not running. I must investigate. Give me some minutes please

Shell-Script

root@green:/etc/init.d# shutdown -r now
root@green:/etc/init.d#
Broadcast message from root@green
(/dev/pts/0) at 2:07 ...
The system is going down for reboot NOW!
Connection to 7x.4x.9x.2x6 closed by remote host.
Connection to 7x.4x.9x.2x6 closed.
nuxwin@dev:~$ ssh root@7x.4x.9x.2x6
root@7x.4x.9x.2x6's password:
Linux green 2.6.32-openvz-042stab090.3-amd64 #1 SMP Fri Jun 6 09:42:35 MSK 2014 x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu Jul 31 01:58:39 2014 from 109.14.46.46
root@green:~# netstat -plunt
Connexions Internet actives (seulement serveurs)
Proto Recv-Q Send-Q Adresse locale Adresse distante Etat PID/Program name
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 1774/apache2
tcp 0 0 0.0.0.0:465 0.0.0.0:* LISTEN 2817/master
tcp 0 0 127.0.0.1:9876 0.0.0.0:* LISTEN 2595/imscp_daemon
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1707/sshd
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 2817/master
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 1774/apache2
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 2851/smbd
tcp 0 0 127.0.0.1:10023 0.0.0.0:* LISTEN 2442/postgrey.pid -
tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 2239/mysqld
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 2851/smbd
tcp 0 0 0.0.0.0:587 0.0.0.0:* LISTEN 2817/master
tcp 0 0 127.0.0.1:12525 0.0.0.0:* LISTEN 2362/policyd-weight
tcp6 0 0 :::110 :::* LISTEN 2572/couriertcpd
tcp6 0 0 :::143 :::* LISTEN 2513/couriertcpd
tcp6 0 0 :::21 :::* LISTEN 2883/proftpd: (acce
tcp6 0 0 :::22 :::* LISTEN 1707/sshd
tcp6 0 0 :::445 :::* LISTEN 2851/smbd
tcp6 0 0 :::993 :::* LISTEN 2548/couriertcpd
tcp6 0 0 :::995 :::* LISTEN 2585/couriertcpd
tcp6 0 0 :::139 :::* LISTEN 2851/smbd
udp 0 0 7x.4x.9x.2x6:1x7 0.0.0.0:* 2848/nmbd
udp 0 0 7x.4x.9x.2x6:1x7 0.0.0.0:* 2848/nmbd
udp 0 0 127.0.0.2:137 0.0.0.0:* 2848/nmbd
udp 0 0 127.0.0.2:137 0.0.0.0:* 2848/nmbd
udp 0 0 0.0.0.0:137 0.0.0.0:* 2848/nmbd
udp 0 0 7x.4x.9x.2x6:1x8 0.0.0.0:* 2848/nmbd
udp 0 0 7x.4x.9x.2x6:1x8 0.0.0.0:* 2848/nmbd
udp 0 0 127.0.0.2:138 0.0.0.0:* 2848/nmbd
udp 0 0 127.0.0.2:138 0.0.0.0:* 2848/nmbd
udp 0 0 0.0.0.0:138 0.0.0.0:* 2848/nmbd
root@green:~#

Display More

**FISA4** · Jul 31st 2014

Nuxwin: no problem. take as much time as you need.

now you can see, i did no crap.
and you know, if i have a problem, then it is a big one.

**FISA4** · Jul 31st 2014

you forgot 1 ip - line 10

nach i-MSCP installation keine DNS Auflösung mehr möglich

Share

Daily visitors