Results 1 to 6 of 6
  1. #1

    complete DNS failure, please help.

    First I would like to say, Ive used this site alot, but ive never registered.
    Shame on me.

    I love this place though, but now I actually need some real help.

    Allow me to present you with the data.

    first we have, uname -a
    Code:
    Linux nsa.nullbytehosting.com 2.6.9-55.plus.c4 #1 Sun May 20 10:11:05 EDT 2007 i686 i686 i386 GNU/Linux
    this is centos4.5 I believe.

    and I have 5 ip addresses.

    208.110.67.101 at eth0:0
    208.110.67.114 at eth0:1
    208.110.67.115 at eth0:2
    208.110.67.116 at eth0:3
    208.110.67.117 at eth0:4




    my problem.

    I cannot seem to get my dns working properly.

    I am pointing my domain of nullbytehosting.com to ns1.nullbytehosting.com and ns2.nullbytehosting.com and of course , iuse godaddy, and ive configured that part properly.

    Ive recently stopped using any control panel software, and started using ssh only.


    I can access ns1 and ns2 . nullbytehosting.com just fine.

    www. or just plain old nullbytehosting.com and its a no go.

    allow me to show you my files.



    /etc/resolv.conf
    Code:
    search nullbytehosting.com
    nameserver 208.110.67.101
    nameserver 208.110.67.114
    /var/named/chroot/etc/named.conf
    Code:
    //
    // named.conf for Red Hat caching-nameserver
    //
    include "/etc/rndc.key";
    
    controls {
        inet 127.0.0.1 allow { localhost; } keys { "rndckey"; };
    };
    
    options {
        directory "/var/named";
        dump-file "/var/named/data/cache_dump.db";
            statistics-file "/var/named/data/named_stats.txt";
        recursion no;
        /*
         * If there is a firewall between you and nameservers you want
         * to talk to, you might need to uncomment the query-source
         * directive below.  Previous versions of BIND always asked
         * questions using port 53, but BIND 8.1 uses an unprivileged
         * port by default.
         */
        query-source address * port 53;
        multiple-cnames yes;
        fetch-glue yes;
    };
    
    //
    // a caching only nameserver config
    //
    controls {
        inet 127.0.0.1 allow { localhost; } keys { rndckey; };
    };
    
    zone "." IN {
        type hint;
        file "/var/named/named.ca";
    };
    
    zone "localdomain" IN {
        type master;
        file "/var/named/localdomain.zone";
        allow-update { none; };
    };
    
    zone "localhost" IN {
        type master;
        file "/var/named/localhost.zone";
        allow-update { none; };
    };
    
    zone "0.0.127.in-addr.arpa" IN {
        type master;
        file "/var/named/named.local";
        allow-update { none; };
    };
    
    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 {
            type master;
        file "/var/named/named.ip6.local";
        allow-update { none; };
    };
    
    zone "255.in-addr.arpa" IN {
        type master;
        file "/var/named/named.broadcast";
        allow-update { none; };
    };
    
    zone "0.in-addr.arpa" IN {
        type master;
        file "/var/named/named.zero";
        allow-update { none; };
    };
    
    zone "nsa.nullbytehosting.com" {
        type master;
        file "/var/named/nsa.nullbytehosting.com.db";
    };
    
    zone "nullbytehosting.com" {
        type master;
        file "/var/named/nullbytehosting.com.db";
    };
    zone "enigmagroup.org" {
        type master;
        file "/var/named/enigmagroup.org.db";
    };
    zone "2020code.com" {
        type master;
        file "/var/named/2020code.com.db";
    };
    zone "megansblog.info" {
        type master;
        file "/var/named/megansblog.info.db";
    };
    
    logging {
        };
    view test {
        };
    /var/named/nsa.nullbytehosting.com.db
    Code:
    $TTL 14400
    @       86400   IN      SOA     ns1.nullbytehosting.com.        nullbytehosting.gmail.com.      (
                                            2007031502
                                            86400
                                            7200
                                            3600000
                                            86400
                                            )
    
    ns1.nullbytehosting.com.        14400  IN       A       208.110.67.101
    ns2.nullbytehosting.com.        14400  IN       A       208.110.67.114
    mail.nullbytehosting.com.       14400   IN      A       208.110.67.101
    nsa.nullbytehosting.com.        14400   IN      A       208.110.67.101
    ftp.nullbytehosting.com.        14400   IN      A       208.110.67.101
    www.nullbytehosting.com.        14400   IN      CNAME   nullbytehosting.com.
    test.nullbytehosting.com.       14400   IN      CNAME   nullbytehosting.com.
    nsa.nullbytehosting.com.        14400   IN      MX 0    mail.nullbytehosting.com.
    nsa.nullbytehosting.com.        14400   IN      NS      ns1.nullbytehosting.com.
    nsa.nullbytehosting.com.        14400   IN      NS      ns2.nullbytehosting.com.
    nsa.nullbytehosting.com.        14400   IN      A       208.110.67.101
    /var/named/nullbytehosting.com.db
    Code:
    $TTL 14400    nullbytehosting.com 14440    IN    SOA    ns1.nullbytehosting.com.    psychomarine.gmail.com.    (
                        2007031601
                        86400
                        7200
                        3600000
                        86400
                        )
    ns1                 14400  IN        A      208.110.67.101
    ns2                14400  IN      A      208.110.67.114
    mail                14400    IN    A    208.110.67.101
    ftp                14400    IN    A      208.110.67.101
    www                14400    IN    CNAME    nullbytehosting.com.
    nullbytehosting.com.     14400     IN     MX 0     mail.nullbytehosting.com.
    nullbytehosting.com.     14400     IN     NS     ns1.nullbytehosting.com.
    nullbytehosting.com.     14400     IN     NS     ns2.nullbytehosting.com.
    nullbytehosting.com.     14400     IN     A     208.110.67.101
    /var/named/named.local
    Code:
    $TTL    86400
    @       IN      SOA     localhost. root.localhost.  (
                                          1997022700 ; Serial
                                          28800      ; Refresh
                                          14400      ; Retry
                                          3600000    ; Expire
                                          86400 )    ; Minimum
                  IN      NS      localhost.
    
    1       IN      PTR     localhost.
    /var/named/named.zero
    Code:
    $TTL    86400
    @               IN SOA  localhost       root (
                                            42              ; serial (d. adams)
                                            3H              ; refresh
                                            15M             ; retry
                                            1W              ; expiry
                                            1D )            ; minimum
        IN    NS    localhost
    /var/named/localdomain.zone
    Code:
    $TTL    86400
    @        IN SOA    localhost root (
                        42        ; serial (d. adams)
                        5M        ; refresh
                        5M        ; retry
                        1W        ; expiry
                        1D )        ; minimum
                IN NS        localhost
    localhost    IN A        127.0.0.1
    /var/named/named.broadcast
    Code:
    $TTL    86400
    @               IN SOA  localhost       root (
                                            42              ; serial (d. adams)
                                            3H              ; refresh
                                            15M             ; retry
                                            1W              ; expiry
                                            1D )            ; minimum
        IN    NS    localhost

    and finally, here is a list of the files in the /var/named directory.

    Code:
    /slaves
    /chroot
    /data
    
    named.broadcast
    named.zero
    localdomain.zone
    named.ca
    localhost.zone
    named.ip6.local
    named.local
    
    nsa.nullbytehosting.com.db
    nullbytehosting.com.db
    can someone please inform me of why this isnt allowing me to see nullbytehosting.com www.nullbytehosting.com or any sites I point to ns1.nullbytehosting.com or ns2.nullbytehosting.com

    clearly accessing
    ns1.nullbytehosting.com
    ns2.nullbytehosting.com

    shows the default page I intend to see, however
    nullbytehosting.com
    www.nullbytehosting.com
    or anyhting like that doesnt exist.

    A lookup on the dns tools website, shows alot of errors , that google isnt much help with. everyone has their own way, and none seem to put it all together and work properly.

    thanks for any help anyone can provide.

    feel free to ask about seeing any other files.

    thanks.

  2. #2
    Have a look at this :http://www.dnsstuff.com/tools/dnsrep...ytehosting.com

    could help you resolve this , there are some errors in your domain dns entries .

  3. #3
    Join Date
    Feb 2006
    Location
    Melbourne, Australia
    Posts
    141
    Yes, shame on you for not registering =p

    But yes, you have provided more than enough information so I'm sure the general public of WHT will thank you for that, as with this amount of information we can properly diagnose the issue, having not read over any of your configuration files as I'm in a hurry is to check out the log files! - named logs standard messages to the syslog daemon, which places them in /var/log/messages, so to a quick tail (tail -n 100 /var/log/messages) and you should see the errors in there if any.

    That should indeed help you, if not chuck up the messages log into a public viewable directory and post the link and we'll go from there.
    Dymestry Interactive | Australian Co-Location - Dymestry.com
    Fully Managed Dedicated Servers And Co-Location (Sydney & Melbourne)

  4. #4
    ok, thanks for the replies.

    I changed a few things, a couple of double entries, etc... and this is the error messages I get from the logs,

    keep in mind, I deleted all logs, then `service named stop` then `service named start`



    Code:
    Sep  2 12:39:07 nsa named[2833]: shutting down: flushing changes
    Sep  2 12:39:07 nsa named[2833]: stopping command channel on 127.0.0.1#953
    Sep  2 12:39:07 nsa named[2833]: no longer listening on 127.0.0.1#53
    Sep  2 12:39:07 nsa named[2833]: no longer listening on 208.110.67.101#53
    Sep  2 12:39:07 nsa named[2833]: no longer listening on 208.110.67.114#53
    Sep  2 12:39:07 nsa named[2833]: no longer listening on 208.110.67.115#53
    Sep  2 12:39:07 nsa named[2833]: no longer listening on 208.110.67.116#53
    Sep  2 12:39:07 nsa named[2833]: no longer listening on 208.110.67.117#53
    Sep  2 12:39:07 nsa named[2833]: no longer listening on 208.110.67.118#53
    Sep  2 12:39:07 nsa named[2833]: exiting
    Sep  2 12:39:07 nsa named:  succeeded
    Sep  2 12:39:13 nsa named[9984]: starting BIND 9.2.4 -u named -t /var/named/chroot
    Sep  2 12:39:13 nsa named[9984]: using 1 CPU
    Sep  2 12:39:13 nsa named[9984]: loading configuration from '/etc/named.conf'
    Sep  2 12:39:13 nsa named[9984]: listening on IPv4 interface lo, 127.0.0.1#53
    Sep  2 12:39:13 nsa named[9984]: listening on IPv4 interface eth0, 208.110.67.101#53
    Sep  2 12:39:13 nsa named[9984]: listening on IPv4 interface eth0:1, 208.110.67.114#53
    Sep  2 12:39:13 nsa named[9984]: listening on IPv4 interface eth0:2, 208.110.67.115#53
    Sep  2 12:39:13 nsa named[9984]: listening on IPv4 interface eth0:3, 208.110.67.116#53
    Sep  2 12:39:13 nsa named[9984]: listening on IPv4 interface eth0:4, 208.110.67.117#53
    Sep  2 12:39:13 nsa named[9984]: listening on IPv4 interface eth0:5, 208.110.67.118#53
    Sep  2 12:39:13 nsa named[9984]: command channel listening on 127.0.0.1#953
    Sep  2 12:39:13 nsa named[9984]: zone 0.in-addr.arpa/IN: loaded serial 42
    Sep  2 12:39:13 nsa named[9984]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
    Sep  2 12:39:13 nsa named[9984]: zone 255.in-addr.arpa/IN: loaded serial 42
    Sep  2 12:39:13 nsa named[9984]: 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: loaded serial 1997022700
    Sep  2 12:39:13 nsa named[9984]: zone 2020code.com/IN: loading master file /var/named/2020code.com.db: file not found
    Sep  2 12:39:13 nsa named[9984]: /var/named/nullbytehosting.com.db:1: no TTL specified; zone rejected
    Sep  2 12:39:13 nsa named[9984]: zone nullbytehosting.com/IN: loading master file /var/named/nullbytehosting.com.db: no ttl
    Sep  2 12:39:13 nsa named[9984]: zone nsa.nullbytehosting.com/IN: loading master file /var/named/nsa.nullbytehosting.com.db: file not found
    Sep  2 12:39:13 nsa named[9984]: zone megansblog.info/IN: loading master file /var/named/megansblog.info.db: file not found
    Sep  2 12:39:13 nsa named[9984]: zone localdomain/IN: loaded serial 42
    Sep  2 12:39:13 nsa named[9984]: zone localhost/IN: loaded serial 42
    Sep  2 12:39:13 nsa named[9984]: zone egv4.org/IN: loading master file /var/named/egv4.org.db: file not found
    Sep  2 12:39:13 nsa named[9984]: zone enigmagroup.org/IN: loading master file /var/named/enigmagroup.org.db: file not found
    Sep  2 12:39:13 nsa named: named startup succeeded
    Sep  2 12:39:13 nsa named[9984]: running

    the files are there, so i dont understand why it cant find them, and this no ttl message is very strange, because look here, nullbytehosting.com.db

    Code:
    $TTL 14440
    @    14440    IN    SOA    ns1.nullbytehosting.com.    psychomarine.gmail.com.
    (
    2007031601    
    86400    
    7200    
    3600000
    86400
    )
    
    ns1                     14400   IN      A      208.110.67.101
    ns2                     14400    IN      A      208.110.67.114
    nsa                     14440    IN      A    208.110.67.101
    ftp                      14400    IN      A     208.110.67.101
    mail                    14400    IN    CNAME    208.110.67.101
    www                  14400    IN    CNAME    nullbytehosting.com.
    nullbytehosting.com.         14400     IN     MX 0     nullbytehosting.com.
    localhost.nullbytehosting.com.    14440     IN     A     127.0.0.1
    nullbytehosting.com.         14400     IN     A     208.110.67.101
    nullbytehosting.com.         14400     IN     NS     ns1.nullbytehosting.com.
    nullbytehosting.com.         14400     IN     NS     ns2.nullbytehosting.com.

  5. #5
    Make sure named has permission to read the files wherever you're putting them.

  6. #6
    ok, I made a discovery.

    since this is a caching nameserver, I cal only assume that the records that are in

    /var/named

    are not the ones it reads.

    so I put them in

    /var/named/chroot/var/named

    and at least half the errors on a dns lookup are gone, and now it seems to be at least accepting it, when typing in a domain.

    theres some new issues, but I think thats more specific ot another thread. thanks everyone for all their information.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •