bind server doesn't do its job

milimooli · 10-14-2012, 03:55 PM

Hi There...
I just installed bind on RHEL 6 and point a domain to that server. but actually when i ping domain from network-tools.com, it returns error 1214:Unknown error
Here is my named.conf:

Code:

//
// named.conf
//
// Provided by Red Hat bind package to configure the ISC BIND named(8) DNS
// server as a caching only nameserver (as a localhost DNS resolver only).
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//

options {
    listen-on port 53 { any; };
    listen-on-v6 port 53 { ::1; };
    directory       "/var/named";
    dump-file       "/var/named/data/cache_dump.db";
    statistics-file "/var/named/data/named_stats.txt";
    memstatistics-file "/var/named/data/named_mem_stats.txt";
    allow-query     { any; };
    recursion yes;

    dnssec-enable yes;
    dnssec-validation yes;
    dnssec-lookaside auto;

    /* Path to ISC DLV key */
    bindkeys-file "/etc/named.iscdlv.key";

    managed-keys-directory "/var/named/dynamic";
};

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

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

include "/etc/named.rfc1912.zones";
include "/etc/named.root.key";
zone "mydomain.com"{
    type master;
    file "/var/named/data/named.mydomain.com";
    allow-update { none; };
 };`

AND The content of "/var/named/data/named.mydomain.com":

Code:

$TTL 38400

mydomain.com. IN SOA ns1.mydomain.com. milad.yahoo.com. (
2012101201 ; serial number YYMMDDNN
28800 ; Refresh
7200 ; Retry
864000 ; Expire
38400 ; Min TTL
)

mydomain.com. IN A 1.2.3.4
www IN A 1.2.3.4
ns1.mydomain.com. IN A 1.2.3.4
ns2.mydomain.com. IN A 1.2.3.4
mydomain.com. IN NS ns1.mydomain.com.
mydomain.com. IN NS ns2.mydomain.com.

AND i'm sure the named service is running:

Code:

[root@server ~]# service named status
version: 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.3
CPUs found: 8
worker threads: 8
number of zones: 20
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/0/1000
tcp clients: 0/100
server is up and running
named (pid 26299) is running...

Also here is the output of dig utility:

Code:

[root@server ~]# dig mydomain.com
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.3 <<>> mydomain.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 6806
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

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

;; Query time: 321 msec
;; SERVER: 5.6.7.8#53(5.6.7.8)##note that 5.6.7.8 is my idc dns ip
;; WHEN: Sun Oct 14 23:53:47 2012

bathory · 10-15-2012, 03:36 AM

Quote:

dig mydomain.com
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.3 <<>> mydomain.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 6806
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

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

;; Query time: 321 msec
;; SERVER: 5.6.7.8#53(5.6.7.8)##note that 5.6.7.8 is my idc dns ip
;; WHEN: Sun Oct 14 23:53:47 2012

You get a SERVFAIL from the 5.6.7.8 dns server.
I guess 5.6.7.8 is defined in /etc/resolv.conf and it's somehow misconfigured. Try:

Code:

dig mydomain.com @1.2.3.4

and see what you get.

Regards

milimooli · 10-15-2012, 01:05 PM

Thanks for your reply Bathory
I'm sure /etc/resolv.conf is configured right(with ip 5.6.7.8) as i can ping every where, yahoo,google,... and got proper reply.
I executed the command you mentioned and get strange answer. in result body is domains and ips that i don't even know what they are!!!!

Code:

[root@server ~]# dig mydomain.com @1.2.3.4

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.3 <<>> mydomain.com @1.2.3.4
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9454
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 4

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

;; ANSWER SECTION:
mydomain.com.		300	IN	A	176.74.176.167

;; AUTHORITY SECTION:
mydomain.com.		172798	IN	NS	sell.internettraffic.com.
mydomain.com.		172798	IN	NS	buy.internettraffic.com.

;; ADDITIONAL SECTION:
buy.internettraffic.com. 172798	IN	A	208.87.35.121
buy.internettraffic.com. 172798	IN	A	208.87.35.120
sell.internettraffic.com. 172798 IN	A	176.74.176.169
sell.internettraffic.com. 172798 IN	A	176.74.176.170

;; Query time: 3177 msec
;; SERVER: 1.2.3.4#53(1.2.3.4)
;; WHEN: Mon Oct 15 21:13:52 2012
;; MSG SIZE  rcvd: 163

bathory · 10-15-2012, 04:17 PM

Quote:

I executed the command you mentioned and get strange answer. in result body is domains and ips that i don't even know what they are!!!!

I guess you've replaced mydomain.com with the actual domain name of your domain and 1.2.3.4 with the real IP of your dns.
According to the zone file you've posted, 1.2.3.4 is supposed to be the authoritative nameserver for your domain. So it should answer authoritatively (set the aa flag in response), resolving mydomain.com to 1.2.3.4.
If it looks wrong you may use:

Code:

dig +trace mydomain.com

and/or this site trying to identify the data known by the other nameservers for your domain

Regards

milimooli · 10-18-2012, 01:50 AM

Thanks bathory,

that site displayed that there is a problem. could you please give me your main address so that i can send real output for you?

bathory · 10-18-2012, 03:16 AM

Quote:

Originally Posted by milimooli

Thanks bathory,

that site displayed that there is a problem. could you please give me your main address so that i can send real output for you?

You can click on my nick and select "Contact Info" to send me an email.

Cheers.