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.

cannot resolve external dns names

Discussion in 'Bind / DNS / Nameserver Issues' started by crackdom, May 15, 2006.

  1. crackdom

    crackdom Registered

    Joined:
    Jun 19, 2005
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    I am having really problems with a new dedicated server that we have just purchased. It has its own name servers running.

    WHM 10.8.0 cPanel 10.8.2-R83
    Trustix 2.2 i686 - WHM X v3.1.0

    The problem is that the server can not resolve any external domain names. This cause lots of problems like not being able to use any cpanel updates.

    It can also recieve email but it can sent them, unrouteable mail domain "hotmail.com"

    example with a ping

    [~]# ping yahoo.com
    ping: unknown host yahoo.com


    but if I ping with the ip address everything works correctly, so it can definatly get to the outside world.

    dig has the same problem. If I dig a domain hosted on the server, i get

    [~]# dig biz-training.com

    ; <<>> DiG 9.3.2 <<>> biz-training.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35877
    ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;biz-training.com. IN A

    ;; ANSWER SECTION:
    biz-training.com. 14400 IN A 198.87.3.205

    ;; AUTHORITY SECTION:
    biz-training.com. 86400 IN NS 198.87.3.204.
    biz-training.com. 86400 IN NS 198.87.3.203.

    ;; Query time: 2 msec
    ;; SERVER: 198.87.3.203#53(198.87.3.203)
    ;; WHEN: Mon May 15 17:22:32 2006
    ;; MSG SIZE rcvd: 102


    which is as expected, but if i dig an external domains, i get

    [~]# dig google.com

    ; <<>> DiG 9.3.2 <<>> google.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19617
    ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 13

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

    ;; AUTHORITY SECTION:
    . 517986 IN NS L.ROOT-SERVERS.NET.
    . 517986 IN NS M.ROOT-SERVERS.NET.
    . 517986 IN NS A.ROOT-SERVERS.NET.
    . 517986 IN NS B.ROOT-SERVERS.NET.
    . 517986 IN NS C.ROOT-SERVERS.NET.
    . 517986 IN NS D.ROOT-SERVERS.NET.
    . 517986 IN NS E.ROOT-SERVERS.NET.
    . 517986 IN NS F.ROOT-SERVERS.NET.
    . 517986 IN NS G.ROOT-SERVERS.NET.
    . 517986 IN NS H.ROOT-SERVERS.NET.
    . 517986 IN NS I.ROOT-SERVERS.NET.
    . 517986 IN NS J.ROOT-SERVERS.NET.
    . 517986 IN NS K.ROOT-SERVERS.NET.

    ;; ADDITIONAL SECTION:
    A.ROOT-SERVERS.NET. 604386 IN A 198.41.0.4
    B.ROOT-SERVERS.NET. 604386 IN A 192.228.79.201
    C.ROOT-SERVERS.NET. 604386 IN A 192.33.4.12
    D.ROOT-SERVERS.NET. 604386 IN A 128.8.10.90
    E.ROOT-SERVERS.NET. 604386 IN A 192.203.230.10
    F.ROOT-SERVERS.NET. 604386 IN A 192.5.5.241
    G.ROOT-SERVERS.NET. 604386 IN A 192.112.36.4
    H.ROOT-SERVERS.NET. 604386 IN A 128.63.2.53
    I.ROOT-SERVERS.NET. 604386 IN A 192.36.148.17
    J.ROOT-SERVERS.NET. 604386 IN A 192.58.128.30
    K.ROOT-SERVERS.NET. 604386 IN A 193.0.14.129
    L.ROOT-SERVERS.NET. 604386 IN A 198.32.64.12
    M.ROOT-SERVERS.NET. 604386 IN A 202.12.27.33

    ;; Query time: 3 msec
    ;; SERVER: xx.xx.xx.xx#53(xx.xx.xx.xx)
    ;; WHEN: Mon May 15 17:20:39 2006
    ;; MSG SIZE rcvd: 447


    I though this would be a resolv.conf issue but that appers to be correct.

    nameserver 198.87.3.203
    nameserver 198.87.3.204

    I have run out of ideas to try. There are not unsual line is in the messages log.

    Any one got any ideas?

    Thank you
     
  2. aby

    aby Well-Known Member

    Joined:
    May 31, 2005
    Messages:
    638
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    India
    Try allowing recursion in named.conf to see if that helps.
     
  3. crackdom

    crackdom Registered

    Joined:
    Jun 19, 2005
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    That fixed it

    Thank you for that it is all working fine now. It is always the simple things that I miss.
     
Loading...

Share This Page