klassev,
благодарю за ответ!
ps aux | grep named
named 1942 0.0 0.4 38952 3480 ? Ssl 11:37 0:00 /usr/sbin/named -u named
root 15424 0.0 0.0 3080 712 pts/0 S+ 11:59 0:00 grep named
manman,
iptables -nvL
Chain INPUT (policy ACCEPT 790K packets, 757M bytes)
pkts bytes target prot opt in out source destination
39 6192 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0
790K 757M ISPMGR all -- * * 0.0.0.0/0 0.0.0.0/0
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
Chain OUTPUT (policy ACCEPT 571K packets, 164M bytes)
571K 164M ISPMGR all -- * * 0.0.0.0/0 0.0.0.0/0
Chain ISPMGR (2 references)
Может что-то не то в
/etc/resolv.conf
Ничего не менял, что с впс пришло, то и оставил, кроме того, что добавил выше nameserver 127.0.0.1
BasePelleta добавил 28-11-2010 в 19:49
А где перекрыто?
dig @174.200.164.158 mydomain.com
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> @174.200.164.158 mydomain.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55741
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;mydomain.com. IN A
;; ANSWER SECTION:
mydomain.com. 3600 IN A 174.200.164.158
;; AUTHORITY SECTION:
mydomain.com. 3600 IN NS ns2.mydomain.com.
mydomain.com. 3600 IN NS ns1.mydomain.com.
;; ADDITIONAL SECTION:
ns1.mydomain.com. 3600 IN A 174.200.164.158
ns2.mydomain.com. 3600 IN A 174.200.164.160
;; Query time: 0 msec
;; SERVER: 174.200.164.158#53(174.200.164.158)
;; WHEN: Sun Nov 28 11:44:35 2010
;; MSG SIZE rcvd: 118
174.200.164.158 - настроящий!
dig 174.200.164.158
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> 174.200.164.158
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 42824
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;174.200.164.158. IN A
. 10800 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2010112800 1800 900 604800 86400
;; Query time: 231 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Nov 28 11:43:08 2010
;; MSG SIZE rcvd: 108
netstat -na |grep LISTEN|grep 53
tcp 0 0 174.200.164.160:53 0.0.0.0:* LISTEN
tcp 0 0 174.200.164.158:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN
tcp 0 0 ::1:953 :::* LISTEN
unix 2 [ ACC ] STREAM LISTENING 262282531 tmp/ispmgr.adm.sock
BasePelleta добавил 28-11-2010 в 19:35
iptables -I INPUT -p udp -j ACCEPT
Пустую строку вернуло!
BasePelleta добавил 28-11-2010 в 19:38
Сделал!
dig @127.0.0.1 mydomain.com
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> @127.0.0.1 mydomain.com
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11979
;; WHEN: Sun Nov 28 11:37:26 2010
telnet 174.200.164.158 53
Trying 174.200.164.158...
Connected to 174.200.164.158.
Escape character is '^]'.
Благодарю за ответ!
Вот мои /var/log/messages
Nov 28 09:59:32 pellets-wood named[17891]: running Nov 28 09:59:32 pellets-wood named[17891]: zone mydomain.com/IN: sending notifies (serial 2010112700) Nov 28 09:59:32 pellets-wood named[17891]: zone mydomain2.com/IN: sending notifies (serial 2010112702) Nov 28 09:59:32 pellets-wood named[17891]: zone mydomain3.com/IN: sending notifies (serial 2010112800) Nov 28 09:59:32 pellets-wood named[17891]: zone mydomain4.com/IN: sending notifies (serial 2010112800) Nov 28 09:59:33 pellets-wood named[17891]: client 174.200.164.160#31536: received notify for zone 'mydomain.com' Nov 28 09:59:33 pellets-wood named[17891]: client 174.200.164.160#30221: received notify for zone 'mydomain2.com' Nov 28 09:59:33 pellets-wood named[17891]: client 174.200.164.160#30221: received notify for zone 'mydomain3.com' Nov 28 09:59:33 pellets-wood named[17891]: client 174.200.164.160#30221: received notify for zone 'mydomain4.com' Nov 28 10:01:01 pellets-wood rotated[23716]: Rotation finished. 0 log files was processed. 0 seconds left Nov 28 10:51:40 pellets-wood named[17891]: shutting down: flushing changes Nov 28 10:51:40 pellets-wood named[17891]: stopping command channel on 127.0.0.1#953 Nov 28 10:51:40 pellets-wood named[17891]: stopping command channel on ::1#953 Nov 28 10:51:40 pellets-wood named[17891]: no longer listening on 127.0.0.1#53 Nov 28 10:51:40 pellets-wood named[17891]: no longer listening on 174.200.164.158#53 Nov 28 10:51:40 pellets-wood named[17891]: no longer listening on 174.200.164.160#53 Nov 28 10:51:40 pellets-wood named[17891]: exiting Nov 28 10:51:42 pellets-wood named[6125]: starting BIND 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 -u named Nov 28 10:51:42 pellets-wood named[6125]: adjusted limit on open files from 1024 to 1048576 Nov 28 10:51:42 pellets-wood named[6125]: found 1 CPU, using 1 worker thread Nov 28 10:51:42 pellets-wood named[6125]: using up to 4096 sockets Nov 28 10:51:42 pellets-wood named[6125]: loading configuration from '/etc/named.conf' Nov 28 10:51:42 pellets-wood named[6125]: using default UDP/IPv4 port range: [1024, 65535] Nov 28 10:51:42 pellets-wood named[6125]: using default UDP/IPv6 port range: [1024, 65535] Nov 28 10:51:42 pellets-wood named[6125]: listening on IPv4 interface lo, 127.0.0.1#53 Nov 28 10:51:42 pellets-wood named[6125]: listening on IPv4 interface venet0:0, 174.200.164.158#53 Nov 28 10:51:42 pellets-wood named[6125]: listening on IPv4 interface venet0:1, 174.200.164.160#53 Nov 28 10:51:42 pellets-wood named[6125]: command channel listening on 127.0.0.1#953 Nov 28 10:51:42 pellets-wood named[6125]: command channel listening on ::1#953 Nov 28 10:51:42 pellets-wood named[6125]: the working directory is not writable Nov 28 10:51:42 pellets-wood named[6125]: zone mydomain.com/IN: loaded serial 2010112700 Nov 28 10:51:42 pellets-wood named[6125]: zone mydomain2.com/IN: loaded serial 2010112702 Nov 28 10:51:42 pellets-wood named[6125]: zone mydomain3.com/IN: loaded serial 2010112800 Nov 28 10:51:42 pellets-wood named[6125]: zone mydomain4.com/IN: loaded serial 2010112800 Nov 28 10:51:42 pellets-wood named[6125]: running Nov 28 10:51:42 pellets-wood named[6125]: zone mydomain.com/IN: sending notifies (serial 2010112700) Nov 28 10:51:42 pellets-wood named[6125]: zone mydomain2.com/IN: sending notifies (serial 2010112702) Nov 28 10:51:42 pellets-wood named[6125]: zone mydomain3.com/IN: sending notifies (serial 2010112800) Nov 28 10:51:42 pellets-wood named[6125]: zone mydomain4.com/IN: sending notifies (serial 2010112800) Nov 28 10:51:42 pellets-wood named[6125]: client 174.200.164.160#2330: received notify for zone 'mydomain.com' Nov 28 10:51:43 pellets-wood named[6125]: client 174.200.164.160#20235: received notify for zone 'mydomain2.com' Nov 28 10:51:43 pellets-wood named[6125]: client 174.200.164.160#20235: received notify for zone 'mydomain3.com' Nov 28 10:51:43 pellets-wood named[6125]: client 174.200.164.160#20235: received notify for zone 'mydomain4.com'
BasePelleta добавил 28-11-2010 в 18:56
dig @ns1.mydomain.com mydomain.com axfr
(ничего не вывело)
BasePelleta добавил 28-11-2010 в 18:59
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> @ns1.mydomain.com mydomain.com axfr ; (1 server found) ;; global options: printcmd ;; connection timed out; no servers could be reached [root@pellets-wood data]# dig @174.200.164.158 mydomain.com -t soa ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> @174.200.164.158 mydomain.com -t soa ; (1 server found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49979 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUESTION SECTION: ;mydomain.com. IN SOA ;; ANSWER SECTION: mydomain.com. 3600 IN SOA ns1.mydomain.com. root.mydomain.com. 2010112700 10800 3600 604800 86400 ;; AUTHORITY SECTION: mydomain.com. 3600 IN NS ns1.mydomain.com. mydomain.com. 3600 IN NS ns2.mydomain.com. ;; ADDITIONAL SECTION: ns1.mydomain.com. 3600 IN A 174.200.164.158 ns2.mydomain.com. 3600 IN A 174.200.164.160 ;; Query time: 10 msec ;; SERVER: 174.200.164.158#53(174.200.164.158) ;; WHEN: Sun Nov 28 10:57:44 2010 ;; MSG SIZE rcvd: 143
BasePelleta добавил 28-11-2010 в 19:03
dig @ns1.mydomain.com mydomain.com (ничего не вывело)
Проблема: на данный момент домен mydomain.com недоступен!
BasePelleta добавил 28-11-2010 в 19:07
Прошло 2 суток!
Стоит задуматься, все ли правильно сделал?
inseonight, тогда возникает проблема синхронизации!
А если пользователь возжелает удалить файл, а он уже на другом сервере?
BasePelleta добавил 27-11-2010 в 10:53
Не нравится! Нужно решение проще!
Есть еще вариант - подгрузка формы аплоуда целевого ВПС через айфрейм в этом плане проблема будет решена.
Попутные вопросы: аутентификация в подгружаемой форме аплоуда
