Configuration problem bind9

poiuytrez · 06-10-2009, 05:43 AM

Hello,

I am trying to setup a dns server (which is also a webserver) on debian lenny.
bind just does not want to start. It seems that I made a mistake in the configs files. I do not have any more error messages...

This is my named.conf.local

zone "ooole.be" {
type master;
file "/etc/bind/db.ooole.be"
};

and this is my db.ooole.be file

$TTL 85000
@ IN SOA ns.ooole.be. hostmaster.ooole.be. (
2009061001
8H
2H
1W
1D )

@ IN NS ns.ooole.be.
www IN A 87.98.153.152

Thank you for you help.

bathory · 06-10-2009, 05:55 AM

You miss a ";" at the end of the line "file "/etc/bind/db.ooole.be". It should be

Code:

file "/etc/bind/db.ooole.be";

You have also to add an A record for your dns, so your zone file should be:

Code:

$TTL 85000
@ IN SOA ns.ooole.be. hostmaster.ooole.be. (
2009061002
8H
2H
1W
1D )

@ IN NS ns.ooole.be.
www IN A 87.98.153.152
ns      IN A 87.98.153.152

Regards

poiuytrez · 06-11-2009, 10:13 PM

Thanks man ! It seems to work !

poiuytrez · 06-12-2009, 05:34 AM

Bind works, but the DNS serveur does not work.
My registrar is correctly pointing on the dns server, but my dns server does not seems to work...
When I do a
nslookup www.oole.be
on my server, it works. But when I do it from outsite (at home), it does not work.
Do you have any suggestions or tools to help me debug this problem ?

Thanks.

bathory · 06-12-2009, 05:54 AM

Quote:

My registrar is correctly pointing on the dns server, but my dns server does not seems to work...

Are you sure about that? Because as you can see from the following trace is seems that sdns1.ovh.net and r24786.ovh.net are authoritative for your domain.

Quote:

dig +trace oole.be

; <<>> DiG 9.6.1rc1 <<>> +trace oole.be
;; global options: +cmd
. 420885 IN NS B.ROOT-SERVERS.NET.
. 420885 IN NS D.ROOT-SERVERS.NET.
. 420885 IN NS J.ROOT-SERVERS.NET.
. 420885 IN NS I.ROOT-SERVERS.NET.
. 420885 IN NS F.ROOT-SERVERS.NET.
. 420885 IN NS L.ROOT-SERVERS.NET.
. 420885 IN NS A.ROOT-SERVERS.NET.
. 420885 IN NS K.ROOT-SERVERS.NET.
. 420885 IN NS H.ROOT-SERVERS.NET.
. 420885 IN NS C.ROOT-SERVERS.NET.
. 420885 IN NS E.ROOT-SERVERS.NET.
. 420885 IN NS M.ROOT-SERVERS.NET.
. 420885 IN NS G.ROOT-SERVERS.NET.
;; Received 272 bytes from 127.0.0.1#53(127.0.0.1) in 1 ms

be. 172800 IN NS a.ns.dns.be.
be. 172800 IN NS b.ns.dns.be.
be. 172800 IN NS c.ns.dns.be.
be. 172800 IN NS x.dns.be.
be. 172800 IN NS london.ns.dns.be.
be. 172800 IN NS prague.ns.dns.be.
be. 172800 IN NS brussels.ns.dns.be.
be. 172800 IN NS amsterdam.ns.dns.be.
;; Received 369 bytes from 193.0.14.129#53(K.ROOT-SERVERS.NET) in 106 ms

oole.be. 86400 IN NS sdns1.ovh.net.
oole.be. 86400 IN NS r24786.ovh.net.
;; Received 87 bytes from 194.0.1.10#53(x.dns.be) in 103 ms

;; Received 25 bytes from 213.251.188.140#53(sdns1.ovh.net) in 106 ms

poiuytrez · 06-12-2009, 02:10 PM

The primary dns is r24786.ovh.net.
which is my server.

bathory · 06-12-2009, 03:17 PM

According to your 1st post the NS record for oole.be is supposed to be ns.ooole.be, so you have to change that to r24786.ovh.net
And the main problem is that r24786.ovh.net is not reachable from the internet:

Quote:

dig oole.be @r24786.ovh.net

; <<>> DiG 9.6.0-P1 <<>> oole.be @r24786.ovh.net
;; global options: +cmd

;; connection timed out; no servers could be reached
If this is the named server you're trying to configure, then you must configure your firewall to allow dns queries (open tcp/udp port 53)

Regards

poiuytrez · 06-12-2009, 03:22 PM

Ok, when I try on the server
dig @87.98.153.183 www.oole.be
is does not work. But when I try
dig @127.0.0.1 www.oole.be
is works. But the firewall is not configured in debian by default, so I really don't see where it does not work.

Thanks.

bathory · 06-12-2009, 03:32 PM

Could you please post /etc/named.conf, or at least the output of:

Code:

netstat -tuanp|grep 53

Maybe you have configured bind to listen only on the loopback interface.

poiuytrez · 06-13-2009, 12:22 AM

Thank you man,

You were right! I had to modify /etc/bind/named.conf.options
to add the line :

listen-on { 87.98.153.183; };

Now it works !