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.

Dns Problem

Discussion in 'Bind / DNS / Nameserver Issues' started by Yard, Apr 1, 2008.

  1. Yard

    Yard Member

    Joined:
    Nov 8, 2002
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    1
    Hi, I have a small problem with my dns, my second server (cpanel dns only) is working fine, but it seem when I upgrade my real cpanel my primary dns stop working fine...

    I'm using my dns for my customer

    when I do dig, from my primary dns I don't get any ip but if I do it from my secondary it work... here the result:

    dig @ns1.xxxxx.com rogers.com

    ; <<>> DiG 9.2.4 <<>> @ns1.xxxxx.com rogers.com
    ; (1 server found)
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43771
    ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 4

    ;; QUESTION SECTION:
    ;rogers.com. IN A

    ;; AUTHORITY SECTION:
    rogers.com. 163844 IN NS NS2.YM.RNC.NET.CABLE.rogers.com.
    rogers.com. 163844 IN NS ns2.wlfdle.RNC.NET.CABLE.rogers.com.
    rogers.com. 163844 IN NS ns3.YM.RNC.NET.CABLE.rogers.com.
    rogers.com. 163844 IN NS ns3.wlfdle.RNC.NET.CABLE.rogers.com.

    ;; ADDITIONAL SECTION:
    NS2.YM.RNC.NET.CABLE.rogers.com. 163844 IN A 24.153.22.142
    ns2.wlfdle.RNC.NET.CABLE.rogers.com. 163844 IN A 24.153.22.14
    ns3.YM.RNC.NET.CABLE.rogers.com. 163844 IN A 64.71.246.156
    ns3.wlfdle.RNC.NET.CABLE.rogers.com. 163844 IN A 64.71.246.28

    ;; Query time: 47 msec
    ;; SERVER: 64.235.222.82#53(xx.xx.xx.xx)
    ;; WHEN: Tue Apr 1 14:52:17 2008
    ;; MSG SIZE rcvd: 188

    dig @ns2.xxxxx.com rogers.com

    ; <<>> DiG 9.2.4 <<>> @ns2.xxxx.com rogers.com
    ; (1 server found)
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26197
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;rogers.com. IN A

    ;; ANSWER SECTION:
    rogers.com. 3500 IN A 207.245.252.27

    ;; AUTHORITY SECTION:
    rogers.com. 86300 IN NS ns2.ym.rnc.net.cable.rogers.com.
    rogers.com. 86300 IN NS ns2.wlfdle.rnc.net.cable.rogers.com.
    rogers.com. 86300 IN NS ns3.ym.rnc.net.cable.rogers.com.
    rogers.com. 86300 IN NS ns3.wlfdle.rnc.net.cable.rogers.com

    ;; Query time: 48 msec
    ;; SERVER: 67.18.210.210#53(xx.xx.xx.xx)
    ;; WHEN: Tue Apr 1 14:52:14 2008
    ;; MSG SIZE rcvd: 140

    the result is almost the same, except I have an answer section from my ns2... did me , or cpanel, messup something into the config?
     
  2. LiNUxG0d

    LiNUxG0d Well-Known Member

    Joined:
    Jun 25, 2003
    Messages:
    206
    Likes Received:
    1
    Trophy Points:
    18
    Location:
    Gatineau, Quebec, Canada
    Hi there,

    Firstly, check the /etc/resolv.conf as that's the DNS servers that `dig` will use to get your responses. If one has different ones than the other, this could be part of the problem. I've seen odd bugs where the DNS resolution for the DNS you're digging it was wrong due to a corrupted zone on the initial lookup. AKA: ns1.xxxxx.com is resolving to a bad IP and not actually your own, because the resolv.conf DNS aren't looking things up properly.

    Secondly, it's important, if you're running a firewall on the local host or DNS, that you allow outbound/inbound traffic on the proper ports. DNS usually operate on 53, UDP.

    Are they both supposed to have identical records? If so, have you tried copying your /var/named/* and /etc/named.conf to the other server?

    I've done this in the past. Same symptoms. One was ok, one wasn't. Refreshed one with the others zones and used the other ones named.conf.

    Fixed it for me. :)

    You never know.
     
Loading...

Share This Page