jez9999

Well-Known Member
Jun 10, 2005
87
0
156
OK, so I'm regularly receiving these [ipcheck] e-mails, which go something like:

IMPORTANT: Do not ignore this email.
The hostname (vpsxxx.blah.com) resolves to . It should resolve to x.x.x.100. Please be sure to correct /etc/hosts as well as the 'A' entry in zone file for the domain.
The thing is, this is just stupid. For one, I do have /etc/hosts setup to resolve my hostname to my machine's IP address. However, I don't have (in this example) blah.com setup on my nameserver software - why would I? My machine's hostname does NOT have to be in a domain the nameserver for which is hosted on my local machine! If ipcheck had bothered to lookup the hostname on the internet it would've found that it resolved to my IP address fine; the hostname is just resolved by one of my VPS provider's nameservers.

So, my question is, how can I make ipcheck behave more sensibly, or just disable it altogether?
 

chirpy

Well-Known Member
Verifed Vendor
Jun 15, 2002
13,465
30
473
Go on, have a guess
The problem won't be with ipcheck as it does work perfectly correctly in the scenario you have described.

Is your hostname an FQDN in the format hostname.domain.tld?

If so, does the authorattitive DNS server for domain.tld have an A record for hostname pointing to your main IP address on the server?

If that is correct, are you running named on your server?

If you are, do you have your servers IP address in /etc/resolv.conf?

If you do, have you checked that there is no zone file for domain.tld configured in the local DNS?

If there is a zone for domain.tld on the local DNS, delete it.

Double check your /etc/hosts file ane make sure that the only lines are:

127.0.0.1 localhost
11.22.33.44 hostname.domain.tld hostname

With your servers appropriate values.

And finally, if your main network interface is not eth0 (e.g. it's eth1 or a VPS using venet0:0 then ensure that you have that set correctly in WHM > Basic cPanel/WHM Setup > Alternate Main Ethernet Device