-
Re: problemas com bind
Seguinte.
# tail -f /var/log/messages
Jul 5 19:15:11 spyderlinux named[1079]: shutting down
Jul 5 19:15:11 spyderlinux named[1079]: stopping command channel on 127.0.0.1#953
Jul 5 19:15:11 spyderlinux named[1079]: stopping command channel on 204.232.208.237#953
Jul 5 19:15:11 spyderlinux named[1079]: no longer listening on 127.0.0.1#53
Jul 5 19:15:11 spyderlinux named[1079]: no longer listening on 204.232.208.237#53
Jul 5 19:15:11 spyderlinux named[1079]: exiting
Jul 5 19:15:13 spyderlinux named[14036]: starting BIND 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 -u named -t /var/named/chroot
Jul 5 19:15:13 spyderlinux named[14036]: adjusted limit on open files from 1024 to 1048576
Jul 5 19:15:13 spyderlinux named[14036]: found 4 CPUs, using 4 worker threads
Jul 5 19:15:13 spyderlinux named[14036]: using up to 4096 sockets
Jul 5 19:15:13 spyderlinux named[14036]: loading configuration from '/etc/named.conf'
Jul 5 19:15:13 spyderlinux named[14036]: using default UDP/IPv4 port range: [1024, 65535]
Jul 5 19:15:13 spyderlinux named[14036]: using default UDP/IPv6 port range: [1024, 65535]
Jul 5 19:15:13 spyderlinux named[14036]: listening on IPv4 interface lo, 127.0.0.1#53
Jul 5 19:15:13 spyderlinux named[14036]: listening on IPv4 interface eth0, 204.232.208.237#53
Jul 5 19:15:13 spyderlinux named[14036]: /etc/named.conf:46: using specific query-source port suppresses port randomization and can be insecure.
Jul 5 19:15:13 spyderlinux named[14036]: command channel listening on 127.0.0.1#953
Jul 5 19:15:13 spyderlinux named[14036]: command channel listening on 204.232.208.237#953
Jul 5 19:15:13 spyderlinux named[14036]: data/208.232.204.zone:6: TTL set to prior TTL (10)
Jul 5 19:15:13 spyderlinux named[14036]: zone 208.232.204.in-addr.arpa/IN: loaded serial 2010062911
Jul 5 19:15:13 spyderlinux named[14036]: data/spdnetsecure.zone:6: ignoring out-of-zone data (spdnetsecure.com.br)
Jul 5 19:15:13 spyderlinux named[14036]: zone spdnetsecure.br/IN: loaded serial 2010070111
Jul 5 19:15:13 spyderlinux named[14036]: running
------------------------- || -------------------------- || -------------------------------
# netstat -nlptu
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address Stat e PID/Program name
tcp 0 0 127.0.0.1:465 0.0.0.0:* LIST EN 1445/exim
tcp 0 0 204.232.208.237:53 0.0.0.0:* LIST EN 14036/named
tcp 0 0 127.0.0.1:53 0.0.0.0:* LIST EN 14036/named
tcp 0 0 204.232.208.237:953 0.0.0.0:* LIST EN 14036/named
tcp 0 0 127.0.0.1:953 0.0.0.0:* LIST EN 14036/named
tcp 0 0 127.0.0.1:25 0.0.0.0:* LIST EN 1445/exim
tcp 0 0 127.0.0.1:587 0.0.0.0:* LIST EN 1445/exim
tcp 0 0 ::1:465 :::* LIST EN 1445/exim
tcp 0 0 :::22 :::* LIST EN 1429/sshd
tcp 0 0 ::1:25 :::* LIST EN 1445/exim
tcp 0 0 ::1:587 :::* LIST EN 1445/exim
udp 0 0 0.0.0.0:5353 0.0.0.0:* 1469/avahi-daemon:
udp 0 0 0.0.0.0:53 0.0.0.0:* 14036/named
udp 0 0 204.232.208.237:53 0.0.0.0:* 14036/named
udp 0 0 127.0.0.1:53 0.0.0.0:* 14036/named
udp 0 0 0.0.0.0:48591 0.0.0.0:* 1469/avahi-daemon:
udp 0 0 :::5353 :::* 1469/avahi-daemon:
udp 0 0 :::51613 :::* 1469/avahi-daemon:
-
Re: problemas com bind
bem.. subiu normalmente e está ali, escutando; vamos ver se êle faz o que deve:
lá em /etc/yum.d vc tem os vários *.conf com os enderêços dos repositórios a serem acessados; faça:
dig @127.0.0.1 end.repositorio (só dominio) soa
"só dominio" significa: dominioqualquer.com resulta em dominioqualquer.com (sem o www).
informe o que conseguiu como resultado; pode TAMBÉM experimentar outros dominios (terra.com.br, uol.com.br..)
-
Re: problemas com bind
# dig @127.0.0.1 google.com
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> @127.0.0.1 google.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55651
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 3600 IN A 72.232.183.12
;; AUTHORITY SECTION:
google.com. 3600 IN NS dns1.superdns.com.br.
google.com. 3600 IN NS dns2.superdns.com.br.
;; Query time: 4 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jul 6 12:20:58 2010
;; MSG SIZE rcvd: 97
Pelo que eu notei não consta erro.
Qual arquivo que tem que ser colocado no /etc/resolv.conf para conseguir utilizar normalmente?
-
Re: problemas com bind
em /etc/resolv.conf
search seu.dominio
nameserver 127.0.0.1
-
Re: problemas com bind
Editei o /etc/resolv.conf e coloquei dessa forma.
Permanece dando o erro.
Error Downloading Packages:
php-mbstring-5.1.6-27.el5.x86_64: failure: CentOS/php-mbstring-5.1.6-27.el5.x86_64.rpm from base: [Errno 256] No more mirrors to try.
squirrelmail-1.4.8-5.el5.centos.10.noarch: failure: CentOS/squirrelmail-1.4.8-5.el5.centos.10.noarch.rpm from base: [Errno 256] No more mirrors to try.
gmp-4.1.4-10.el5.x86_64: failure: CentOS/gmp-4.1.4-10.el5.x86_64.rpm from base: [Errno 256] No more mirrors to try.
tmpwatch-2.9.7-1.1.el5.2.x86_64: failure: CentOS/tmpwatch-2.9.7-1.1.el5.2.x86_64.rpm from base: [Errno 256] No more mirrors to try.
php-5.1.6-27.el5.x86_64: failure: CentOS/php-5.1.6-27.el5.x86_64.rpm from base: [Errno 256] No more mirrors to try.
php-common-5.1.6-27.el5.x86_64: failure: CentOS/php-common-5.1.6-27.el5.x86_64.rpm from base: [Errno 256] No more mirrors to try.
php-cli-5.1.6-27.el5.x86_64: failure: CentOS/php-cli-5.1.6-27.el5.x86_64.rpm from base: [Errno 256] No more mirrors to try.