Knowledgebase
Knowledgebase
Portal Home > Knowledgebase > Articles Database > HyperVM RDNS Not Working
HyperVM RDNS Not Working
Posted by Siterack_net, 03-09-2011, 09:06 AM I am having troubles getting HyperVM's rdns slave server working. I am using HyperVM, internally, to divide my servers into VPS containers, so a single website cannot take down an entire server. So before the flames begin, about security, I do NOT use hypervm to sell vps's from It's an excellent platform for internal use. According to my DC everything is setup for me to be able to run my own RDNS server. However, if I try to do an RDNS lookup, I get the following results... DNSTOOLS= xxx.xxx.xxx.xxx resolves to same INTODNS = ERROR: No reverse DNS (PTR) entries. The problem MX records are: xxx.xxx.xxx.xxx.in-addr.arpa -> no reverse (PTR) detected 12DT.COM=(unable to resolve xxx.xxx.xxx.xxx) Not sure what step I am missing here. There is, at this time, no firewall installed for the host node or the hypervm container handling rdns. I did add rdns entries for each IP of each VPS on the node. If anyone has any ideas, it would be greatly appreciated.
Posted by eth00, 03-09-2011, 05:11 PM Try: dig +trace -x IP-Address Based off of the domain posted above it looks like you already got it working
Posted by Siterack_net, 03-09-2011, 05:14 PM If by domain above, you are referring to siterack.net, then no Siterack.net is on it's own server elsewhere. However, I gave up on my own rdns server, and told the DC to take over. Another thing I had noticed, was that the rdns slae was not even collecting the ip data from the master. So it gets back to that whole authentication issue I have been experiencing.
Posted by mugo, 03-10-2011, 03:12 AM Your DNS server has the be authoritive for the IPs. This is normally your ISP / Hosting providers main DNS, they have to allocate to YOUR DNS servers to actually have this work. In most instances, you have to have a specific in-addr.arpa zone name, this depends on the network size and class(less). How many IPs do you have and what is the zone name? You do have your PTR records setup? Basically, the zone name you are using to name your rDNS pointers has to be a secific name. I've found that many providers are lacking in this knowledge...they know how to point it to you, but are clueless on the zone file name you need to answer with. Realistically, your zone file should look something like 0/25.1.168.192.in-addr.arpa for a /25 network, if your network is 192.168.1.0/25. Mix n match for your IP and size.
Add to Favourites 
Print this Article
Also Read
