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.

Nameserver can lookup own domains, but anything external get

Discussion in 'Bind / DNS / Nameserver Issues' started by rich2, Oct 6, 2002.

  1. rich2

    rich2 Well-Known Member

    Joined:
    Apr 9, 2002
    Messages:
    64
    Likes Received:
    0
    Trophy Points:
    6
    Topic says most of it,

    my main nameserver, if i do an nslookup on any of our domains it looks it up fine, if i look up any external domain i get a SERVFAIL

    so in resolved.conf i changed the primary ns to another i know that is working and it looks up fine.. so its definitely the nameserver not being able to lookup outside requests

    anyone have any idea about this, first time i have run into this problem and am quite confused
     
  2. itf

    itf Well-Known Member

    Joined:
    May 9, 2002
    Messages:
    624
    Likes Received:
    0
    Trophy Points:
    16
    [quote:cb825e3a3a][i:cb825e3a3a]Originally posted by rich2[/i:cb825e3a3a]

    Topic says most of it,

    my main nameserver, if i do an nslookup on any of our domains it looks it up fine, if i look up any external domain i get a SERVFAIL

    so in resolved.conf i changed the primary ns to another i know that is working and it looks up fine.. so its definitely the nameserver not being able to lookup outside requests

    anyone have any idea about this, first time i have run into this problem and am quite confused[/quote:cb825e3a3a]
    After making sure about these settings:
    /etc/hosts
    /etc/resolv.conf
    DNS records

    And if you have passed domain propagation period
    And if when you use this command in ssh:

    dig @127.0.0.1 server.domain.com
    And you will see you dns records

    But anyone outside of your server can not access to your nameservers :
    You can check it by:
    dig @your-nameserver-ip server.domain.com
    or
    http://www.dnsreport.com

    The major possible issue is an incorrect firewall setting and usually this is an issue about IPchains because during server installation in red hat you selected firewall without going in details of its settings

    Just stop IPchains by using this command in a root ssh session:
    /etc/rc.d/init.d/ipchains stop

    If it works then you know what is the problem your firewall settings (ipchains in this sample) .
     
  3. bdraco

    bdraco Guest

    You are probably missing the hint zone. Please contact support for help.
     
Loading...

Share This Page