مشکل در راه اندازی cPanel و DNS

نمایش نسخه قابل چاپ

September 13th, 2011, 08:38
AhmadTux

مشکل در راه اندازی cPanel و DNS

سلام دوستان
من یه vps دارم که روش freebsd 8.2 نصب کردم و تنها کاری که انجام دادم اینه که update کردم و cPanel نصبیدم.

سوال 1 ) من میخوام Hostname رو که به صورت FQDN خواسته ، vps1.weblar.net ست کنم
حالا وقتی که با IP میخوام پنل سرور رو ببینم میزنم :

کد:

http://96.127.133.53:2087/

که میره رو :

کد:

https://vps1.weblar.net:2087/

و من چیزی نمیبینم !

فایل DNS من :

کد:

cat /etc/resolv.conf domain weblar.net nameserver 4.2.2.4

وضعیت weblar.net :

کد:

http://www.intodns.com/weblar.net

ممنون میشم که کمک کنید :x
September 13th, 2011, 14:27
Neo2

پاسخ : مشکل در راه اندازی cPanel و DNS

نقل قول:

نوشته اصلی توسط AhmadTux

سلام دوستان
من یه vps دارم که روش freebsd 8.2 نصب کردم و تنها کاری که انجام دادم اینه که update کردم و cPanel نصبیدم.

سوال 1 ) من میخوام Hostname رو که به صورت FQDN خواسته ، vps1.weblar.net ست کنم
حالا وقتی که با IP میخوام پنل سرور رو ببینم میزنم :

کد:

http://96.127.133.53:2087/

که میره رو :

کد:

https://vps1.weblar.net:2087/

و من چیزی نمیبینم !

فایل DNS من :

کد:

cat /etc/resolv.conf domain weblar.net nameserver 4.2.2.4

وضعیت weblar.net :

کد:

http://www.intodns.com/weblar.net

ممنون میشم که کمک کنید :x

تنظیمات مربوط به DNS و Nameserver های دامین و سی پنل رو با هم چک کنید
SSL دارید رو سرور ؟ اگه ندارید پورتی که اینجا هست رو هم عوض کنید.
September 13th, 2011, 14:34
AhmadTux

پاسخ : مشکل در راه اندازی cPanel و DNS

سلام
ممنون
چند دقیقه قبل شما فهمیدم

ممنونم
پورت باید 2086 باشه
September 14th, 2011, 15:43
AhmadTux

پاسخ : مشکل در راه اندازی cPanel و DNS

بازهم کار نمیکنه !
نصب کردم و ns1.weblar تا ns4 رو ست کردم
روی دامین ها هم همینطور

الان cpanel برای یوزر کار میکنه
اما هیچ کدوم از دامنه ها کار نمیکنن !!!

نمیدونم کجاش مورد داره!
یکی کمکی کنه
http://www.intodns.com/ahmadtux.com

---------- Post added at 03:43 PM ---------- Previous post was at 03:23 PM ----------

ip ها رو چرا نشون نمیده اینجا ؟
Ahmadtux.com DNS Lookup | Nameserver Lookup - Who.is - Who.is
September 14th, 2011, 18:55
iMohsen

پاسخ : مشکل در راه اندازی cPanel و DNS

خب این میگه سرور شما به درخواست جواب نمیده .
یا فایروال دارید که پورت 53 رو بلاک کرده و یا اصلا سرویس dns استارت نیست
September 14th, 2011, 22:21
AhmadTux

پاسخ : مشکل در راه اندازی cPanel و DNS

هنوز فایروال نصب نکردم

وقتی هم که میزنم
service named start
مینویسه :
named already running? pid=750

پورتهاش رو هم که اسکن میکنم همه هستن الا 53

کد:

Discovered open port 22/tcp on 96.127.133.44 Discovered open port 110/tcp on 96.127.133.44 Discovered open port 25/tcp on 96.127.133.44 Discovered open port 3306/tcp on 96.127.133.44 Discovered open port 80/tcp on 96.127.133.44 Discovered open port 993/tcp on 96.127.133.44 Discovered open port 143/tcp on 96.127.133.44 Discovered open port 995/tcp on 96.127.133.44 Discovered open port 21/tcp on 96.127.133.44 Discovered open port 443/tcp on 96.127.133.44
September 14th, 2011, 22:31
AhmadTux

1 فایل پیوست

پاسخ : مشکل در راه اندازی cPanel و DNS

اینم یه جا دیدم
چیه ؟
فایل پیوست 3264
September 15th, 2011, 13:17
AhmadTux

پاسخ : مشکل در راه اندازی cPanel و DNS

یکی نیست کمک کنه ؟؟؟!!!!
September 15th, 2011, 14:14
iMohsen

پاسخ : مشکل در راه اندازی cPanel و DNS

نقل قول:

نوشته اصلی توسط AhmadTux

اینم یه جا دیدم
چیه ؟
فایل پیوست 3264

خب همینه دیگه .
داره میگه named اجازه نداره رو پورت 53 سرویس دهی کنه .
September 15th, 2011, 14:19
AhmadTux

پاسخ : مشکل در راه اندازی cPanel و DNS

خوب محسن جان من که فایروال ندارم
چیکار کنم ؟
September 15th, 2011, 14:21
iMohsen

پاسخ : مشکل در راه اندازی cPanel و DNS

البته این روی اینترفیس lo1 میخواد سرویس بده .
این اینترفیس روش ip هست ؟

خروجی ifconfig رو بده .
September 15th, 2011, 14:52
Milad-H

پاسخ : مشکل در راه اندازی cPanel و DNS

با سلام دامنه را بدید تا چک کنم
قبلاش ابتدا Cpanel رو با Force a reinstall even if the system is up to date اپدیت کنید.
Main >> cPanel >> Upgrade to Latest Version
اگر نشد آپاچی رو از EasyApache رو بویلد کنید حتما مشکل حل خواهد شد.

