I have a new VPS server in which I did not configure the /etc/resolv.conf file. My VPS has three domains that are all working and resolving fine. But I keep getting an email from my provider that says this:
The hostname (v6.volumedr.com) resolves to. It should resolve to xx.xx.xx.xx. Please be sure to correct /etc/hosts as well as the 'A' entry in zone file for the domain.
Some are all of these problems can be caused by
/etc/resolv.conf being setup incorrectly. Please check this file if youbelieve everything else is correct.
You may be able to automaticly correct this problem by using the Add an A entry for your hostname ' under ' Dns Functions ' in your Web Host Manager.
Why does the actual server hostname need to resolve via dns?
I have confirmed that /etc/hosts looks good and I added an A record in my WHM for each domain. Do I need to configure the /etc/resolv.conf file too? Do I need to list my three domains and my server hostname(v8) and then my two primary DNS servers?
I'm supposed to be completing a server migration on Saturday night. But I have one teeeeny tiny problem....
I have no DNS/nameservers provided by my new DC for the resolv.conf.
They have them - but I don't think they operate like true root nameservers or something. I keep getting a ton of Unroutable Mail Domain errors for server email that should be leaving the new box.
When the resolv.conf was set to use the 4.2.2.x dns servers - it was working fine. And I don't know if it's ok to just keep it using those or not?...
What other DNS servers can I use for the resolv.conf? Any DC's nameservers? Are there "public" ones available somewhere?
Is it better to put the IP of your server on the first line followed by the dns servers from the datacenter? And, how do you make the changes go in effect? I assume you just restart bind?
Yes using NSLOOKUP and DIG both always return results from the first name server if it is up (no rotation) and when it is down, the timeout is the default 5 seconds (not the 2 that I specified) before going to the second name server.
I have a VPS (ConetOS 4.4, OpenVZ), it all works fine, however on reboot, the resolv.conf gets reset to some nameservers that are no longer in use, How do I change this so after a reboot it uses the nameservers I am using now?
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 just got a very cheap box intended to learn HyperVM/OpenVZ. just got it tonight and got 5 IPs. So I add those 4 IPs in the Resources > IP Pools section. I don't know what to add in the Resolv Entries (space Separated) field.
if this is not the correct forum for this, please be free to move them.
I have 2 servers hosted with SoftLayer, In 22 Jun, I had reboot my servers, one of them didn't start and then SL said that it's was a reslov problem and we fix it, after that day, I start seeing all my websites traffic start go down , I check Google Analytics and the visitors number is going down everyday, I open a ticket and say that to SL and i think it's was a DNS problem they tell me after a lot of replys that they fix it and i must wait for 72 hours that need for the dns to be updated worldwide, I didn't say that SL support is bad no they are very very helpful support and many thanks to them, but i wanna to listen to your opinions here about my problem, and from where it's?
I have nginx conf which works perfectly fine with ip adress,but when i put domain then php for some reason no longer works,i getting download php file situation.
Here is main conf file:
####################################################################### # # This is the main Nginx configuration file. # # More information about the configuration options is available on # * the English wiki - http://wiki.codemongers.com/Main # * the Russian documentation - http://sysoev.ru/nginx/ # #######################################################################
#---------------------------------------------------------------------- # Main Module - directives that cover basic functionality # # http://wiki.codemongers.com/NginxMainModule # #----------------------------------------------------------------------
I'm about to set my own permalink rules in Wordpress.
My VPS is running LxAdmin on CentOS and I have lighttpd installed. I've read I need to edit lighttpd.conf but I don't know which application I should use. The file is located in /etc/lighttpd/ but have no idea how to gain access.
I tried that recently to install PHP 4 & PHP 5 on the same server - without any luck, i stumbled into a massive hole.
the existing httpd.conf was replaced and there was a backup made - stupid me accidently deleted this backup file and was left this a non-working copy of httpd.conf - if anyone can help me it would be much appreciated.
root@server1 [~]# /etc/init.d/httpd configtest Warning: DocumentRoot [/dev/null] does not exist Syntax OK
I would like to set some hard limits for some developmental testing I am doing using quota tools and what not. In limits.conf I have the following:
-------- @dev hard cpu 0.30 --------
As far as I can see, this would limit all users in the group "dev" from using more than half a minute of CPU time, am I correct?
Assuming I am, once I write these changes no limits seem to be enforced. Are these values cached in the memory and a reboot is needed for them to take effect?
I just installed a new version of CSF again on my server.
Based on the article and tutorial that I read, I do not have to change anything much on the csf.conf if I am installing it for WHM/Cpanel server.
I notice new version 3.33 has new function such as synflood and so on, can someone tell me if I need to change any settings inside my csf.conf other than disabling the testing = 0 on a fresh new cpanel server?
I recently updated to apache 2.2 and when I went to check
/usr/local/apache/conf/httpd.conf
I noticed that a lot of the stuff was missing from what I usually see in apache 1.3 Was a new file created when the update was finish? I used easyapache to make the update.
I was playing with a backup machine I have today. It's been running FreeBSD 6.3 a while now. I just realised today that CPUTYPE in make.conf was set wrong. When I set it to what it should be, according to the list of valid values, I got odd errors during world and kernel rebuilds, along with some from some ports. I googled it and found many people do not suggest setting that directive in make.conf. May I ask if anybody has experience with this, and what impact it would have on my box should I remove the directive and recompile?
I'm trying to accomplish a redirect (or rewrite) of [url]to [url]
* I got DNS *.domain.com correctly pointing to my server. * I also created a vhost.conf inside /var/www/vhosts/domain.com/conf, and Plesk (/var/www/vhosts/domain.com/conf/httpd.include) is correctly including the file. * even though I don't know if it's needed or not, I created in Plesk a new CNAME with value *.domain.com pointing to domain.com
how should I optimize httpd.conf on my server. Apache was set up by my friend, unfortunately it started to "stuck" lately during peak time. Browser is connecting to a website for a long time before it actually starts to load it.
I remember seeing a website/forum where you couldn't post your server stats and httpd.conf settings and experts would give advice on settings you should use.
Does anyone know the url to this site, or site similar to it
I installed postgres and i seem to have a problem connecting to it both locally and remotely.
this is the error i get:
Code: Warning: pg_connect() [function.pg-connect]: Unable to connect to PostgreSQL server: FATAL: missing or erroneous pg_hba.conf file HINT: See server log for details. in /var/www/html/2.3/includes/configuration.php on line 25 these are the contents of my pg_hba.conf file
Code: # TYPE DATABASE USER CIDR-ADDRESS METHOD
# "local" is for Unix domain socket connections only #local all all ident sameuser local all all trust all
#@remove-line-for-nolocal@local all all @authmethod@ #host all all 10.0.0.1 255.255.255.0 trust
host all all all trust all
# IPv4 local connections: #host all all 127.0.0.1/32 ident sameuser host all all 127.0.0.1/32 trust all # IPv6 local connections: host all all ::1/128 ident sameuser
i'd imagine "host all all all trust all" would allow anyone to access it, wouldn't it?
