i had install cpanel on Cent Os 5 on a VPS
Cpanel Correctly Running but named does not working !
i try to restart named but it say :
root@server [/etc]# service named restart
Stopping named: [ OK ]
Starting named:
Error in named configuration:
none:0: open: /etc/named.conf: file not found
[FAILED]
i have adidcated server any i get anew one and my site is rock2host.com on the domain name i make the ns1 - ns2-ns3-ns4 of ips of the new server but the problem that to this time there is no any account on my server is working as i have adns error but i do not what is the problem i made that
DNS Functions Adding an A entry for your hostname Bind reloading on server using rndc zone: [rock2host.com] Error reloading bind on server: rndc: get config key list: not found
DNS Functions Cleanup Nameserver Config File Fatal! named.conf fails named-checkconf, please repair named.conf and try again
options { default-key "rndc-key"; default-server 127.0.0.1; default-port 953; }; # End of rndc.conf
# Use with the following in named.conf, adjusting the allow list as needed: #key "rndc-key" { # algorithm hmac-md5; # secret "KLGSBmWZrev0I4fR4Tm4GXxdcYSTFzF23b1f9is1M="; #}; # # controls { # inet 127.0.0.1 port 953 # allow { 127.0.0.1; } keys { "rndc-key"; }; # }; # End of named.conf Then i took a look at named.conf
Code: options { /* make named use port 53 for the source of all queries, to allow * firewalls to block all ports except 53: */
//query-source port 53;
/* We no longer enable this by default as the dns posion exploit has forced many providers to open up their firewalls a bit */
// Put files that named is allowed to write in the data/ directory: directory "/var/named"; // the default pid-file "/var/run/named/named.pid"; dump-file "data/cache_dump.db"; statistics-file "data/named_stats.txt"; /* memstatistics-file "data/named_mem_stats.txt"; */ };
logging { /* If you want to enable debugging, eg. using the 'rndc trace' command, * named will try to write the 'named.run' file in the $directory (/var/named"). * By default, SELinux policy does not allow named to modify the /var/named" directory, * so put the default debug log file in data/ : */ channel default_debug { file "data/named.run"; severity dynamic; }; };
// All BIND 9 zones are in a "view", which allow different zones to be served // to different types of client addresses, and for options to be set for groups // of zones. // // By default, if named.conf contains no "view" clauses, all zones are in the // "default" view, which matches all clients. // // If named.conf contains any "view" clause, then all zones MUST be in a view; // so it is recommended to start off using views to avoid having to restructure // your configuration files in the future.
view "localhost_resolver" { /* This view sets up named to be a localhost resolver ( caching only nameserver ). * If all you want is a caching-only nameserver, then you need only define this view: */ match-clients { 127.0.0.0/24; }; match-destinations { localhost; }; recursion yes;
zone "." IN { type hint; file "/var/named/named.ca"; };
/* these are zones that contain definitions for all the localhost * names and addresses, as recommended in RFC1912 - these names should * ONLY be served to localhost clients: */ include "/var/named/named.rfc1912.zones"; };
I'd like to add geodns to BIND, so I need to modify named.conf. All that I will put into is a include of an acl file (for different IP ranges), and add a new view for existed domain.
My VPS use cPanel. What is the best way to handle this, as named.conf can be modify by cPanel? I can modify the template in /scripts/rebuilddnsconfig, but I don't know how to add a new view.
There's only one site in my VPS. But I use a few subdomains in DNS (legacy issues). Only one db file in /var/named/
I have the following problem: When i try to restart the nameserver service i get the following error:
# service named restart Stopping named: [ OK ] Starting named: Error in named configuration: /etc/named.conf:87: unknown option 'e' /etc/named.conf:120: unexpected end of input [FAILED] my named.conf as follows:
options { /* make named use port 53 for the source of all queries, to allow * firewalls to block all ports except 53: */ query-source port 53;
// Put files that named is allowed to write in the data/ directory: directory "/var/named"; // the default dump-file "data/cache_dump.db"; statistics-file "data/named_stats.txt"; /* memstatistics-file "data/named_mem_stats.txt"; */ };
logging { /* If you want to enable debugging, eg. using the 'rndc trace' command, * named will try to write the 'named.run' file in the $directory (/var/named). * By default, SELinux policy does not allow named to modify the /var/named directory, * so put the default debug log file in data/ : */ channel default_debug { file "data/named.run"; severity dynamic; }; };
// All BIND 9 zones are in a "view", which allow different zones to be served // to different types of client addresses, and for options to be set for groups // of zones. // // By default, if named.conf contains no "view" clauses, all zones are in the // "default" view, which matches all clients. // // If named.conf contains any "view" clause, then all zones MUST be in a view; // so it is recommended to start off using views to avoid having to restructure // your configuration files in the future.
view "localhost_resolver" { /* This view sets up named to be a localhost resolver ( caching only nameserver ). * If all you want is a caching-only nameserver, then you need only define this view: */ match-clients { 127.0.0.0/24; }; match-destinations { localhost; }; recursion yes;
zone "." IN { type hint; file "/var/named/named.ca"; };
// include "/var/named/named.rfc1912.zones"; // you should not serve your rfc1912 names to non-localhost clients.
// These are your "authoritativ zone "smpl.splinteredmedia.net" { type master; file "/var/named/smpl.splinteredmedia.net.db"; };
e" internal zones, and would probably // also be included in the "localhost_resolver" view above : };
view "external" { /* This view will contain zones you want to serve only to "external" clients * that have addresses that are not on your directly attached LAN interface subnets: */
recursion no; // you'd probably want to deny recursion to external clients, so you don't // end up providing free DNS service to all takers
// all views must contain the root hints zone: zone "." IN { type hint; file "/var/named/named.ca"; };
// These are your "authoritative" external zones, and would probably // contain entries for just your web and mail servers:
// BEGIN external zone entries
};
z zone "smpl.splinteredmedia.net" { type master; file "/var/named/smpl.splinteredmedia.net.db"; };
I'm getting this warning from check server security option in csf : -------- You have a local DNS server running but do not have any recursion restrictions set in /etc/named.conf. This is a security and performance risk and you should look at restricting recursive lookups to the local IP addresses only -------- I saw named.conf but In fact I didn't understand what should I do Can somebody tells me what should i do and what this warning trying to tell me?
After Cpanel update latest release version. I have issue with named.conf. I tried to rebuild named. but..
/scripts/rebuilddnsconfig fixrndc requires a syntactically correct /etc/named.conf. No changes were made to /etc/named.conf.
Problem was:
/etc/named.conf:23: when using 'view' statements, all zones must be in views Anyone can explain me about "/etc/named.conf:23: when using 'view' statements, all zones must be in views"?
I was tring to upgrade my kernel and after installing new kernel i tried to select kernel but i was unable to find grub.conf file ! /boot/grub/grub.conf
Rapidly growing error logs showing the same message
$ug-non-zts-20020429/ffmpeg.so' - /usr/local/lib/php/extensions/no-debug-non-zts-20020429//usr/local/lib/php/extensions/no-debug-non-zts-20020429/ffmpeg.so: cannot open shared object file: No such file or directory in Unknown on line 0
root@server [~]# ls /usr/local/lib/php/extensions/no-debug-non-zts-20020429 ./ ../ eaccelerator.so* root@server [~]# ls /usr/local/lib/php/extensions/no-debug-non-zts-20020429 ./ ../ eaccelerator.so*
I work for a start up as well as do independent consulting. I had a friend set up my apache server initially for the start up. It's been running fine. Now I want to host a client's site on the same server. I tired just adding a vhost section at the bottom of the conf file, but it said that I was running two sites off the same port. I tried manipulating the stuff my buddy did for me for the first site, then putting two vhosts on the bottom, but that just didn't work.
I recently needed to make some changes to the domain.conf file at the following path: /etc/nginx/plesk.conf.d/vhosts. When I try to edit the file it just has 3 lines at the top warning me that the changes made here would not persist, while other domain confs have full configs inside.
I am positive that the domain in question is set to use nginx, double checked this, so what gives? Why is the file blank?
I have following error when try to login in my vps, how can resolve this issue?
Code:
Last login: Thu Jun 19 21:00:43 2008 from xxx.xxx.xxx.xxx
ALERT! You are entering a secured area! Your IP and login information have been recorded. System administration has been notified. This system is restricted to authorized access only. All activities on this system are recorded and logged. Unauthorized access will be fully investigated and reported to the appropriate law enforcement agencies.
I am trying to increase my open file limit on my CentOS release 4.6 VPS.
I have tried modifying my /etc/security/limits.conf with the following: @mysql soft nofile 4096 @mysql hard nofile 4096 @mysql soft sigpending 4096 @mysql hard sigpending 4096
Even is a mannual set it with "ulimit -n 4096 mysql" it will not stick.
Any ideas what I can do to get this limit increased permanently?
When trying to access any files or pages I'm getting the error:"Not Found...The requested URL /wp-login.php was not found on this server.Apache Server at calmcomputing.net Port 80"
The standard default page displays but my Wordpress installation does not (nor does anything for that matter). I've looked in the file manager (and via ftp) and all the files are there like they should be. This is the same for any of the subdomains that I've setup as well.
I see some errors about lame servers in messages log,and i noticed that look like adress of isp surfer domain beacuse i noticed domain of my isp listed also as lame name server.Here is example:
Nov 24 03:46:55 available9 named[7562]: lame server resolving '247.100.51.72.in-addr.arpa' (in '100.51.72.in-addr.arpa'?): 205.214.192.202#53 Nov 24 03:46:55 available9 named[7562]: lame server resolving '247.100.51.72.in-addr.arpa' (in '100.51.72.in-addr.arpa'?): 205.214.192.201#53 Nov 24 03:46:56 available9 named[7562]: lame server resolving '247.100.51.72.in-addr.arpa' (in '100.51.72.in-addr.arpa'?): 205.214.192.202#53 Nov 24 03:46:56 available9 named[7562]: lame server resolving '247.100.51.72.in-addr.arpa' (in '100.51.72.in-addr.arpa'?): 205.214.192.201#53 Nov 24 07:19:51 available9 named[7562]: FORMERR resolving 'ducksimilar.com/NS/IN': 203.93.208.87#53 Nov 24 07:19:51 available9 named[7562]: FORMERR resolving 'ducksimilar.com/NS/IN': 91.208.228.150#53 Nov 24 07:19:52 available9 named[7562]: FORMERR resolving 'host1.experienceexcept.com/AAAA/IN': 203.93.208.87#53 Nov 24 07:19:52 available9 named[7562]: FORMERR resolving 'host2.experienceexcept.com/AAAA/IN': 203.93.208.87#53 Nov 24 07:19:52 available9 named[7562]: FORMERR resolving 'host1.experienceexcept.com/AAAA/IN': 91.208.228.150#53 Nov 24 07:19:52 available9 named[7562]: FORMERR resolving 'host2.experienceexcept.com/AAAA/IN': 91.208.228.150#53 Nov 24 07:19:52 available9 named[7562]: FORMERR resolving 'host1.experienceexcept.com/AAAA/IN': 203.93.208.87#53 Nov 24 07:19:52 available9 named[7562]: FORMERR resolving 'host2.experienceexcept.com/AAAA/IN': 203.93.208.87#53 Nov 24 07:19:52 available9 named[7562]: FORMERR resolving 'host1.experienceexcept.com/AAAA/IN': 91.208.228.150#53 Nov 24 07:19:52 available9 named[7562]: FORMERR resolving 'host2.experienceexcept.com/AAAA/IN': 91.208.228.150#53
On attempting to select the configuration->filter option on RoundCube, we got the error message:
SERVICE CURRENTLY NOT AVAILABLE! Error No. [501]
On /var/log/plesk-roundcube/errors we can see the following logs:
[06-Jun-2015 14:57:17 -0300]: PHP Error: SieveRules plugin: Unable to open default rule file in /usr/share/psa-roundcube/plugins/sieverules/sieverules.php on line 1523 (GET /roundcube/?_task=settings&_action=plugin.sieverules) ... [06-Jun-2015 14:57:17 -0300]: PHP Error: SieveRules plugin: Unable to open example rule file in /usr/share/psa-roundcube/plugins/sieverules/sieverules.php on line 1560 (GET /roundcube/?_task=settings&_action=plugin.sieverules) ... [06-Jun-2015 14:57:17 -0300]: PHP Error: Error loading template for sieverules.sieverules in /usr/share/psa-roundcube/program/include/rcmail_output_html.php on line 496 (GET /roundcube/?_task=settings&_action=plugin.sieverules)
