I hope your day is going good. I've been trying to fix a problem I had all week. I receive daily email notification that "example.[url]" does not resolve to any IP. However, when in WHM, it already contains Server Main Ip: 208.53.183.125. I've tried a few solutions from the web, but to no avail:
IMPORTANT: Do not ignore this email. The hostname (example.mydomainname.com) resolves to . It should resolve to 208.53.183.125. 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 you believe 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
1) Within WHM, I have the following:
-Add an A entry for your hostname (I only have one listed) Hostname: example.mydomainname.com Server Main Ip: 208.53.183.125
-Primary/secondary nameserver Primary Nameserver: ns1.mydomainname.com (A entry = 208.53.181.26) Secondary Nameserver: ns2.mydomainname.com (A entry = 208.53.181.27)
-Additional IP my webhost gave me to use: 208.53.181.26 (used in primary name server) 208.53.181.27 (used in secondary name server) 208.53.181.28
-Current DNS Zone listing: example.com (my website URL that is currently working) example.mydomainname.com (hostname I made myself that contains the server main IP) ns1.mydomainname.com (A entry = 208.53.181.26) ns2.mydomainname.com (A entry = 208.53.181.27)
2) My edit "edit /etc/resolv.conf" contains the following: Search localdomain nameserver 66.90.68.25 nameserver 66.90.68.26
Issue: I receive daily email notification that "example.mydomainname.com" does not resolve to any IP. However, when in WHM, it already contains Server Main Ip: 208.53.183.125.
The following error was encountered: Unable to determine IP address from host name for www.gbn.ge The dnsserver returned: Server Failure: The name server was unable to process this query. This means that:
The cache was not able to resolve the hostname presented in the URL.
Check if the address is correct.
Your cache administrator is webmaster.
Generated Wed, 16 Apr 2008 13:13:49 GMT by proxy.geonet.ge (squid/2.6.STABLE19)
I have a dedicated WHM server (qumbia.org) with several CPanel accounts, among them:
- qumibiao (qumbia.org). - qumbiaca (qumbia.ca).
Both of these accounts were set to the same ip (70.86.221.122).
15 days ago, I changed qumbiaca to the ip 70.86.221.123
Since, some requests (about 1% of the total according to my logs) for qumbia.ca are still serving up what's in /home/qumbiao/public_html
I know next to nothing about this, but perhaps some ISPs have cached the 70.86.221.122 IP and are directing requests there? Still, why wouldn't WHM, upon receiving such a request, resolve it to the right address, it being on the same server?
My Time to live record is set to 24 hours on my DNS, and the expire header set to 41 days.
Might it be a good idea to set up a new DNS (NS3.QUMBIA.ORG) on my WHM and give that DNS to qumbia.ca? Would this force the ISPs to reset their cache? Or does the problem lie elsewhere? Should I just wait out the 41-day expire period and hope for the best?
i have a domain registered within PLESK having the same name as the server itself. After a short period of time the domain shows up the PLESK default page instead of the original content located in the vhost httpdocs directory.
To restore the content it's possible to deactivate and re-activate the domain from the customers control panel. But after an amount of time the default page comes back.I first recognized the error after the update to PLESK 12.
My VPS was a clean build 2 weeks ago and so far i have installed cpanel and configured everything and added accounts. I began that one of my scripts that uses gethostbyaddr($ip) was failing to resolve any of the ip's it received. I made another PHP file to test this, with this code:
PHP Code:
<?phpecho file_get_contents[url];?>
Resulting in:
Warning: file_get_contents() [function.file-get-contents]: php_network_getaddresses: getaddrinfo failed: Name or service not known
The thing is, the VPS is resolving domains just fine
;; ANSWER SECTION: google.com. 300 IN A 64.233.167.99 google.com. 300 IN A 64.233.187.99 google.com. 300 IN A 72.14.207.99
;; AUTHORITY SECTION: google.com. 343652 IN NS ns2.google.com. google.com. 343652 IN NS ns3.google.com. google.com. 343652 IN NS ns4.google.com. google.com. 343652 IN NS ns1.google.com.
;; ADDITIONAL SECTION: ns1.google.com. 343143 IN A 216.239.32.10 ns2.google.com. 343143 IN A 216.239.34.10 ns3.google.com. 343143 IN A 216.239.36.10 ns4.google.com. 343143 IN A 216.239.38.10
i use centos based server. yesterday everything was OK. but now, when i connect via SSH, my server can't resolve hosts. wget, ping, or curl don't work. also i use VNC to remote desktop. when try to open a page via firefox, it says server not found.
I got a new server from uk2, has whm but i just couldnt get the server to work, i changed hostname and made nameservers etc but couldnt get it to work i pointed ips to hostnames and everything no response, domain is www.uploadline.com ns1.uploadline.com and ns2.uploadline.com i havent used cpanel for 2 years now and i used to have alot of experience in it before these days i just stick to directadmin and other control panels.
I just need to ask a few questions and i need help too to get my server up and running as im losing alot of time and money here
i remembered when i changed hostname on whm i need to run this through ssh: /usr/local/cpanel/cpkeyclt So i did, and this was the result:
Quote:
login as: rootroot@server80004.uk2net.com's password: Last login: Sat Nov 1 01:39:07 2008 from proxy-sov.uk2.net root@server1 [~]# /usr/local/cpanel/cpkeyclt Updating Internal cPanel Information........................................quer y failed: query timed out [cpkeyclt.pl]: No working dig found! Unable to establish connection. License server hostnames could not be resolve to IPs. Done .Done root@server1 [~]#
i am having a problem getting a dedicated server running for Unreal Tournament GOTY. everytime i create a dedicated server i get this error in the console:
Log: AInternetLink Resolve failed: Can't find host master.mplayer.com (WSANO_DATA) ScriptLog: UdpServerUplink: Failed to resolve master server address, aborting.
I have a fresh server running CentOS 6 (final). I am trying to install Plesk 11.5.30 but i am experiencing some problems. When i run the plesk-installer i get this message:
Your host name must resolve to the correct IP address of your server, unless you are using network address translation (NAT).
Please quit Parallels Installer, fix the host name resolution problem, and then try installing again.
You can skip the hostname check and continue the installation, however, in such a case, the installer cannot guarantee successful installation.
I'm wondering whether it is possible to perform a full server migration to a new Plesk server with the same hostname or will Plesk give an error about the hostname being the same?
The new server would not be accessible by hostname (only via IP) until DNS and glue records were changed after the migration.
I know how to do this by analysing the headers, but we have a customers who doesn't believe what we are telling them.
Is there some kind of 3rd party service or script that we can point them to? So they can send an email to the service (or paste headers, or whatever) and it tells them who is the sending mail server hostname/ip?
(The problem is that this customer doesn't understand that all email sent from the server uses the same SMTP server hostname/ip. They are convinced that if they connect to "mail.their domain.com" then this is what is reported as the sending mail server/IP.)
I have an existing server running cpanel that I would like to change the hostname on. What I am curious about, is the effects on the rest of the server if I go and change it. From what I can tell, the current host name is being used all over the place, and I don't know if cpanel updates everything on it's own, or if I would need to manually update everything after I change the name.
our company is ordering a new dedicated server and we are a little unsure what we should choose as far as the full hostname and nameservers of this one server.
This server will have a couple different websites on it, but really, there is only one BIG website on it... let's call it abcd.com.
While most would pick a hostname of host.abcd.com for instance, if at all possible, we would like the domain name part of the hostname to be something different than abcd.com. We own a domain name that doesn't point to anything yet (unuseddomain.com) and we were wondering if we could use that domain in our hostname.. host.unuseddomain.com.
And instead of using abcd.com as the domain name for our own nameservers (ie. ns1.abcd.com, ns2.abcd.com), we would like to again, use the unused domain name we own (unuseddomain.com) for the nameservers domain name: ns1.unuseddomain.com, ns2.unuseddomain.com.
So...
Will this work? Is this perfectly acceptable?
And lastly...
Since the one website we really care about on this server (the one we got the server for in the first place) is abcd.com, is using the unuseddomain.com for the hostname and nameservers (as above) a bad choice in anyway regarding email deliverability? I understand that mail ISP's (hotmail, yahoo, etc.) do all kinds of checks on hostnames (PTR), etc... and we want to make sure that we aren't hurting ourselves in anyway by using an "empty" domain name that we own as our hostname's and nameserver's domain name.
For instance, if we send mail from the abcd.com account, it will use mail.abcd.com (1.1.1.1) as it's outgoing mail server... Hotmail will see this... do a reverse-dns lookup on 1.1.1.1 and see host.unuseddomain.com. See what I'm saying? It all will work, but will it toss up red flags?
I enter one of my IPs or the hostname belonging to this IP, followed by the Plesk port, and I get redirected to the "main" hostname of the server, which was set in Plesk. But at this moment that hostname is used by another server (my old server) and so I'm redirected to the other server and cannot access Plesk on the new server.
I don't know why Plesk reacts like this, because it did not on the old server. Here the problem more detailed:
I'm just configuring my new server with Plesk 11. My old server uses Plesk 10. On my old server / in Plesk 10 I have the following scenario:
- I have several IPs (10) - Each IP is used for a different domain - Each IP has it's domain as the reverse entry (configured outside of the server/Plesk) - Each IP is set to "Dedicated" in Plesk - I set Plesk to listen only on one of these IPs (and different port) - Several domains are created in Plesk, but not a domain for my Plesk IP - The server's name is one of the domains (required for mails not being recognized as spam) - The hostname of the Plesk IP is one assigned by my provider (something like x-x-x-x.xyzservers.com) - Entering the IP of Plesk redirects to the "Plesk hostname" => Plesk can be accessed by using x-x-x-x.xyzservers.com:myport
And under Plesk 11 (here comes the problem):
- Still several IPs (but less: 4) - One IP should be used for Plesk, one for domain X, one for domain Y and the last one for the other domains - Reverse entries are x-x-x-x.xyzservers.com for Plesk IP, domain X/Y for two other IPs and the main domain for the last IP - Plesk IP and the two single domain IPs are configured as dedicated, the last one as shared - At this point I did not configure any domains in Plesk - Server's name is the same as my old server (the main domain) => Entering any IP with the Plesk port redirects to the servers hostname, e.g. my main domain, which is still on the old server. => Result: I cannot access Plesk!
Of course I could just change the hostname of the server via SSH (just have to find out how to do this), but why does Plesk react in another way now? Or is the problem that I cannot change Plesk to listen on only one IP?
I've been having some DNS problems with one of my domains for quite some time now. The domain does not always resolve - some go days without being able to access the site.
I ran a simple BASH script to show what I mean. I replaced my domain with "mysite.net" and the IP with "xx.xx.xxx.xxx".
# for i in `seq 1 15`; do host mysite.net; done
mysite.net has address xx.xx.xxx.xxx mysite.net mail is handled by 0 mysite.net. Host mysite.net not found: 2(SERVFAIL) mysite.net has address xx.xx.xxx.xxx Host mysite.net not found: 2(SERVFAIL) mysite.net has address xx.xx.xxx.xxx Host mysite.net not found: 2(SERVFAIL) mysite.net has address xx.xx.xxx.xxx Host mysite.net not found: 2(SERVFAIL) mysite.net mail is handled by 0 mysite.net. mysite.net has address xx.xx.xxx.xxx Host mysite.net not found: 2(SERVFAIL) Host mysite.net not found: 2(SERVFAIL) mysite.net has address xx.xx.xxx.xxx Host mysite.net not found: 2(SERVFAIL) mysite.net mail is handled by 0 mysite.net. mysite.net has address xx.xx.xxx.xxx mysite.net mail is handled by 0 mysite.net. mysite.net has address xx.xx.xxx.xxx mysite.net mail is handled by 0 mysite.net. mysite.net has address xx.xx.xxx.xxx mysite.net mail is handled by 0 mysite.net. mysite.net has address xx.xx.xxx.xxx Host mysite.net not found: 2(SERVFAIL) mysite.net has address xx.xx.xxx.xxx mysite.net mail is handled by 0 mysite.net. mysite.net has address xx.xx.xxx.xxx mysite.net mail is handled by 0 mysite.net. mysite.net has address xx.xx.xxx.xxx mysite.net mail is handled by 0 mysite.net. mysite.net has address xx.xx.xxx.xxx mysite.net mail is handled by 0 mysite.net.
Has anyone experienced a similar problem? I have gone over the DNS records countless times and see no problems. The site is hosted on my own dedicated server.
I have a server that I use to host my primary domain, and I have a cople Plesk servers, now I updated the hostnames of all the servers like
Code: s1.de.myserverplace.de
Now when the plesk server sends a mail it goes in spam always,
In the SPF records of the primary domain sits this
Code: myserverplace.de. IN TXT "v=spf1 a mx a:myserverplace.de a:s1.de.myserverplace.de ip4:148.251.100.157 ip4:144.76.163.46 ip6:2a01:4f8:201:81b8::60 ?all"
But when I actually send the mail in the headers of the received mail I get this.
Code: Received: from s1.de.myserverplace.de (s1.de.myserverplace.de. [144.76.163.46]) by mx.google.com with ESMTPS id p2si2158952wjy.73.2015.05.14.04.09.17 for <mymailtestacount@gmail.com> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Okay guys, a quick question for all the gurus out there. I'll admit I'm a bit embarassed posting such an easy question, but give a guy a break, I've been using managed servers for god knows how long and I've finally decided to take a dive into administration. Everything is firewalled and secured properly, I'm just having trouble getting the ServerAlias to work right.
What happens is I go into my browser and enter in [url]walaa! It works.
Now, when I enter in [url], it does not resolve.
I have checked with "dig" the domain settings and it looks as though all of the nameservers are set up fine, this is an apache problem. I'm running apache 2.2 on Ubuntu 7.10 for all those who are interested.
Here is my etc/apache2/sites-available/domain.com:
<VirtualHost *:80>
# Admin email, Server Name (domain name) and any aliases ServerAdmin webmaster@domain1.com ServerName domain.com ServerAlias www.domain.com
# Index file and Document Root (where the public files are located) DirectoryIndex index.html DocumentRoot /home/demo/public_html/domain.com/public
I've been having this problem for a while now. I have a dedicated linix server running with the cpanel. I've setup my own nameservers and for the most part it all runs without a problem. However, every now and then the domains will not resolve for many people.
This may only last a few minutes but it happens regularly. There doesn't seem to be any pattern. The server is still available via IP address. Also, any domain name set as a nameserver with the registrar is not affected by this problem. All other domains are affected. This problem has persisted over many cpanel updates.
I have gone through all the nameserver files (I can think of or have read about) looking for something that may be causing this but everything looks normal.
