ispCP - Board - Support
Bind problem - Printable Version

+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Support Area (/forum-30.html)
+--- Forum: System Setup & Installation (/forum-32.html)
+--- Thread: Bind problem (/thread-8491.html)

Bind problem - by_maximus - 11-19-2009 11:32 AM

root@server:/etc/bind# netstat -tlnp | grep named
tcp 0 0 127.0.0.1:953 0.0.0.0:* OUÇA 1
7757/named
tcp 0 0 10.1.229.12:53 0.0.0.0:* OUÇA 1
7757/named
tcp 0 0 10.1.229.11:53 0.0.0.0:* OUÇA 1
7757/named
tcp 0 0 174.142.73.187:53 0.0.0.0:* OUÇA 1
7757/named
tcp 0 0 127.0.0.1:53 0.0.0.0:* OUÇA 1
7757/named
tcp6 0 0 ::1:953 :::* OUÇA 1
7757/named
tcp6 0 0 :::53 :::* OUÇA 1
7757/named


the panel this configured for the IP 174.142.73.186 and why bind this only twirling in the 187?

RE: Bind problem - Nuxwin - 11-19-2009 03:23 PM

Hello ;

Not worry about that. In my opinion, that is an faulty information. Under Debian, Bind9 listens on all interface normally. See your /etc/named.conf.options for that issue.

Code:
ispcp:/etc/bind# netstat -plunt | grep named
tcp        0      0 192.168.0.130:53        0.0.0.0:*               LISTEN      14391/named    
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      14391/named    
tcp        0      0 127.0.0.1:953           0.0.0.0:*               LISTEN      14391/named    
tcp6       0      0 :::53                   :::*                    LISTEN      14391/named    
tcp6       0      0 ::1:953                 :::*                    LISTEN      14391/named    
udp        0      0 192.168.0.130:53        0.0.0.0:*                           14391/named    
udp        0      0 127.0.0.1:53            0.0.0.0:*                           14391/named    
udp6       0      0 :::53

Adn After adding a new Ip (192.168.0.140) (from the frontend as admin user), and restarted Bind9 :

Code:
ispcp:/etc/bind# netstat -plunt | grep named
tcp        0      0 192.168.0.140:53        0.0.0.0:*               LISTEN      16649/named    
tcp        0      0 192.168.0.130:53        0.0.0.0:*               LISTEN      16649/named    
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      16649/named    
tcp        0      0 127.0.0.1:953           0.0.0.0:*               LISTEN      16649/named    
tcp6       0      0 :::53                   :::*                    LISTEN      16649/named    
tcp6       0      0 ::1:953                 :::*                    LISTEN      16649/named    
udp        0      0 192.168.0.140:53        0.0.0.0:*                           16649/named    
udp        0      0 192.168.0.130:53        0.0.0.0:*                           16649/named    
udp        0      0 127.0.0.1:53            0.0.0.0:*                           16649/named    
udp6       0      0 :::53                   :::*                                16649/named

Conclusion : Not worry about that. Wink

RE: Bind problem - by_maximus - 11-24-2009 09:27 AM

I only understood that in mine in case that, in the register of the domain it only this catching ns2, ns1 it accuses depleted time

RE: Bind problem - by_maximus - 11-25-2009 12:32 PM

any reply?