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 configuration error

Discussion in 'Bind / DNS / Nameserver Issues' started by kylebuttress, Feb 27, 2005.

  1. kylebuttress

    kylebuttress Member

    Joined:
    Feb 15, 2005
    Messages:
    11
    Likes Received:
    0
    Trophy Points:
    1
    Hi all,

    I am have some problems configuring my server with dns.

    I have the server set up and cpanel and whm are working just fine.

    I am trying to configure dns and i am receiving errors when I get a report from www.dnsstuff.com

    I get replies saying that
    Server failure. There's a problem with the DNS server for mydomain.com

    at other times it reporst that No A record exists for that domain.

    though when I dig mydomain.com

    I get an expected result

    My question is this.

    Would this error happen if the NOC where the server is housed has not or does not have the DNS record for my server in there dns file?

    I am at a loss to know or find an answer to this problem I believe my named.conf and zone files are ok but cannot figure out hot to fix this error.


    any help or advice would be really appreciated.

    regards

    Kyle
     
  2. DigitalN

    DigitalN Well-Known Member

    Joined:
    Sep 23, 2004
    Messages:
    420
    Likes Received:
    1
    Trophy Points:
    18
    Have you registered your name servers with your domain name registrar, with the IPs that you have set them up with on your box? and do you have A records for them within the domains dns zone?

    What is your domain name?
     
  3. kylebuttress

    kylebuttress Member

    Joined:
    Feb 15, 2005
    Messages:
    11
    Likes Received:
    0
    Trophy Points:
    1
    Hi.

    I have a domains name

    gchost.com.au registered over a week now and it has nameservers listed as
    ns1.gchost.com.au and
    ns1.zodns.com

    below are my config files

    any help would be unreal

    thanks

    Kyle


    ------------------> Zone File gchost.com.au

    $TTL 3600

    @ IN SOA ns1.gchost.com.au. kyle.ionlinemail.com. (
    2005022801 ; Serial
    10800 ; Refresh
    3600 ; Retry
    604800 ; Expire
    86400 ) ; Minimum TTL

    ; DNS Servers
    IN NS ns1.gchost.com.au.
    IN NS ns1.zodns.com.

    ; MX Record
    @ IN MX 10 mail.gchost.com.au.

    ; Machine Names
    localhost IN A 127.0.0.1
    ns1 IN A 202.144.167.142
    mail IN A 202.144.167.142
    IN A 202.144.167.142
    www IN A 202.144.167.142

    ; Aliases
    ftp IN CNAME gchost.com.au.
    bonobo 14400 IN A 202.144.167.142
    -------------------> END ZONE
    I have a a reverse zone file also

    --------------------> REVERSE ZONE
    $TTL 3600

    167.144.202.in-addr.arpa. IN SOA ns1.gchost.com.au. kyle.ionlinemail.com. (
    5 ; Serial
    10800 ; Refresh
    3600 ; Retry
    604800 ; Expire
    3600 ) ; Minimum

    @ IN NS ns1.gchost.com.au.
    @ IN NS ns1.zodns.com
    142 IN PTR ns1.gchost.com.au.
    142 IN PTR mail.gchost.com.au.
    142 IN PTR gchost.com.au.
    ------------------------> END REVERSE ZONE

    the named.conf is
    ------------------------->
    key "rndc-key" {
    algorithm hmac-md5;
    secret "qppE1JcHkoDhU1o0/mM0/Q==";
    };

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

    // $FreeBSD: src/etc/namedb/named.conf,v 1.15.2.1 2004/09/30 23:36:07 dougb Exp $
    //
    // Refer to the named.conf(5) and named(8) man pages, and the documentation
    // in /usr/share/doc/bind9 for more details.
    //
    // If you are going to set up an authoritative server, make sure you
    // understand the hairy details of how DNS works. Even with
    // simple mistakes, you can break connectivity for affected parties,
    // or cause huge amounts of useless Internet traffic.

    options {
    directory "/etc/namedb";
    pid-file "/var/run/named/pid";
    dump-file "/var/dump/named_dump.db";
    statistics-file "/var/stats/named.stats";

    // If named is being used only as a local resolver, this is a safe default.
    // For named to be accessible to the network, comment this option, specify
    // the proper IP address, or delete this option.
    listen-on { 127.0.0.1; };

    // If you have IPv6 enabled on this system, uncomment this option for
    // use as a local resolver. To give access to the network, specify
    // an IPv6 address, or the keyword "any".
    // listen-on-v6 { ::1; };

    // In addition to the "forwarders" clause, you can force your name
    // server to never initiate queries of its own, but always ask its
    // forwarders only, by enabling the following line:
    //
    // forward only;

    // If you've got a DNS server around at your upstream provider, enter
    // its IP address here, and enable the line below. This will make you
    // benefit from its cache, thus reduce overall DNS traffic in the Internet.
    /*
    forwarders {

    };
    */
    /*
    * 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 versions 8 and later
    * use a pseudo-random unprivileged UDP port by default.
    */
    // query-source address * port 53;
    };

    // If you enable a local name server, don't forget to enter 127.0.0.1
    // first in your /etc/resolv.conf so this server will be queried.
    // Also, make sure to enable it in /etc/rc.conf.

    // RFC 3152

    // RFC 1886 -- deprecated

    // NB: Do not use the IP addresses below, they are faked, and only
    // serve demonstration/documentation purposes!
    //
    // Example slave zone config entries. It can be convenient to become
    // a slave at least for the zone your own domain is in. Ask
    // your network administrator for the IP address of the responsible
    // primary.
    //
    // Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
    // (This is named after the first bytes of the IP address, in reverse
    // order, with ".IN-ADDR.ARPA" appended.)
    //
    // Before starting to set up a primary zone, make sure you fully
    // understand how DNS and BIND works. There are sometimes
    // non-obvious pitfalls. Setting up a slave zone is simpler.
    //
    // NB: Don't blindly enable the examples below. :) Use actual names
    // and addresses instead.

    /*

    */


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

    zone "0.168.192.in-addr.arpa" {
    type slave;
    file "/etc/named/0.168.192.in-addr.arpa";
    masters {
    192.168.1.1;
    };
    };

    zone "167.144.202.in-addr.arpa" IN {
    type master;
    file "/etc/namedb/167.144.202.db";
    allow-update { none; };
    };

    zone "example.com" {
    type slave;
    file "/etc/named/example.com";
    masters {
    192.168.1.1;
    };
    };

    zone "gchost.com" {
    type master;
    file "/etc/namedb/gchost.com.db";
    };

    zone "gchost.com.au" {
    type master;
    file "/etc/namedb/gchost.com.au.db";
    allow-transfer { 66.114.69.151; };
    };
    ------------------------> END NAMED.CONF
     
  4. DigitalN

    DigitalN Well-Known Member

    Joined:
    Sep 23, 2004
    Messages:
    420
    Likes Received:
    1
    Trophy Points:
    18
    Ok thanks, I'll do some tests at your name servers and get back to you .. in a mo.

    Can you just do this

    # rndc reload

    # tail -100 /var/log/messages

    Post the output from messages.
     
  5. kylebuttress

    kylebuttress Member

    Joined:
    Feb 15, 2005
    Messages:
    11
    Likes Received:
    0
    Trophy Points:
    1
    sure thanks for this

    ------> SNIP
    rndc reload
    server reload successful
    bonobo# tail -100 /var/log/messages
    Feb 28 10:34:19 bonobo named[4450]: zone gchost.com.au/IN: loading master file /etc/namedb/gchost.com.au.db: unknown class/type
    Feb 28 10:34:19 bonobo named[4450]: zone 1.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.INT/IN: loading master file /etc/named/localhost-v6.rev: file not found
    Feb 28 10:35:15 bonobo named[4450]: zone 0.0.127.IN-ADDR.ARPA/IN: loading master file /etc/named/localhost.rev: file not found
    Feb 28 10:35:15 bonobo named[4450]: zone 1.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: loading master file /etc/named/localhost-v6.rev: file not found
    Feb 28 10:35:15 bonobo named[4450]: dns_master_load: /etc/namedb/gchost.com.au.db:26: mail.gchost.com.au: CNAME and other data
    Feb 28 10:35:15 bonobo named[4450]: zone gchost.com.au/IN: loading master file /etc/namedb/gchost.com.au.db: CNAME and other data
    Feb 28 10:35:15 bonobo named[4450]: zone 1.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.INT/IN: loading master file /etc/named/localhost-v6.rev: file not found
    Feb 28 10:35:19 bonobo named[4486]: starting BIND 9.3.0 -u bind -c /etc/namedb/named.conf
    Feb 28 10:35:19 bonobo named[4486]: command channel listening on 127.0.0.1#953
    Feb 28 10:35:19 bonobo named[4486]: zone 0.0.127.IN-ADDR.ARPA/IN: loading master file /etc/named/localhost.rev: file not found
    Feb 28 10:35:19 bonobo named[4486]: zone 1.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: loading master file /etc/named/localhost-v6.rev: file not found
    Feb 28 10:35:19 bonobo named[4486]: dns_master_load: /etc/namedb/gchost.com.au.db:26: mail.gchost.com.au: CNAME and other data
    Feb 28 10:35:19 bonobo named[4486]: zone gchost.com.au/IN: loading master file /etc/namedb/gchost.com.au.db: CNAME and other data
    Feb 28 10:35:19 bonobo named[4486]: zone 1.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.INT/IN: loading master file /etc/named/localhost-v6.rev: file not found
    Feb 28 10:48:50 bonobo named[4486]: zone 0.0.127.IN-ADDR.ARPA/IN: loading master file /etc/named/localhost.rev: file not found
    Feb 28 10:48:50 bonobo named[4486]: zone 1.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: loading master file /etc/named/localhost-v6.rev: file not found
    Feb 28 10:48:50 bonobo named[4486]: zone 1.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.INT/IN: loading master file /etc/named/localhost-v6.rev: file not found
    Feb 28 10:49:21 bonobo named[4588]: starting BIND 9.3.0 -u bind -c /etc/namedb/named.conf
    Feb 28 10:49:21 bonobo named[4588]: command channel listening on 127.0.0.1#953
    Feb 28 10:49:21 bonobo named[4588]: zone 0.0.127.IN-ADDR.ARPA/IN: loading master file /etc/named/localhost.rev: file not found
    Feb 28 10:49:21 bonobo named[4588]: zone 1.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: loading master file /etc/named/localhost-v6.rev: file not found
    Feb 28 10:49:21 bonobo named[4588]: zone 1.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.INT/IN: loading master file /etc/named/localhost-v6.rev: file not found
    Feb 28 10:53:06 bonobo named[4631]: starting BIND 9.3.0 -u bind -c /etc/namedb/named.conf
    Feb 28 10:53:06 bonobo named[4631]: command channel listening on 127.0.0.1#953
    Feb 28 10:53:06 bonobo named[4631]: zone 0.0.127.IN-ADDR.ARPA/IN: loading master file /etc/named/master/localhost.rev: file not found
    Feb 28 10:53:06 bonobo named[4631]: zone 1.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: loading master file /etc/named/master/localhost-v6.rev: file not found
    Feb 28 10:53:06 bonobo named[4631]: zone 1.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.INT/IN: loading master file /etc/named/master/localhost-v6.rev: file not found
    Feb 28 10:55:01 bonobo named[4631]: zone 0.0.127.IN-ADDR.ARPA/IN: loading master file /var/named/etc/named/master/localhost.rev: file not found
    Feb 28 10:55:01 bonobo named[4631]: zone 1.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: loading master file /var/named/etc/named/master/localhost-v6.rev: file not found
    Feb 28 10:55:01 bonobo named[4631]: zone 1.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.INT/IN: loading master file /var/named/etc/named/master/localhost-v6.rev: file not found
    Feb 28 10:55:06 bonobo named[4698]: starting BIND 9.3.0 -u bind -c /etc/namedb/named.conf
    Feb 28 10:55:06 bonobo named[4698]: command channel listening on 127.0.0.1#953
    Feb 28 10:55:06 bonobo named[4698]: zone 0.0.127.IN-ADDR.ARPA/IN: loading master file /var/named/etc/named/master/localhost.rev: file not found
    Feb 28 10:55:06 bonobo named[4698]: zone 1.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: loading master file /var/named/etc/named/master/localhost-v6.rev: file not found
    Feb 28 10:55:06 bonobo named[4698]: zone 1.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.INT/IN: loading master file /var/named/etc/named/master/localhost-v6.rev: file not found
    Feb 28 11:02:06 bonobo named[4854]: starting BIND 9.3.0 -u bind -c /etc/namedb/named.conf
    Feb 28 11:02:06 bonobo named[4854]: command channel listening on 127.0.0.1#953
    Feb 28 11:02:06 bonobo named[4854]: zone 0.0.127.IN-ADDR.ARPA/IN: loading master file /etc/named/localhost.rev: file not found
    Feb 28 11:02:06 bonobo named[4854]: zone 1.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: loading master file /var/named/etc/named/master/localhost-v6.rev: file not found
    Feb 28 11:02:06 bonobo named[4854]: zone 1.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.INT/IN: loading master file /var/named/etc/named/master/localhost-v6.rev: file not found
    Feb 28 11:05:56 bonobo named[4926]: starting BIND 9.3.0 -u bind -c /etc/namedb/named.conf
    Feb 28 11:05:56 bonobo named[4926]: command channel listening on 127.0.0.1#953
    Feb 28 11:06:27 bonobo named[4926]: transfer of '0.168.192.in-addr.arpa/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:06:27 bonobo named[4926]: transfer of 'example.com/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:07:26 bonobo named[4926]: transfer of '0.168.192.in-addr.arpa/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:07:27 bonobo named[4926]: transfer of 'example.com/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:09:16 bonobo named[4926]: transfer of '0.168.192.in-addr.arpa/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:09:20 bonobo named[4926]: transfer of 'example.com/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:12:35 bonobo named[4926]: transfer of '0.168.192.in-addr.arpa/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:12:51 bonobo named[4926]: transfer of 'example.com/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:19:08 bonobo named[4926]: transfer of '0.168.192.in-addr.arpa/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:20:12 bonobo named[4926]: transfer of 'example.com/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:26:52 bonobo named[5206]: starting BIND 9.3.0 -u bind -c /etc/namedb/named.conf
    Feb 28 11:26:52 bonobo named[5206]: /etc/namedb/named.conf:7: couldn't find key 'rndc-key' for use with command channel 127.0.0.1#953
    Feb 28 11:26:52 bonobo named[5206]: command channel listening on 127.0.0.1#953
    Feb 28 11:27:22 bonobo named[5206]: transfer of '0.168.192.in-addr.arpa/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:27:22 bonobo named[5206]: transfer of 'example.com/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:27:29 bonobo named[5206]: invalid command from 127.0.0.1#52733: bad auth
    Feb 28 11:27:29 bonobo named[5224]: starting BIND 9.3.0 -u bind -c /etc/namedb/named.conf
    Feb 28 11:27:29 bonobo named[5224]: command channel listening on 127.0.0.1#953
    Feb 28 11:28:00 bonobo named[5224]: transfer of 'example.com/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:28:12 bonobo named[5224]: transfer of '0.168.192.in-addr.arpa/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:28:49 bonobo named[5224]: transfer of 'example.com/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:28:55 bonobo named[5224]: transfer of '0.168.192.in-addr.arpa/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:30:31 bonobo named[5224]: transfer of '0.168.192.in-addr.arpa/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:30:53 bonobo named[5224]: transfer of 'example.com/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:33:30 bonobo named[5224]: unknown control channel command 'relaod'
    Feb 28 11:34:35 bonobo named[5224]: transfer of 'example.com/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:34:38 bonobo named[5224]: transfer of '0.168.192.in-addr.arpa/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:47:28 bonobo named[5224]: transfer of '0.168.192.in-addr.arpa/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:50:30 bonobo named[5224]: transfer of 'example.com/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:53:19 bonobo named[5224]: transfer of '0.168.192.in-addr.arpa/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 11:53:19 bonobo named[5224]: transfer of 'example.com/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 12:15:00 bonobo su: kyle to root on /dev/ttyp1
    -----------------> End Snip
     
  6. DigitalN

    DigitalN Well-Known Member

    Joined:
    Sep 23, 2004
    Messages:
    420
    Likes Received:
    1
    Trophy Points:
    18
    Bind doesn't appear to be running at 202.144.167.142

    Is Bind enabled within whm ?

    Check that it is enabled and if not enable it.

    Also

    # /scripts/fixndc

    then

    # rndc reload

    and tail -100 /var/log/messages

    Check for errors in messages.

    That should rectify that issue.
     
    #6 DigitalN, Feb 27, 2005
    Last edited: Feb 27, 2005
  7. kylebuttress

    kylebuttress Member

    Joined:
    Feb 15, 2005
    Messages:
    11
    Likes Received:
    0
    Trophy Points:
    1
    restarted service in whm

    ------------------->Snip
    Waiting for named to restart.... . . . . . . . . . . finished.

    named status

    bind 5833 0.0 0.4 5308 4288 ?? Ss 12:26PM 0:00.03 /usr/sbin/named -u bind -c /etc/namedb/named.conf


    named started ok Feb 28 12:26:45 bonobo named[5833]: starting BIND 9.3.0 -u bind -c /etc/namedb/named.conf Feb 28 12:26:45 bonobo named[5833]: command channel listening on 127.0.0.1#953

    ---->End Snip

    more from messages
    ------------------> Snip
    Feb 28 12:26:45 bonobo named[5833]: starting BIND 9.3.0 -u bind -c /etc/namedb/named.conf
    Feb 28 12:26:45 bonobo named[5833]: command channel listening on 127.0.0.1#953
    Feb 28 12:27:15 bonobo named[5833]: transfer of '0.168.192.in-addr.arpa/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 12:27:16 bonobo named[5833]: transfer of 'example.com/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 12:28:09 bonobo named[5833]: transfer of '0.168.192.in-addr.arpa/IN' from 192.168.1.1#53: failed to connect: connection refused
    Feb 28 12:28:20 bonobo named[5833]: transfer of 'example.com/IN' from 192.168.1.1#53: failed to connect: connection refused

    ---------> ENd Snip
     
  8. DigitalN

    DigitalN Well-Known Member

    Joined:
    Sep 23, 2004
    Messages:
    420
    Likes Received:
    1
    Trophy Points:
    18
    Your slave zone hasn't made it to the secondary name server (due to bind not running on your primary I would imagine)



    # dig @ns1.zodns.com gchost.com.au

    ; <<>> DiG 9.2.4 <<>> @ns1.zodns.com gchost.com.au
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 7149
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;gchost.com.au. IN A

    ;; Query time: 220 msec
    ;; SERVER: 66.114.69.151#53(ns1.zodns.com)
    ;; WHEN: Mon Feb 28 15:31:36 2005
    ;; MSG SIZE rcvd: 31
     
  9. DigitalN

    DigitalN Well-Known Member

    Joined:
    Sep 23, 2004
    Messages:
    420
    Likes Received:
    1
    Trophy Points:
    18
    Bind isn't running still

    # nmap 202.144.167.142

    Interesting ports on (202.144.167.142):
    (The 1583 ports scanned but not shown below are in state: closed)
    Port State Service
    21/tcp open ftp
    22/tcp open ssh
    25/tcp open smtp
    80/tcp open http
    110/tcp open pop-3
    135/tcp filtered loc-srv
    139/tcp filtered netbios-ssn
    143/tcp open imap2
    443/tcp open https
    445/tcp filtered microsoft-ds
    465/tcp open smtps
    993/tcp open imaps
    995/tcp open pop3s
    1080/tcp filtered socks
    3306/tcp open mysql
    6346/tcp filtered gnutella
    6666/tcp open irc-serv
    65301/tcp filtered pcanywhere
     
  10. kylebuttress

    kylebuttress Member

    Joined:
    Feb 15, 2005
    Messages:
    11
    Likes Received:
    0
    Trophy Points:
    1
    odd

    server status shows

    apache (1.3.33 (Unix)) up
    bind (9.3.0) up
    cppop up
    cpsrvd up
    exim up
    eximstats up
    ftpd up
    imap up
    mysql (4.0.21) up
    spamd up
    syslogd up
    Server Load 0.02 (1 cpu)
    Memory Used 15.96 %
    Swap 0.00 %
    Disk amrd0s1a (/) 8 %
    Disk amrd0s1d (/usr) 21 %
    Disk amrd0s1e (/var) 1 %


    ps -aux | grep bind shows
    bind 5833 0.0 0.4 5428 4412 ?? Is 12:26PM 0:00.07 /usr/sbin/named -u bind -c /etc/namedb/named.conf

    so thats weird?
     
  11. DigitalN

    DigitalN Well-Known Member

    Joined:
    Sep 23, 2004
    Messages:
    420
    Likes Received:
    1
    Trophy Points:
    18
    Do you have ports 953 and 53 enabled within your firewall? Do you have a firewall?

    What does

    # /scripts/fixndc

    do .. any good ?
     
  12. kylebuttress

    kylebuttress Member

    Joined:
    Feb 15, 2005
    Messages:
    11
    Likes Received:
    0
    Trophy Points:
    1
    no firewall setup on machine

    bonobo# /scripts/fixndc
    Found key in named.conf ..
    Found controls in named.conf ..
    named.conf has already been fixed!
     
  13. DigitalN

    DigitalN Well-Known Member

    Joined:
    Sep 23, 2004
    Messages:
    420
    Likes Received:
    1
    Trophy Points:
    18
    You need to comment this part out of /etc/namedb/named.conf (freebsd) default or /etc/named.conf - whichever is yours

    // If named is being used only as a local resolver, this is a safe default.
    // For named to be accessible to the network, comment this option, specify
    // the proper IP address, or delete this option.
    listen-on { 127.0.0.1; };

    Change to

    // If named is being used only as a local resolver, this is a safe default.
    // For named to be accessible to the network, comment this option, specify
    // the proper IP address, or delete this option.
    //listen-on { 127.0.0.1; };

    And then restart named - that should allow connections to your network interfaces, rather than just 127.0.0.1

    I missed that earlier :)
     
    #13 DigitalN, Feb 27, 2005
    Last edited: Feb 27, 2005
  14. kylebuttress

    kylebuttress Member

    Joined:
    Feb 15, 2005
    Messages:
    11
    Likes Received:
    0
    Trophy Points:
    1
    I have done that

    this has fixed a lot of errors from the dnsreport.com page.


    thanks so much for your help.

    such a small thing

    I must have skimmed passed that line a hunder times.

    thanks heaps

    regards

    Kyle
     
  15. DigitalN

    DigitalN Well-Known Member

    Joined:
    Sep 23, 2004
    Messages:
    420
    Likes Received:
    1
    Trophy Points:
    18
    Looks like you fixed that now :)

    You need an A record for the domain (without www) as there is a problem there still, but the dns zone is now readable :)

    # dig @202.144.167.142 www.gchost.com.au

    ; <<>> DiG 9.2.4 <<>> @202.144.167.142 www.gchost.com.au
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11570
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

    ;; QUESTION SECTION:
    ;www.gchost.com.au. IN A

    ;; ANSWER SECTION:
    www.gchost.com.au. 3600 IN A 202.144.167.142

    ;; AUTHORITY SECTION:
    gchost.com.au. 3600 IN NS ns1.gchost.com.au.
    gchost.com.au. 3600 IN NS ns1.zodns.com.

    ;; ADDITIONAL SECTION:
    ns1.zodns.com. 172642 IN A 66.114.69.151
    ns1.gchost.com.au. 3600 IN A 202.144.167.142

    ;; Query time: 51 msec
    ;; SERVER: 202.144.167.142#53(202.144.167.142)
    ;; WHEN: Mon Feb 28 16:04:02 2005
    ;; MSG SIZE rcvd: 128




    # dig @202.144.167.142 gchost.com.au

    ; <<>> DiG 9.2.4 <<>> @202.144.167.142 gchost.com.au
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47203
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;gchost.com.au. IN A

    ;; AUTHORITY SECTION:
    gchost.com.au. 3600 IN SOA ns1.gchost.com.au. kyle.ionlinemail.com. 2005022801 10800 3600 604800 86400

    ;; Query time: 51 msec
    ;; SERVER: 202.144.167.142#53(202.144.167.142)
    ;; WHEN: Mon Feb 28 16:04:51 2005
    ;; MSG SIZE rcvd: 91
     
Loading...

Share This Page