Main >> Software >> EasyApache (Apache Update
باز هم اگه نشد my sql را ریستارت کنید و سریع یک بار DNS مربوط به دامنه اصلی را باز و سیو کنید.
همچنین اطلاعت داخل my.cnf را کاملا خالی کنید.
September 16th, 2011, 11:06
AhmadTux

پاسخ : مشکل در راه اندازی cPanel و DNS

نقل قول:

نوشته اصلی توسط iMohsen

البته این روی اینترفیس lo1 میخواد سرویس بده .
این اینترفیس روش ip هست ؟

خروجی ifconfig رو بده .

کد:

em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM> ether 00:50:56:b4:00:aa inet 96.127.133.44 netmask 0xffffffe0 broadcast 96.127.133.63 media: Ethernet autoselect (1000baseT <full-duplex>) status: active plip0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> metric 0 mtu 1500 lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=3<RXCSUM,TXCSUM> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 nd6 options=3<PERFORMNUD,ACCEPT_RTADV>

---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------

نقل قول:

نوشته اصلی توسط Milad-H

با سلام دامنه را بدید تا چک کنم
قبلاش ابتدا Cpanel رو با Force a reinstall even if the system is up to date اپدیت کنید.
Main >> cPanel >> Upgrade to Latest Version
اگر نشد آپاچی رو از EasyApache رو بویلد کنید حتما مشکل حل خواهد شد.

Main >> Software >> EasyApache (Apache Update
باز هم اگه نشد my sql را ریستارت کنید و سریع یک بار DNS مربوط به دامنه اصلی را باز و سیو کنید.
همچنین اطلاعت داخل my.cnf را کاملا خالی کنید.

نشد !

---------- Post added at 10:12 AM ---------- Previous post was at 10:10 AM ----------

این gmail همه میل های cpanel رو اسپم کرده بود
اینو تازه دیدم :

کد:

IMPORTANT: Do not ignore this email. Your hostname (vps1.weblar.net) could not be resolved to an IP address. This means that /etc/hosts is not set up correctly, and/or there is no dns entry for vps1.weblar.net. Please be sure that the contents of /etc/hosts are configured correctly, and also that there is a correct 'A' entry for the domain in the zone file. Some or all of these problems can be caused by /etc/resolv.conf being setup incorrectly. Please check that file if you believe everything else is correct. You may be able to automatically correct this problem by using the 'Add an A entry for your hostname' option under 'Dns Functions' in your Web Host Manager.

---------- Post added at 10:16 AM ---------- Previous post was at 10:12 AM ----------

محتویات /etc/hosts

کد:

::1 localhost localhost.weblar.net 127.0.0.1 localhost localhost.weblar.net 96.127.133.44 vps1.weblar.net vps1 vps1.weblar.net.

---------- Post added at 11:06 AM ---------- Previous post was at 10:16 AM ----------

اینم قسمتی از log

کد:

Sep 14 12:22:20 vps1 kernel: da0: 10240MB (20971520 512 byte sectors: 255H 63S/T 1305C) Sep 14 12:22:20 vps1 kernel: Trying to mount root from ufs:/dev/da0s1a Sep 14 12:22:21 vps1 named[750]: starting BIND 9.6.-ESV-R3 -u bind -c /etc/namedb/named.conf -t /var/named -u bind Sep 14 12:22:21 vps1 named[750]: built with '--prefix=/usr' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--enable-threads' '--enable-getifaddrs' '--disable-linux-caps' '--with-openssl=/usr' '--with-randomdev=/dev/random' '--without-idn' '--without-libxml2' Sep 14 12:22:21 vps1 named[750]: command channel listening on 127.0.0.1#953 Sep 14 12:22:21 vps1 named[750]: running Sep 14 12:22:21 vps1 named[835]: starting BIND 9.6.-ESV-R3 -u bind -c /etc/namedb/named.conf -t /var/named -u bind Sep 14 12:22:21 vps1 named[835]: built with '--prefix=/usr' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--enable-threads' '--enable-getifaddrs' '--disable-linux-caps' '--with-openssl=/usr' '--with-randomdev=/dev/random' '--without-idn' '--without-libxml2' Sep 14 12:22:21 vps1 named[835]: could not listen on UDP socket: address in use Sep 14 12:22:21 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 14 12:22:21 vps1 named[835]: not listening on any interfaces Sep 14 12:22:21 vps1 named[835]: /etc/namedb/named.conf:4: couldn't add command channel 127.0.0.1#953: address in use Sep 14 12:22:21 vps1 named[835]: could not listen on UDP socket: permission denied Sep 14 12:22:21 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 14 12:22:21 vps1 named[835]: running Sep 14 12:22:25 vps1 PAM-hulk[1130]: failed to connect stream socket Sep 14 12:22:27 vps1 named[1277]: starting BIND 9.6.-ESV-R3 -u bind -c /etc/named.conf Sep 14 12:22:27 vps1 named[1277]: built with '--prefix=/usr' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--enable-threads' '--enable-getifaddrs' '--disable-linux-caps' '--with-openssl=/usr' '--with-randomdev=/dev/random' '--without-idn' '--without-libxml2' Sep 14 12:22:27 vps1 named[1277]: none:0: open: /etc/named.conf: file not found Sep 14 12:22:27 vps1 named[1277]: loading configuration: file not found Sep 14 12:22:27 vps1 named[1277]: exiting (due to fatal error) Sep 14 12:23:51 vps1 pure-ftpd: (?@?) [WARNING] Unknown run-time option Sep 14 13:22:24 vps1 named[835]: could not listen on UDP socket: permission denied Sep 14 13:22:24 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 14 13:22:24 vps1 named[835]: not listening on any interfaces Sep 14 14:22:26 vps1 named[835]: could not listen on UDP socket: permission denied Sep 14 14:22:26 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 14 14:22:26 vps1 named[835]: not listening on any interfaces Sep 14 14:33:52 vps1 login: ROOT LOGIN (root) ON ttyv0 Sep 14 15:22:28 vps1 named[835]: could not listen on UDP socket: permission denied Sep 14 15:22:28 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 14 15:22:28 vps1 named[835]: not listening on any interfaces Sep 14 16:22:31 vps1 named[835]: could not listen on UDP socket: permission denied Sep 14 16:22:31 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 14 16:22:31 vps1 named[835]: not listening on any interfaces Sep 14 17:22:33 vps1 named[835]: could not listen on UDP socket: permission denied Sep 14 17:22:33 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 14 17:22:33 vps1 named[835]: not listening on any interfaces Sep 14 18:22:36 vps1 named[835]: could not listen on UDP socket: permission denied Sep 14 18:22:36 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 14 18:22:36 vps1 named[835]: not listening on any interfaces Sep 14 19:22:38 vps1 named[835]: could not listen on UDP socket: permission denied Sep 14 19:22:38 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 14 19:22:38 vps1 named[835]: not listening on any interfaces Sep 14 20:22:40 vps1 named[835]: could not listen on UDP socket: permission denied Sep 14 20:22:40 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 14 20:22:40 vps1 named[835]: not listening on any interfaces Sep 14 21:22:43 vps1 named[835]: could not listen on UDP socket: permission denied Sep 14 21:22:43 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 14 21:22:43 vps1 named[835]: not listening on any interfaces Sep 14 21:48:53 vps1 pure-ftpd[51338]: (?@91.99.167.108) [WARNING] Authentication failed for user [sa] Sep 14 21:49:00 vps1 pure-ftpd[51357]: (?@91.99.167.108) [WARNING] Authentication failed for user [sa] Sep 14 21:49:07 vps1 pure-ftpd[51376]: (?@91.99.167.108) [WARNING] Authentication failed for user [sa] Sep 14 21:49:14 vps1 pure-ftpd[51388]: (?@91.99.167.108) [WARNING] Authentication failed for user [sa] Sep 14 21:49:28 vps1 pure-ftpd[51403]: (?@91.99.167.108) [WARNING] Authentication failed for user [sa] Sep 14 21:49:39 vps1 pure-ftpd[51417]: (?@91.99.167.108) [WARNING] Authentication failed for user [sa] Sep 14 21:49:49 vps1 pure-ftpd[51433]: (?@91.99.167.108) [WARNING] Authentication failed for user [sa] Sep 14 21:50:02 vps1 pure-ftpd[51445]: (?@91.99.167.108) [WARNING] Authentication failed for user [sa] Sep 14 21:50:13 vps1 pure-ftpd[51488]: (?@91.99.167.108) [WARNING] Authentication failed for user [sa] Sep 14 21:50:30 vps1 pure-ftpd[51511]: (?@91.99.167.108) [WARNING] Authentication failed for user [sa] Sep 14 21:50:40 vps1 pure-ftpd[51522]: (?@91.99.167.108) [WARNING] Authentication failed for user [sa] Sep 14 21:50:49 vps1 pure-ftpd[51530]: (?@91.99.167.108) [WARNING] Authentication failed for user [sa] Sep 14 21:51:03 vps1 pure-ftpd[51544]: (?@91.99.167.108) [WARNING] Authentication failed for user [sa] Sep 14 21:51:14 vps1 pure-ftpd[51553]: (?@91.99.167.108) [WARNING] Authentication failed for user [sa] Sep 14 21:51:24 vps1 pure-ftpd[51564]: (?@91.99.167.108) [WARNING] Authentication failed for user [sa] Sep 14 21:51:33 vps1 pure-ftpd[51572]: (?@91.99.167.108) [WARNING] Authentication failed for user [root] Sep 14 21:51:40 vps1 pure-ftpd[51586]: (?@91.99.167.108) [WARNING] Authentication failed for user [root] Sep 14 21:51:46 vps1 pure-ftpd[51597]: (?@91.99.167.108) [WARNING] Authentication failed for user [root] Sep 14 21:51:58 vps1 pure-ftpd[51611]: (?@91.99.167.108) [WARNING] Authentication failed for user [root] Sep 14 21:52:05 vps1 pure-ftpd[51622]: (?@91.99.167.108) [WARNING] Authentication failed for user [root] Sep 14 21:52:13 vps1 pure-ftpd[51635]: (?@91.99.167.108) [WARNING] Authentication failed for user [root] Sep 14 21:52:20 vps1 pure-ftpd[51646]: (?@91.99.167.108) [WARNING] Authentication failed for user [root] Sep 14 21:52:27 vps1 pure-ftpd[51657]: (?@91.99.167.108) [WARNING] Authentication failed for user [root] Sep 14 21:52:35 vps1 pure-ftpd[51671]: (?@91.99.167.108) [WARNING] Authentication failed for user [root] Sep 14 21:52:43 vps1 pure-ftpd[51682]: (?@91.99.167.108) [WARNING] Authentication failed for user [root] Sep 14 21:52:54 vps1 pure-ftpd[51693]: (?@91.99.167.108) [WARNING] Authentication failed for user [root] Sep 14 21:53:01 vps1 pure-ftpd[51707]: (?@91.99.167.108) [WARNING] Authentication failed for user [root] Sep 14 21:53:10 vps1 pure-ftpd[51718]: (?@91.99.167.108) [WARNING] Authentication failed for user [root] Sep 14 21:53:16 vps1 pure-ftpd[51729]: (?@91.99.167.108) [WARNING] Authentication failed for user [root] Sep 14 21:53:30 vps1 pure-ftpd[51740]: (?@91.99.167.108) [WARNING] Authentication failed for user [root] Sep 14 21:53:39 vps1 pure-ftpd[51751]: (?@91.99.167.108) [WARNING] Authentication failed for user [root] Sep 14 21:53:48 vps1 pure-ftpd[51765]: (?@91.99.167.108) [WARNING] Authentication failed for user [tmp] Sep 14 21:53:56 vps1 pure-ftpd[51777]: (?@91.99.167.108) [WARNING] Authentication failed for user [tmp] Sep 14 21:54:09 vps1 pure-ftpd[51785]: (?@91.99.167.108) [WARNING] Authentication failed for user [tmp] Sep 14 21:54:17 vps1 pure-ftpd[51796]: (?@91.99.167.108) [WARNING] Authentication failed for user [tmp] Sep 14 21:54:31 vps1 pure-ftpd[51807]: (?@91.99.167.108) [WARNING] Authentication failed for user [tmp] Sep 14 21:54:38 vps1 pure-ftpd[51815]: (?@91.99.167.108) [WARNING] Authentication failed for user [tmp] Sep 14 21:54:50 vps1 pure-ftpd[51826]: (?@91.99.167.108) [WARNING] Authentication failed for user [tmp] Sep 14 21:54:59 vps1 pure-ftpd[51837]: (?@91.99.167.108) [WARNING] Authentication failed for user [tmp] Sep 14 21:55:08 vps1 pure-ftpd[51889]: (?@91.99.167.108) [WARNING] Authentication failed for user [tmp] Sep 14 21:55:15 vps1 pure-ftpd[51903]: (?@91.99.167.108) [WARNING] Authentication failed for user [tmp] Sep 14 21:55:23 vps1 pure-ftpd[51914]: (?@91.99.167.108) [WARNING] Authentication failed for user [tmp] Sep 14 21:55:31 vps1 pure-ftpd[51925]: (?@91.99.167.108) [WARNING] Authentication failed for user [tmp] Sep 14 21:55:39 vps1 pure-ftpd[51936]: (?@91.99.167.108) [WARNING] Authentication failed for user [tmp] Sep 14 21:55:50 vps1 pure-ftpd[51947]: (?@91.99.167.108) [WARNING] Authentication failed for user [tmp] Sep 14 21:56:02 vps1 pure-ftpd[51958]: (?@91.99.167.108) [WARNING] Authentication failed for user [tmp] Sep 14 21:56:09 vps1 pure-ftpd[51972]: (?@91.99.167.108) [WARNING] Authentication failed for user [tmp] Sep 14 21:56:17 vps1 pure-ftpd[51983]: (?@91.99.167.108) [WARNING] Authentication failed for user [temp] Sep 14 21:56:23 vps1 pure-ftpd[51997]: (?@91.99.167.108) [WARNING] Authentication failed for user [temp] Sep 14 21:56:30 vps1 pure-ftpd[52008]: (?@91.99.167.108) [WARNING] Authentication failed for user [temp] Sep 14 21:56:36 vps1 pure-ftpd[52016]: (?@91.99.167.108) [WARNING] Authentication failed for user [temp] Sep 14 21:56:43 vps1 pure-ftpd[52027]: (?@91.99.167.108) [WARNING] Authentication failed for user [temp] Sep 14 21:56:49 vps1 pure-ftpd[52038]: (?@91.99.167.108) [WARNING] Authentication failed for user [temp] Sep 14 21:56:56 vps1 pure-ftpd[52050]: (?@91.99.167.108) [WARNING] Authentication failed for user [temp] Sep 14 21:57:04 vps1 pure-ftpd[52063]: (?@91.99.167.108) [WARNING] Authentication failed for user [temp] Sep 14 21:57:12 vps1 pure-ftpd[52077]: (?@91.99.167.108) [WARNING] Authentication failed for user [temp] Sep 14 21:57:23 vps1 pure-ftpd[52091]: (?@91.99.167.108) [WARNING] Authentication failed for user [temp] Sep 14 21:57:29 vps1 pure-ftpd[52105]: (?@91.99.167.108) [WARNING] Authentication failed for user [temp] Sep 14 21:57:44 vps1 pure-ftpd[52116]: (?@91.99.167.108) [WARNING] Authentication failed for user [temp] Sep 14 21:57:51 vps1 pure-ftpd[52124]: (?@91.99.167.108) [WARNING] Authentication failed for user [temp] Sep 14 21:58:01 vps1 pure-ftpd[52135]: (?@91.99.167.108) [WARNING] Authentication failed for user [temp] Sep 14 21:58:14 vps1 pure-ftpd[52152]: (?@91.99.167.108) [WARNING] Authentication failed for user [temp] Sep 14 21:58:22 vps1 pure-ftpd[52165]: (?@91.99.167.108) [WARNING] Authentication failed for user [temp] Sep 14 21:58:29 vps1 pure-ftpd[52174]: (?@91.99.167.108) [WARNING] Authentication failed for user [test] Sep 14 21:58:38 vps1 pure-ftpd[52188]: (?@91.99.167.108) [WARNING] Authentication failed for user [test] Sep 14 21:58:46 vps1 pure-ftpd[52199]: (?@91.99.167.108) [WARNING] Authentication failed for user [test] Sep 14 21:58:59 vps1 pure-ftpd[52210]: (?@91.99.167.108) [WARNING] Authentication failed for user [test] Sep 14 21:59:08 vps1 pure-ftpd[52221]: (?@91.99.167.108) [WARNING] Authentication failed for user [test] Sep 14 21:59:18 vps1 pure-ftpd[52226]: (?@91.99.167.108) [WARNING] Authentication failed for user [test] Sep 14 21:59:25 vps1 pure-ftpd[52231]: (?@91.99.167.108) [WARNING] Authentication failed for user [test] Sep 14 21:59:31 vps1 pure-ftpd[52236]: (?@91.99.167.108) [WARNING] Authentication failed for user [test] Sep 14 21:59:39 vps1 pure-ftpd[52241]: (?@91.99.167.108) [WARNING] Authentication failed for user [test] Sep 14 21:59:47 vps1 pure-ftpd[52246]: (?@91.99.167.108) [WARNING] Authentication failed for user [test] Sep 14 21:59:53 vps1 pure-ftpd[52251]: (?@91.99.167.108) [WARNING] Authentication failed for user [test] Sep 14 22:00:01 vps1 pure-ftpd[52257]: (?@91.99.167.108) [WARNING] Authentication failed for user [test] Sep 14 22:00:07 vps1 pure-ftpd[52305]: (?@91.99.167.108) [WARNING] Authentication failed for user [test] Sep 14 22:00:14 vps1 pure-ftpd[52310]: (?@91.99.167.108) [WARNING] Authentication failed for user [test] Sep 14 22:00:19 vps1 login: ROOT LOGIN (root) ON ttyv0 Sep 14 22:00:22 vps1 pure-ftpd[52317]: (?@91.99.167.108) [WARNING] Authentication failed for user [test] Sep 14 22:00:30 vps1 pure-ftpd[52328]: (?@91.99.167.108) [WARNING] Authentication failed for user [test] Sep 14 22:00:36 vps1 pure-ftpd[52333]: (?@91.99.167.108) [WARNING] Authentication failed for user [tst] Sep 14 22:00:43 vps1 pure-ftpd[52338]: (?@91.99.167.108) [WARNING] Authentication failed for user [tst] Sep 14 22:00:49 vps1 pure-ftpd[52343]: (?@91.99.167.108) [WARNING] Authentication failed for user [tst] Sep 14 22:00:57 vps1 pure-ftpd[52348]: (?@91.99.167.108) [WARNING] Authentication failed for user [tst] Sep 14 22:01:03 vps1 pure-ftpd[52355]: (?@91.99.167.108) [WARNING] Authentication failed for user [tst] Sep 14 22:01:06 vps1 root: /usr/sbin/service: WARNING: $pureftpd_enable is not set properly - see rc.conf(5). Sep 14 22:01:06 vps1 root: /usr/sbin/service: WARNING: $stunnel_enable is not set properly - see rc.conf(5). Sep 14 22:01:06 vps1 root: /usr/sbin/service: WARNING: $rsyncd_enable is not set properly - see rc.conf(5). Sep 14 22:01:06 vps1 root: /usr/sbin/service: WARNING: $exim_enable is not set properly - see rc.conf(5). Sep 14 22:01:10 vps1 pure-ftpd[52360]: (?@91.99.167.108) [WARNING] Authentication failed for user [tst] Sep 14 22:01:16 vps1 pure-ftpd[52814]: (?@91.99.167.108) [WARNING] Authentication failed for user [tst] Sep 14 22:01:28 vps1 pure-ftpd[52821]: (?@91.99.167.108) [WARNING] Authentication failed for user [tst] Sep 14 22:01:34 vps1 pure-ftpd[52826]: (?@91.99.167.108) [WARNING] Authentication failed for user [tst] Sep 14 22:01:42 vps1 pure-ftpd[52831]: (?@91.99.167.108) [WARNING] Authentication failed for user [tst] Sep 14 22:01:48 vps1 pure-ftpd[52836]: (?@91.99.167.108) [WARNING] Authentication failed for user [tst] Sep 14 22:01:56 vps1 pure-ftpd[52848]: (?@91.99.167.108) [WARNING] Authentication failed for user [tst] Sep 14 22:02:02 vps1 named[750]: stopping command channel on 127.0.0.1#953 Sep 14 22:02:02 vps1 named[750]: exiting Sep 14 22:02:02 vps1 named[52956]: starting BIND 9.6.-ESV-R3 -u bind -c /etc/namedb/named.conf -t /var/named -u bind Sep 14 22:02:02 vps1 named[52956]: built with '--prefix=/usr' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--enable-threads' '--enable-getifaddrs' '--disable-linux-caps' '--with-openssl=/usr' '--with-randomdev=/dev/random' '--without-idn' '--without-libxml2' Sep 14 22:02:02 vps1 named[52956]: command channel listening on 127.0.0.1#953 Sep 14 22:02:02 vps1 named[52956]: running Sep 14 22:02:03 vps1 pure-ftpd[52853]: (?@91.99.167.108) [WARNING] Authentication failed for user [tst] Sep 14 22:02:10 vps1 pure-ftpd[52958]: (?@91.99.167.108) [WARNING] Authentication failed for user [tst] Sep 14 22:02:16 vps1 pure-ftpd[52963]: (?@91.99.167.108) [WARNING] Authentication failed for user [tst] Sep 14 22:02:25 vps1 pure-ftpd[52968]: (?@91.99.167.108) [WARNING] Authentication failed for user [tst] Sep 14 22:02:33 vps1 pure-ftpd[52973]: (?@91.99.167.108) [WARNING] Authentication failed for user [admin] Sep 14 22:02:39 vps1 pure-ftpd[52978]: (?@91.99.167.108) [WARNING] Authentication failed for user [admin] Sep 14 22:02:45 vps1 pure-ftpd[52983]: (?@91.99.167.108) [WARNING] Authentication failed for user [admin] Sep 14 22:02:53 vps1 pure-ftpd[52988]: (?@91.99.167.108) [WARNING] Authentication failed for user [admin] Sep 14 22:03:02 vps1 pure-ftpd[52994]: (?@91.99.167.108) [WARNING] Authentication failed for user [admin] Sep 14 22:03:11 vps1 pure-ftpd[52999]: (?@91.99.167.108) [WARNING] Authentication failed for user [admin] Sep 14 22:03:17 vps1 pure-ftpd[53004]: (?@91.99.167.108) [WARNING] Authentication failed for user [admin] Sep 14 22:03:25 vps1 pure-ftpd[53009]: (?@91.99.167.108) [WARNING] Authentication failed for user [admin] Sep 14 22:03:33 vps1 pure-ftpd[53014]: (?@91.99.167.108) [WARNING] Authentication failed for user [admin] Sep 14 22:03:42 vps1 pure-ftpd[53019]: (?@91.99.167.108) [WARNING] Authentication failed for user [admin] Sep 14 22:03:49 vps1 pure-ftpd[53024]: (?@91.99.167.108) [WARNING] Authentication failed for user [admin] Sep 14 22:03:56 vps1 pure-ftpd[53029]: (?@91.99.167.108) [WARNING] Authentication failed for user [admin] Sep 14 22:04:05 vps1 pure-ftpd[53034]: (?@91.99.167.108) [WARNING] Authentication failed for user [admin] Sep 14 22:04:11 vps1 pure-ftpd[53039]: (?@91.99.167.108) [WARNING] Authentication failed for user [admin] Sep 14 22:04:18 vps1 pure-ftpd[53044]: (?@91.99.167.108) [WARNING] Authentication failed for user [admin] Sep 14 22:04:25 vps1 pure-ftpd[53049]: (?@91.99.167.108) [WARNING] Authentication failed for user [admin] Sep 14 22:04:32 vps1 pure-ftpd[53054]: (?@91.99.167.108) [WARNING] Authentication failed for user [newuser] Sep 14 22:04:39 vps1 pure-ftpd[53059]: (?@91.99.167.108) [WARNING] Authentication failed for user [newuser] Sep 14 22:04:45 vps1 pure-ftpd[53064]: (?@91.99.167.108) [WARNING] Authentication failed for user [newuser] Sep 14 22:04:52 vps1 pure-ftpd[53069]: (?@91.99.167.108) [WARNING] Authentication failed for user [newuser] Sep 14 22:04:59 vps1 pure-ftpd[53074]: (?@91.99.167.108) [WARNING] Authentication failed for user [newuser] Sep 14 22:05:05 vps1 pure-ftpd[53099]: (?@91.99.167.108) [WARNING] Authentication failed for user [newuser] Sep 14 22:05:13 vps1 pure-ftpd[53113]: (?@91.99.167.108) [WARNING] Authentication failed for user [newuser] Sep 14 22:05:19 vps1 pure-ftpd[53118]: (?@91.99.167.108) [WARNING] Authentication failed for user [newuser] Sep 14 22:05:27 vps1 pure-ftpd[53126]: (?@91.99.167.108) [WARNING] Authentication failed for user [newuser] Sep 14 22:05:35 vps1 pure-ftpd[53131]: (?@91.99.167.108) [WARNING] Authentication failed for user [newuser] Sep 14 22:05:43 vps1 pure-ftpd[53136]: (?@91.99.167.108) [WARNING] Authentication failed for user [newuser] Sep 14 22:05:49 vps1 pure-ftpd[53141]: (?@91.99.167.108) [WARNING] Authentication failed for user [newuser] Sep 14 22:05:55 vps1 pure-ftpd[53146]: (?@91.99.167.108) [WARNING] Authentication failed for user [newuser] Sep 14 22:06:04 vps1 pure-ftpd[53151]: (?@91.99.167.108) [WARNING] Authentication failed for user [newuser] Sep 14 22:06:13 vps1 pure-ftpd[53157]: (?@91.99.167.108) [WARNING] Authentication failed for user [newuser] Sep 14 22:06:21 vps1 pure-ftpd[53162]: (?@91.99.167.108) [WARNING] Authentication failed for user [newuser] Sep 14 22:06:29 vps1 pure-ftpd[53167]: (?@91.99.167.108) [WARNING] Authentication failed for user [nobody] Sep 14 22:06:35 vps1 pure-ftpd[53172]: (?@91.99.167.108) [WARNING] Authentication failed for user [nobody] Sep 14 22:06:41 vps1 pure-ftpd[53177]: (?@91.99.167.108) [WARNING] Authentication failed for user [nobody] Sep 14 22:06:49 vps1 pure-ftpd[53182]: (?@91.99.167.108) [WARNING] Authentication failed for user [nobody] Sep 14 22:06:55 vps1 pure-ftpd[53187]: (?@91.99.167.108) [WARNING] Authentication failed for user [nobody] Sep 14 22:07:02 vps1 pure-ftpd[53192]: (?@91.99.167.108) [WARNING] Authentication failed for user [nobody] Sep 14 22:07:10 vps1 pure-ftpd[53199]: (?@91.99.167.108) [WARNING] Authentication failed for user [nobody] Sep 14 22:07:17 vps1 pure-ftpd[53204]: (?@91.99.167.108) [WARNING] Authentication failed for user [nobody] Sep 14 22:07:23 vps1 pure-ftpd[53209]: (?@91.99.167.108) [WARNING] Authentication failed for user [nobody] Sep 14 22:07:30 vps1 pure-ftpd[53214]: (?@91.99.167.108) [WARNING] Authentication failed for user [nobody] Sep 14 22:07:38 vps1 pure-ftpd[53219]: (?@91.99.167.108) [WARNING] Authentication failed for user [nobody] Sep 14 22:07:46 vps1 pure-ftpd[53224]: (?@91.99.167.108) [WARNING] Authentication failed for user [nobody] Sep 14 22:07:54 vps1 pure-ftpd[53229]: (?@91.99.167.108) [WARNING] Authentication failed for user [nobody] Sep 14 22:08:00 vps1 pure-ftpd[53234]: (?@91.99.167.108) [WARNING] Authentication failed for user [nobody] Sep 14 22:08:05 vps1 pure-ftpd[53239]: (?@91.99.167.108) [WARNING] Authentication failed for user [nobody] Sep 14 22:08:12 vps1 pure-ftpd[53244]: (?@91.99.167.108) [WARNING] Authentication failed for user [nobody] Sep 14 22:22:45 vps1 named[835]: could not listen on UDP socket: permission denied Sep 14 22:22:45 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 14 22:22:45 vps1 named[835]: not listening on any interfaces Sep 14 23:22:48 vps1 named[835]: could not listen on UDP socket: permission denied Sep 14 23:22:48 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 14 23:22:48 vps1 named[835]: not listening on any interfaces Sep 14 23:49:43 vps1 login: 2 LOGIN FAILURES ON ttyv0 Sep 14 23:49:59 vps1 login: ROOT LOGIN (root) ON ttyv0 Sep 15 00:22:50 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 00:22:50 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 00:22:50 vps1 named[835]: not listening on any interfaces Sep 15 01:22:52 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 01:22:52 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 01:22:52 vps1 named[835]: not listening on any interfaces Sep 15 02:22:55 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 02:22:55 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 02:22:55 vps1 named[835]: not listening on any interfaces Sep 15 03:22:57 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 03:22:57 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 03:22:57 vps1 named[835]: not listening on any interfaces Sep 15 04:22:59 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 04:22:59 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 04:22:59 vps1 named[835]: not listening on any interfaces Sep 15 05:23:02 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 05:23:02 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 05:23:02 vps1 named[835]: not listening on any interfaces Sep 15 05:36:49 vps1 pure-ftpd: (?@?) [WARNING] Unknown run-time option Sep 15 06:23:04 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 06:23:04 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 06:23:04 vps1 named[835]: not listening on any interfaces Sep 15 07:23:06 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 07:23:06 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 07:23:06 vps1 named[835]: not listening on any interfaces Sep 15 08:23:09 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 08:23:09 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 08:23:09 vps1 named[835]: not listening on any interfaces Sep 15 09:23:11 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 09:23:11 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 09:23:11 vps1 named[835]: not listening on any interfaces Sep 15 10:23:13 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 10:23:13 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 10:23:13 vps1 named[835]: not listening on any interfaces Sep 15 11:23:16 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 11:23:16 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 11:23:16 vps1 named[835]: not listening on any interfaces Sep 15 12:23:18 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 12:23:18 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 12:23:18 vps1 named[835]: not listening on any interfaces Sep 15 13:23:20 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 13:23:20 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 13:23:20 vps1 named[835]: not listening on any interfaces Sep 15 14:23:23 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 14:23:23 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 14:23:23 vps1 named[835]: not listening on any interfaces Sep 15 15:23:25 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 15:23:25 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 15:23:25 vps1 named[835]: not listening on any interfaces Sep 15 16:23:27 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 16:23:27 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 16:23:27 vps1 named[835]: not listening on any interfaces Sep 15 17:23:29 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 17:23:29 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 17:23:29 vps1 named[835]: not listening on any interfaces Sep 15 18:23:32 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 18:23:32 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 18:23:32 vps1 named[835]: not listening on any interfaces Sep 15 19:23:34 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 19:23:34 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 19:23:34 vps1 named[835]: not listening on any interfaces Sep 15 20:23:36 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 20:23:36 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 20:23:36 vps1 named[835]: not listening on any interfaces Sep 15 21:23:38 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 21:23:38 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 21:23:38 vps1 named[835]: not listening on any interfaces Sep 15 22:23:41 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 22:23:41 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 22:23:41 vps1 named[835]: not listening on any interfaces Sep 15 23:23:43 vps1 named[835]: could not listen on UDP socket: permission denied Sep 15 23:23:43 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 15 23:23:43 vps1 named[835]: not listening on any interfaces Sep 16 00:23:45 vps1 named[835]: could not listen on UDP socket: permission denied Sep 16 00:23:45 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 16 00:23:45 vps1 named[835]: not listening on any interfaces Sep 16 01:23:47 vps1 named[835]: could not listen on UDP socket: permission denied Sep 16 01:23:47 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 16 01:23:47 vps1 named[835]: not listening on any interfaces Sep 16 02:23:50 vps1 named[835]: could not listen on UDP socket: permission denied Sep 16 02:23:50 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 16 02:23:50 vps1 named[835]: not listening on any interfaces Sep 16 03:23:52 vps1 named[835]: could not listen on UDP socket: permission denied Sep 16 03:23:52 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 16 03:23:52 vps1 named[835]: not listening on any interfaces Sep 16 04:23:54 vps1 named[835]: could not listen on UDP socket: permission denied Sep 16 04:23:54 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 16 04:23:54 vps1 named[835]: not listening on any interfaces Sep 16 05:23:56 vps1 named[835]: could not listen on UDP socket: permission denied Sep 16 05:23:56 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 16 05:23:56 vps1 named[835]: not listening on any interfaces Sep 16 05:37:19 vps1 pure-ftpd: (?@?) [WARNING] Unknown run-time option Sep 16 06:23:58 vps1 named[835]: could not listen on UDP socket: permission denied Sep 16 06:23:58 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 16 06:23:58 vps1 named[835]: not listening on any interfaces Sep 16 07:24:01 vps1 named[835]: could not listen on UDP socket: permission denied Sep 16 07:24:01 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 16 07:24:01 vps1 named[835]: not listening on any interfaces Sep 16 08:24:03 vps1 named[835]: could not listen on UDP socket: permission denied Sep 16 08:24:03 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 16 08:24:03 vps1 named[835]: not listening on any interfaces Sep 16 08:37:21 vps1 login: ROOT LOGIN (root) ON ttyv0 Sep 16 08:45:16 vps1 pure-ftpd: (?@?) [WARNING] Unknown run-time option Sep 16 09:24:05 vps1 named[835]: could not listen on UDP socket: permission denied Sep 16 09:24:05 vps1 named[835]: creating IPv4 interface lo0 failed; interface ignored Sep 16 09:24:05 vps1 named[835]: not listening on any interfaces
September 16th, 2011, 13:03
iMohsen

پاسخ : مشکل در راه اندازی cPanel و DNS

والا تو این لاگ 2 حالت داره . یا اینه که 2 نسخه از bind نصبه و نسخه اول کانفیگ نشده و و اتوماتیک استارت شده و نسخه دوم که شما کانفیگ میکنی دیگه نمی تونه استارت بشه .
یا این که bind کلا مشکل داره .

حالت دوم اینه که درست کانفیگ نشده باشه . محتویات /etc/named.conf رو بزارید تا ببینیم چیکار میشه کرد .
September 16th, 2011, 13:12
AhmadTux

پاسخ : مشکل در راه اندازی cPanel و DNS

مسیر من اینه :

کد:

/etc/namedb/named.conf

اینم محتویاتش :

کد:

include "/etc/namedb/rndc.key"; controls { inet 127.0.0.1 allow { localhost; } keys { "rndc-key"; }; }; // $FreeBSD: src/etc/namedb/named.conf,v 1.29.2.3.4.1 2010/12/21 17:09:25 kensmith Exp $ // // Refer to the named.conf(5) and named(8) man pages, and the documentation // in /usr/share/doc/bind9 for more details. // // If you are going to set up an authoritative server, make sure you // understand the hairy details of how DNS works. Even with // simple mistakes, you can break connectivity for affected parties, // or cause huge amounts of useless Internet traffic. options { // All file and path names are relative to the chroot directory, // if any, and should be fully qualified. directory "/etc/namedb/working"; pid-file "/var/run/named/pid"; dump-file "/var/dump/named_dump.db"; statistics-file "/var/stats/named.stats"; // If named is being used only as a local resolver, this is a safe default. // For named to be accessible to the network, comment this option, specify // the proper IP address, or delete this option. listen-on { 127.0.0.1; }; // If you have IPv6 enabled on this system, uncomment this option for // use as a local resolver. To give access to the network, specify // an IPv6 address, or the keyword "any". // listen-on-v6 { ::1; }; // These zones are already covered by the empty zones listed below. // If you remove the related empty zones below, comment these lines out. disable-empty-zone "255.255.255.255.IN-ADDR.ARPA"; disable-empty-zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA"; disable-empty-zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA"; // If you've got a DNS server around at your upstream provider, enter // its IP address here, and enable the line below. This will make you // benefit from its cache, thus reduce overall DNS traffic in the Internet. /* forwarders { 127.0.0.1; }; */ // If the 'forwarders' clause is not empty the default is to 'forward first' // which will fall back to sending a query from your local server if the name // servers in 'forwarders' do not have the answer. Alternatively you can // force your name server to never initiate queries of its own by enabling the // following line: // forward only; // If you wish to have forwarding configured automatically based on // the entries in /etc/resolv.conf, uncomment the following line and // set named_auto_forward=yes in /etc/rc.conf. You can also enable // named_auto_forward_only (the effect of which is described above). // include "/etc/namedb/auto_forward.conf"; /* Modern versions of BIND use a random UDP port for each outgoing query by default in order to dramatically reduce the possibility of cache poisoning. All users are strongly encouraged to utilize this feature, and to configure their firewalls to accommodate it. AS A LAST RESORT in order to get around a restrictive firewall policy you can try enabling the option below. Use of this option will significantly reduce your ability to withstand cache poisoning attacks, and should be avoided if at all possible. Replace NNNNN in the example with a number between 49160 and 65530. */ // query-source address * port NNNNN; }; // If you enable a local name server, don't forget to enter 127.0.0.1 // first in your /etc/resolv.conf so this server will be queried. // Also, make sure to enable it in /etc/rc.conf. // The traditional root hints mechanism. Use this, OR the slave zones below. zone "." { type hint; file "/etc/namedb/named.root"; }; /* Slaving the following zones from the root name servers has some significant advantages: 1. Faster local resolution for your users 2. No spurious traffic will be sent from your network to the roots 3. Greater resilience to any potential root server failure/DDoS On the other hand, this method requires more monitoring than the hints file to be sure that an unexpected failure mode has not incapacitated your server. Name servers that are serving a lot of clients will benefit more from this approach than individual hosts. Use with caution. To use this mechanism, uncomment the entries below, and comment the hint zone above. */ /* zone "." { type slave; file "/etc/namedb/slave/root.slave"; masters { 192.5.5.241; // F.ROOT-SERVERS.NET. }; notify no; }; zone "arpa" { type slave; file "/etc/namedb/slave/arpa.slave"; masters { 192.5.5.241; // F.ROOT-SERVERS.NET. }; notify no; }; zone "in-addr.arpa" { type slave; file "/etc/namedb/slave/in-addr.arpa.slave"; masters { 192.5.5.241; // F.ROOT-SERVERS.NET. }; notify no; }; */ /* Serving the following zones locally will prevent any queries for these zones leaving your network and going to the root name servers. This has two significant advantages: 1. Faster local resolution for your users 2. No spurious traffic will be sent from your network to the roots */ // RFC 1912 (and BCP 32 for localhost) zone "localhost" { type master; file "/etc/namedb/master/localhost-forward.db"; }; zone "127.in-addr.arpa" { type master; file "/etc/namedb/master/localhost-reverse.db"; }; zone "255.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; // RFC 1912-style zone for IPv6 localhost address zone "0.ip6.arpa" { type master; file "/etc/namedb/master/localhost-reverse.db"; }; // "This" Network (RFCs 1912 and 3330) zone "0.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; // Private Use Networks (RFC 1918) zone "10.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "16.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "17.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "18.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "19.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "20.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "21.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "22.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "23.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "24.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "25.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "26.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "27.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "28.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "29.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "30.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "31.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "168.192.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; // Link-local/APIPA (RFCs 3330 and 3927) zone "254.169.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; // TEST-NET-[1-3] for Documentation (RFC 5737) zone "2.0.192.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "100.51.198.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "113.0.203.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; // IPv6 Range for Documentation (RFC 3849) zone "0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; // Domain Names for Documentation and Testing (BCP 32) zone "test" { type master; file "/etc/namedb/master/empty.db"; }; zone "example" { type master; file "/etc/namedb/master/empty.db"; }; zone "invalid" { type master; file "/etc/namedb/master/empty.db"; }; zone "example.com" { type master; file "/etc/namedb/master/empty.db"; }; zone "example.net" { type master; file "/etc/namedb/master/empty.db"; }; zone "example.org" { type master; file "/etc/namedb/master/empty.db"; }; // Router Benchmark Testing (RFC 3330) zone "18.198.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "19.198.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; // IANA Reserved - Old Class E Space zone "240.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "241.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "242.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "243.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "244.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "245.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "246.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "247.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "248.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "249.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "250.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "251.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "252.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "253.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "254.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db"; }; // IPv6 Unassigned Addresses (RFC 4291) zone "1.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "3.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "4.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "5.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "6.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "7.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "8.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "9.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "a.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "b.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "c.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "d.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "e.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "0.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "1.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "2.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "3.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "4.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "5.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "6.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "7.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "8.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "9.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "a.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "b.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "0.e.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "1.e.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "2.e.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "3.e.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "4.e.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "5.e.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "6.e.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "7.e.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; // IPv6 ULA (RFC 4193) zone "c.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "d.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; // IPv6 Link Local (RFC 4291) zone "8.e.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "9.e.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "a.e.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "b.e.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; // IPv6 Deprecated Site-Local Addresses (RFC 3879) zone "c.e.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "d.e.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "e.e.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; zone "f.e.f.ip6.arpa" { type master; file "/etc/namedb/master/empty.db"; }; // IP6.INT is Deprecated (RFC 4159) zone "ip6.int" { type master; file "/etc/namedb/master/empty.db"; }; // NB: Do not use the IP addresses below, they are faked, and only // serve demonstration/documentation purposes! // // Example slave zone config entries. It can be convenient to become // a slave at least for the zone your own domain is in. Ask // your network administrator for the IP address of the responsible // master name server. // // Do not forget to include the reverse lookup zone! // This is named after the first bytes of the IP address, in reverse // order, with ".IN-ADDR.ARPA" appended, or ".IP6.ARPA" for IPv6. // // Before starting to set up a master zone, make sure you fully // understand how DNS and BIND work. There are sometimes // non-obvious pitfalls. Setting up a slave zone is usually simpler. // // NB: Don't blindly enable the examples below. :-) Use actual names // and addresses instead. /* An example dynamic zone key "exampleorgkey" { algorithm hmac-md5; secret "sf87HJqjkqh8ac87a02lla=="; }; zone "example.org" { type master; allow-update { key "exampleorgkey"; }; file "/etc/namedb/dynamic/example.org"; }; */ /* Example of a slave reverse zone zone "1.168.192.in-addr.arpa" { type slave; file "/etc/namedb/slave/1.168.192.in-addr.arpa"; masters { 192.168.1.1; }; }; */ zone "ns1.weblar.net" { type master; file "/etc/namedb/working/ns1.weblar.net.db"; }; zone "ns2.weblar.net" { type master; file "/etc/namedb/working/ns2.weblar.net.db"; }; zone "ns3.weblar.net" { type master; file "/etc/namedb/working/ns3.weblar.net.db"; }; zone "ns4.weblar.net" { type master; file "/etc/namedb/working/ns4.weblar.net.db"; }; zone "ahmadtux.com" { type master; file "/etc/namedb/working/ahmadtux.com.db"; };
September 16th, 2011, 13:33
iMohsen

پاسخ : مشکل در راه اندازی cPanel و DNS

کد:

listen-on { 127.0.0.1; };

اینو عوض کن به

کد:

listen-on { any; };

یه بار ریستارت کن ببین درست میشه یا نه .
September 16th, 2011, 13:48
AhmadTux

پاسخ : مشکل در راه اندازی cPanel و DNS

سلام
تو مستنداتش هم گفته بود !

هنوزم کار نمیکنه
September 16th, 2011, 14:02
iMohsen

پاسخ : مشکل در راه اندازی cPanel و DNS

عجیبه !
یه بار named رو kill کنید و با پارامترهای خودش دستی اجراش کنید .

-u bind -c /etc/namedb/named.conf -t /var/named -u bind

ببینین چه خروجی میده .
September 16th, 2011, 19:20
AhmadTux

پاسخ : مشکل در راه اندازی cPanel و DNS

fbsd رو مجدداً نصبیدم

فهمیدم که named پیش فرض نصبه !!!
به نظرتون مشکل تداخلشون این نیست ؟

---------- Post added at 07:14 PM ---------- Previous post was at 07:11 PM ----------

الانم که اسکن میکنم 53 بازه
Discovered open port 53/tcp on 96.127.133.44

---------- Post added at 07:20 PM ---------- Previous post was at 07:14 PM ----------

چطوری unistall کنم وقتی تو لیست pkg_info نیست !؟
September 17th, 2011, 21:09
AhmadTux

پاسخ : مشکل در راه اندازی cPanel و DNS

یافتم !

کد:

http://forums.cpanel.net/f5/3-nameds-running-freebsd-158281.html

به زودی یه آموزش جامع از راه اندازی وب سرور fbsd + cpanel میزارم واسه همه !!!!
September 18th, 2011, 17:41
albaloo18

پاسخ : مشکل در راه اندازی cPanel و DNS

اگر این کار رو زود تر انجام بدی کلی برات دعا می کنیم ...
January 15th, 2012, 17:14
AhmadTux

پاسخ : مشکل در راه اندازی cPanel و DNS

نقل قول:

نوشته اصلی توسط albaloo18

اگر این کار رو زود تر انجام بدی کلی برات دعا می کنیم ...

http://www.webhostingtalk.ir/f93/38758/