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.

Problems Nameserver IP sharing and more

Discussion in 'Bind / DNS / Nameserver Issues' started by webcloaker, Oct 9, 2007.

  1. webcloaker

    webcloaker Member

    Joined:
    Jan 5, 2006
    Messages:
    15
    Likes Received:
    0
    Trophy Points:
    1
    Okay here is my problem,

    I have setup my nameservers,

    They both use the same IP address, which is also the server ip

    I have registered them with godaddy

    I have enabled IP sharing for nameservers.

    When I restart bind this is the output
    Code:
    named started ok Oct 9 20:41:34 fast named[3186]: client 66.90.104.102#32966: view localhost_resolver: received notify for zone 'filestorageservices.com': not authoritative Oct 9 20:55:36 fast named[3186]: shutting down: flushing changes Oct 9 20:55:36 fast named[3186]: stopping command channel on 127.0.0.1#953 Oct 9 20:55:36 fast named[3186]: no longer listening on 127.0.0.1#53 Oct 9 20:55:36 fast named[3186]: no longer listening on 66.90.104.102#53 Oct 9 20:55:36 fast named[3186]: exiting Oct 9 20:55:36 fast named[3370]: starting BIND 9.3.3rc2 -u named Oct 9 20:55:36 fast named[3370]: found 2 CPUs, using 2 worker threads Oct 9 20:55:36 fast named[3370]: loading configuration from '/etc/named.conf' Oct 9 20:55:36 fast named[3370]: listening on IPv4 interface lo, 127.0.0.1#53 Oct 9 20:55:36 fast named[3370]: listening on IPv4 interface eth0, 66.90.104.102#53 Oct 9 20:55:36 fast named[3370]: command channel listening on 127.0.0.1#953 Oct 9 20:55:36 fast named[3370]: zone 0.in-addr.arpa/IN/localhost_resolver: loaded serial 42 Oct 9 20:55:36 fast named[3370]: zone 0.0.127.in-addr.arpa/IN/localhost_resolver: loaded serial 1997022700 Oct 9 20:55:36 fast named[3370]: zone 255.in-addr.arpa/IN/localhost_resolver: loaded serial 42 Oct 9 20:55:36 fast named[3370]: zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN/localhost_resolver: loaded serial 1997022700 Oct 9 20:55:36 fast named[3370]: zone localdomain/IN/localhost_resolver: loaded serial 42 Oct 9 20:55:36 fast named[3370]: zone localhost/IN/localhost_resolver: loaded serial 42 Oct 9 20:55:36 fast named[3370]: zone filestorageservices.com/IN/internal: loaded serial 2007101004 Oct 9 20:55:36 fast named[3370]: zone filestorageservices.com/IN/external: loaded serial 2007101004 Oct 9 20:55:36 fast named[3370]: running Oct 9 20:55:36 fast named[3370]: zone filestorageservices.com/IN/internal: sending notifies (serial 2007101004) Oct 9 20:55:36 fast named[3370]: zone filestorageservices.com/IN/external: sending notifies (serial 2007101004) Oct 9 20:55:36 fast named[3370]: client 66.90.104.102#32967: view localhost_resolver: received notify for zone 'filestorageservices.com': not authoritative

    Filestorageservices.com is viewable from the web, even though bind is spitting out these errors,

    Here is my current named.conf

    include "/etc/rndc.key";

    controls {
    inet 127.0.0.1 allow { localhost; } keys { "rndc-key"; };
    };


    options
    {
    /* make named use port 53 for the source of all queries, to allow
    * firewalls to block all ports except 53:
    */
    query-source port 53;

    // Put files that named is allowed to write in the data/ directory:
    directory "/var/named"; // the default
    dump-file "data/cache_dump.db";
    statistics-file "data/named_stats.txt";
    memstatistics-file "data/named_mem_stats.txt";
    };

    logging
    {
    /* If you want to enable debugging, eg. using the 'rndc trace' command,
    * named will try to write the 'named.run' file in the $directory (/var/named).
    * By default, SELinux policy does not allow named to modify the /var/named directory,
    * so put the default debug log file in data/ :
    */
    channel default_debug {
    file "data/named.run";
    severity dynamic;
    };
    };


    // All BIND 9 zones are in a "view", which allow different zones to be served
    // to different types of client addresses, and for options to be set for groups
    // of zones.
    //
    // By default, if named.conf contains no "view" clauses, all zones are in the
    // "default" view, which matches all clients.
    //
    // If named.conf contains any "view" clause, then all zones MUST be in a view;
    // so it is recommended to start off using views to avoid having to restructure
    // your configuration files in the future.

    view "localhost_resolver"
    {
    /* This view sets up named to be a localhost resolver ( caching only nameserver ).
    * If all you want is a caching-only nameserver, then you need only define this view:
    */
    match-clients { localhost; };
    match-destinations { localhost; };
    recursion yes;

    zone "." IN {
    type hint;
    file "/var/named/named.ca";
    };

    /* these are zones that contain definitions for all the localhost
    * names and addresses, as recommended in RFC1912 - these names should
    * ONLY be served to localhost clients:
    */
    include "/var/named/named.rfc1912.zones";
    };

    view "internal"
    {
    /* This view will contain zones you want to serve only to "internal" clients
    that connect via your directly attached LAN interfaces - "localnets" .
    */
    match-clients { localnets; };
    match-destinations { localnets; };
    recursion yes;

    zone "." IN {
    type hint;
    file "/var/named/named.ca";
    };

    // include "/var/named/named.rfc1912.zones";
    // you should not serve your rfc1912 names to non-localhost clients.

    // These are your "authoritative" internal zones, and would probably
    // also be included in the "localhost_resolver" view above :

    zone "filestorageservices.com" {
    type master;
    file "/var/named/filestorageservices.com.db";
    };
    };

    view "external"
    {
    /* This view will contain zones you want to serve only to "external" clients
    * that have addresses that are not on your directly attached LAN interface subnets:
    */

    recursion no;
    // you'd probably want to deny recursion to external clients, so you don't
    // end up providing free DNS service to all takers

    // all views must contain the root hints zone:
    zone "." IN {
    type hint;
    file "/var/named/named.ca";
    };

    // These are your "authoritative" external zones, and would probably
    // contain entries for just your web and mail servers:

    // BEGIN external zone entries

    zone "filestorageservices.com" {
    type master;
    file "/var/named/filestorageservices.com.db";
    };
    };


    Can anyone here please help me out? Im at the end of my wits:confused:
     
  2. nayagi

    nayagi Member

    Joined:
    Jan 16, 2008
    Messages:
    19
    Likes Received:
    0
    Trophy Points:
    1
    Domain Not Resolving - Need immediate help

    Hi

    I haved attached the actual stuff....

    /etc/named.conf

    include "/etc/rndc.key";

    controls {
    inet 127.0.0.1 allow { localhost; } keys { "rndc-key"; };
    };

    options
    {

    //query-source address * port 53;
    listen-on { 69.10.44.24; };
    directory "/var/named"; // the default
    dump-file "data/cache_dump.db";
    statistics-file "data/named_stats.txt";
    memstatistics-file "data/named_mem_stats.txt";
    };

    logging
    {
    channel default_debug {
    file "data/named.run";
    severity dynamic;
    };
    };

    view "localhost_resolver"
    {
    match-clients { localhost; };
    match-destinations { localhost; };
    recursion yes;

    zone "." IN {
    type hint;
    file "/var/named/named.ca";
    };
    include "/var/named/named.rfc1912.zones";
    };

    view "internal"
    {
    match-clients { localnets; };
    match-destinations { localnets; };
    recursion yes;

    zone "." IN {
    type hint;
    file "/var/named/named.ca";
    };
    zone "autoglassdelivered.com" {
    type master;
    file "/var/named/autoglassdelivered.com.db";
    allow-query { any; };
    allow-update { localhost; };
    };
    };
    view "external"
    {
    match-clients { !localnets; !localhost; };
    match-destinations { !localnets; !localhost; };

    recursion no;


    zone "autoglassdelivered.com" {
    type master;
    file "/var/named/autoglassdelivered.com.db";
    allow-query { any; };
    allow-update { localhost; };
    };
    };

    /etc/resolv.conf

    search server.4wtech.com
    nameserver 69.10.44.24

    /var/named/autoglassdelivered.com.db

    ; Modified by Web Host Manager
    ; Zone File for autoglassdelivered.com
    $TTL 14400
    @ 86400 IN SOA ns1.4wtech.com. admin.4wtech.com. (
    2008012418
    86400
    7200
    3600000
    86400
    )
    autoglassdelivered.com. 86400 IN NS ns1.4wtech.com.
    autoglassdelivered.com. 86400 IN NS ns2.4wtech.com.
    autoglassdelivered.com. 14400 IN A 69.10.44.28
    www.autoglassdelivered.com. 14400 IN A 69.10.44.28
    autoglassdelivered.com. 14400 IN MX 5 smtp.secureserver.net.
    autoglassdelivered.com. 14400 IN MX 10 mailstore1.secureserver.net.
    ns1 14400 IN A 69.10.44.24
    ns2 14400 IN A 69.10.44.24

    I found these messages in /var/log/messages which seems to be the issue to be solved

    Feb 7 01:03:09 server named[19484]: client 69.10.44.24#34913: view localhost_resolver: received notify for zone '4wtech.com': not authoritative
    Feb 7 01:03:22 server named[19484]: lame server resolving 'autoglassdelivered.com' (in 'autoglassdelivered.com'?): 69.10.44.24#53

    When pinging ns1.4wtech.com from inside SSH(putty) and outside ,it is resolving.. Similarly autoglassdelivered.com is not resloving correct ip both inside and outside...

    I have compared my config files and found they are more or less the same...Sitting in this issues for more than two days found many resources but in vain... I need an immediate help...

    Thanks in advance...
     
  3. BlueZebra

    BlueZebra Well-Known Member

    Joined:
    Apr 27, 2006
    Messages:
    48
    Likes Received:
    0
    Trophy Points:
    6
    Hi,

    autoglassdelivered.com is registered with NS1.4WTECH.COM & NS2.4WTECH.COM

    --------------------o
    -sh-2.05b$ host autoglassdelivered.com
    Host autoglassdelivered.com not found: 5(REFUSED)
    --------------------o
    -sh-2.05b$ dig @NS1.4WTECH.COM autoglassdelivered.com

    ;; QUESTION SECTION:
    ;autoglassdelivered.com. IN A
    --------------------o

    -sh-2.05b$ dig @NS2.4WTECH.COM autoglassdelivered.com
    dig: Couldn't find server 'NS2.4WTECH.COM': Name or service not known
    --------------------o

    Please check the setting of 4WTECH.COM. and make sure NS1.4WTECH.COM and NS2.4WTECH.COM are resolving fine

    --------------------o
    -sh-2.05b$ host 4WTECH.COM
    Host 4WTECH.COM not found: 5(REFUSED)
    --------------------o
    -sh-2.05b$ host NS1.4WTECH.COM
    NS1.4WTECH.COM has address 69.10.44.24

    -sh-2.05b$ host NS2.4WTECH.COM
    Host NS2.4WTECH.COM not found: 5(REFUSED)
    --------------------o
     
  4. nayagi

    nayagi Member

    Joined:
    Jan 16, 2008
    Messages:
    19
    Likes Received:
    0
    Trophy Points:
    1
    Hi I am having a domain causing problems.
    "rmtforum.com". I have given the primary nameservers as ns1.4wtech.com and ns2.4wtech.com

    But this domain is not pinging and showing errors like

    SOA Record
    Primary Name Server ns1.4wtech.com
    DNS Host Master Unknown
    Secondary Refresh Unknown
    Secondary Retry Unknown
    Secondary Expire Unknown
    Default Record Cache Time Unknown
    Serial Number Unknown
    ns.4wtech.com Name server
    Name ns.4wtech.com
    IP Address 69.10.44.24
    Location United States
    Response Time 40ms

    Name Server Info
    Info Type*** Message***
    Error The name server did not return any SOA records. This could indicate a 'lame' nameserver - one that is listed as authoratative, but does not return any information for the zone.
    Information The name server did not return any records after our AXFR request. This is quite normal.
    Information This name server returns the following DNS records for 'rmtforum.com': ''

    But all other domains with this name server are working well. Please help me to fix this isssue

    Thanks in advance
     
Loading...

Share This Page