The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

[ipcheck] Problem with DNS setup on Arecord.domain.com

Discussion in 'Bind / DNS / Nameserver Issues' started by enahs, Oct 1, 2013.

  1. enahs

    enahs Member

    Joined:
    Apr 1, 2013
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    Hello,

    I am not completely new to cPanel but this new VPS is only the second one I have setup so with regards to setup I do not have much experience. This is new VPS which we are migrating to from an old VPS at another VPS host. We are now using Microsoft Azure. They provide us with a 100.67.x.x IP address for your VPS to use which is also what is assigned to your hosting accounts. However, this is not the outside IP address used for access to WHM/cPanel and the hosting accounts. It is a completely different IP on a different subnet (I'll just call it the outside IP address). WIth that said I am also not making the VPS the DNS server for these hosting accounts. I will leave their DNS records hosted at their current locations (GoDaddy, Network Solutions...etc). I am receiving an alert with the subject of "[ipcheck] Problem with DNS setup on Arecord.domain.com". The actual hostname is not that, I just changed it to provide anonymity. The actual message is stating that the Arecord.domain.com is pointing to the outside IP address but it should be pointing to the 100.67.x.x address. If I did that I would not be able to utilize my VPS using my FQDN of Arecord.domain.com. Also, I have the "hosts" file (inside the VPS) pointing to itself with the 100.67.x.x address. My last VPS only had an outside IP address assigned to it so I did not have this confusion. This one apparently has NAT'ing setup. The body of the warning message is pasted at the bottom of this post.

    So my questions:

    Can this warning be safely ignored?
    Should I be setting the primary DNS server in the resolv.conf as the VPS' own IP address then use an outside DNS server for secondary and tertiary?

    Thanks in advance for any assistance.


    IMPORTANT: Do not ignore this email.

    The hostname (Arecord.domain.com) resolves to 23.x.x.x. It should resolve to 100.67.x.x. Please be sure that the contents of /etc/hosts are configured correctly, and also that there is a correct 'A' entry for the domain in the zone file.

    Some or all of these problems can be caused by /etc/resolv.conf being setup incorrectly. Please check that file if you believe everything else is correct.

    You may be able to automatically correct this problem by using the 'Add an A entry for your hostname' option under 'Dns Functions' in your Web Host Manager.
     
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,709
    Likes Received:
    658
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hello :)

    You can safely ignore that warning message if the hostname already points to the IP address that you need it to. You should not use the server's IP address as the resolver in your /etc/resolv.conf file. There is an internal case open to address the issue of this warning message when using a NAT environment. For reference, that case number is 56083.

    Thank you.
     
  3. enahs

    enahs Member

    Joined:
    Apr 1, 2013
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    Thank you, I found out later that a NAT'd scenario is not supported by cPanel yet and is slated to be supported on the 11.4 release. Had no idea until we moved the VPS to MS Azure. I also heard that Azure is not a supported virtual environment. That is unfortunate because it is running perfectly for us other than them not allowing us to have more than one static public IP address. That is where I am getting used to SNI....that's another story... :) Looking forward to the official release of 11.4 for this reason alone.
     
Loading...

Share This Page