Where do I configure reverse dns for the domain?

1) Checking the reverse DNS of the IP []: $ Host Host not found: 3 (NXDOMAIN)

Result: ERROR, IP [] does not resolve to a valid host.

The DNS IP [] is not configured correctly

Response test: Remember that in order for the configuration to work correctly, you must configure the reverse DNS, to correctly reverse delegation for the DNS server and also make the configuration of corresponding direct.



Reverse DNS is typically setup at your ISP.

They often have a control panel where you can setup your reverse DNS, but some times you would need to call them or file a support request.

You do not have a way to do this in centos xen or webmin or cloudmin, or tell me how to do it on my server since the ips are already delegated to my system and duly registered in my router?

The first step is to check the file "/ etc / hostname" and "/ etc / hosts" (on the server), which must contain the hostname and domain registered.

The file "/ etc / hostname" must contain only the hostname, as in:


In Fedora and some other distributions, the hostname vai within the file "/ etc / sysconfig / network".

The file "/ etc / hosts" file must contain two entries, one for the loopback interface, and the other for the internet IP of your server, which is linked to the domain, as in: localhost localhost.localdomain etch

From there, add the missing reverse zone in bind complementing domain configuration, we've done. We start by adding the entry in "/ etc / bind / named.conf" or "/ etc / bind / named.conf.local":

zone "" { type master; file "/ etc / bind / db.kurumin.rev"; };

In our example, the IP address is If we remove the last octet and write the rest of the address backwards, we have just the "23.234.64" we use the reverse record. The third line indicates the file where the configuration is saved reverse domain. In this case, the file indicated "db.kurumin.rev" but you can use any file name.

This file "db.kurumin.rev" is very similar to the configuration file of the domain. The three initial lines are identical (including the number of timing), but instead of using the "A" list for each domain and subdomain corresponding to IP, we use the policy "PTR" to list the IP address of each server to the domain (is precisely why we call reverse DNS ;).

In the first file, use only the first three octets of the address (the part on the network), removing the final octet (the address of the server within the network). Now, we used only the number of first omitted.

The server IP is ""; removing the first three octets are only left with the "12". We also have the secondary DNS address, which is, where we used only "13". Relating the two to their respective fields, the file is:

@ IN SOA ( 2006040645 3H 15M 1W 1D) NS NS 12 PTR. 13 PTR.

If you are not using a secondary DNS, just omit the rows relating to it, as in:

@ IN SOA ( 2006040645 3H 15M 1W 1D) NS 12 PTR.

When finished, restart Bind and check using dig. Start checking the area, as in:

From what I understand issso must be configured on my linux and not elsewhere.

Are you sure your provider has delegated that reverse to your system? Because I don't see any sign of this when doing DNS lookups ..

I ask again:

This is not an operation done on my own linux with a script in a file?

These delegates were already ips however was not done the reverse dns because this is a matter directly related to the domain. It seems that we are not talking about the same thing ..

This is not an operation done on my own linux with a script in a file

Reverse DNS is very rarely setup on your own system.

You can setup forward DNS records by going into Server Configuration -> Edit DNS Records in Virtualmin.

And there are details for how to setup your server to act as a nameserver here in the article titled "How do I setup nameservers for my server":

However, as far as Reverse DNS goes -- Reverse DNS is is not typically controlled on your own server, even if you control the forward DNS.

Reverse DNS is typically setup by your provider/ISP.