Skip to main content

Reverse DNS problem

chris0147
Hi all, I need some help with Reverse DNS as I have got a problem with it. I have setup rDNS on my hosting provider which I use rdns1.mydomain.com and I have a server hostname which it is gateway1.mydomain.com. I want to use both different name because of the email providers that want to see both different names so my email would go to inbox. When I open on the Email Deliverability software through in the cpanel, I can see this: - Removed - Can you please advice me with what I need to do? How I can match with the rDNS? Do I need to change the server hostname to match with the rDNS or what? I want to use smtp513.mydomain.com to send the email and I want to use gateway1.mydomain.com to get access to whm and cpanel. I am not sure what I need to do so I need your help with this. Any advice would be much appreciated. Thanks in advance.

Comments

14 comments

Date Votes
  • keat63
    I don't know enough about this to offer anything concrete, but when I set my server up, I had to contact my data centre and ask them to configure RDNS at thier end. This was nothing that I had any control over.
    0
  • chris0147
    Oh right, well I want to use two different IPs to point it in PTR in a single hostname but I cant now because the PTR will only allow you to setup with one IP in a single hostname. I want to setup two different smtp addresses that come with two different IPs, e.g: 106.x.xx.59 and 106.xxx.xxx.202 as the 106.x.xx.59 will be using for smtp513 and 106.xxx.xxx.202 will be using for smtp516 as a backup. The other way I could do is buy another VPS to transfer the IP and point it to PTR that match with the hostname. I am sure someone on here might know better than I do?
    0
  • uk01
    **removed** turned out to be a sporadic issue with a second ip on one server
    0
  • cPanelLauren
    Hello, The documentation here should be useful: How to Configure Reverse DNS for BIND in WHM - cPanel Knowledge Base - cPanel Documentation I do also want to point out that the rDNS should resolve back to the hostname of the server not a domain name.
    0
  • uk01
    Hello, The documentation here should be useful:
    0
  • cPanelLauren
    Hi @uk01 What was the PTR set to on the secondary IP address? It should function the same.
    0
  • chris0147
    Hello, The documentation here should be useful:
    0
  • cPanelLauren
    Hi @chris0147 First, are you sure that your provider delegates access to update rDNS to you? It may be that you're not able to add it. Based on this output it looks like it's not coming up - a PTR record is always going to list the IP address backwards.
    0
  • chris0147
    Hi @chris0147 First, are you sure that your provider delegates access to update rDNS to you? It may be that you're not able to add it. Based on this output it looks like it's not coming up - a PTR record is always going to list the IP address backwards.

    @
    0
  • uk01
    Hi @uk01 What was the PTR set to on the secondary IP address? It should function the same.

    Hi the reseller used to use the secondary ip but now uses the primary as we had to switch mainip due to a Cpanel license issue after uninstalling Cloudlinux. Now Cpanel/main ip > ip 1 Reseller > all domains are ip 1 Other accounts > ip 2 hostname.ourdomain.com > ip 2 RDNS for ip 2 > hostname.ourdomain.com RDNS for ip 1 > resellerdomain.com If the RDNS for ip 1 is not the reseller domain we get this message: The system sends "resellerdomain.com""s outgoing email from the "**ip 1**" IP address. The only PTR value for this IP address must be "resellerdomain.com". This is the name that this server sends with SMTP"s "HELO" command to send "resellerdomain.com""s outgoing email. 1 unexpected PTR value exists for this IP address:
    • hostname.ourdomain.com
    If we change the hostname to ip 1, same as Cpanel, we get issues with the other domains HELO. Setting the reseller as the RDNS for their ip resolves the issue as luckily we do not share that ip.
    0
  • cPanelLauren
    Hi @uk01 The reseller IP needs to have an A record for the hostname as well. In that instance, the PTR should function without issue. Right now my assumption is the only A record associated with it is the reseller's domain.
    0
  • uk01
    Hi @uk01 The reseller IP needs to have an A record for the hostname as well. In that instance, the PTR should function without issue. Right now my assumption is the only A record associated with it is the reseller's domain.

    so 2 records pointing to the same ip?
    • hostname.ourdomain.com >>> to ip 1
    • hostname.ourdomain.com >>> to ip 2
    I didn't think we should point the same sub domain to 2 ip's
    0
  • cPanelLauren
    All an A record does is map a domain name to an IP address. You can use multiple A records for the same domain, in this instance the hostname. You'd either need to do that to resolve the PTR properly or again, you'd need to use a domain whose A record is already mapped to that IP address. This will not affect domain's that have the same IP address assigned as the Apache VirtualHost manages to the per domain configuration. Thanks!
    0
  • uk01
    All an A record does is map a domain name to an IP address. You can use multiple A records for the same domain, in this instance the hostname. You'd either need to do that to resolve the PTR properly or again, you'd need to use a domain whose A record is already mapped to that IP address. This will not affect domain's that have the same IP address assigned as the Apache VirtualHost manages to the per domain configuration. Thanks!

    @cPanelLauren thanks for that info, that's great. That's why the reseller.com domain works on the RDNS then as that domain points to the the ip. I realise now if I have the hostname pointing to the second ip too, then the hostname will work ok for the RDNS. Cheers
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post