View Single Post
  #1  
Old 13th August 2009, 07:27
treeman treeman is offline
Junior Member
 
Join Date: May 2009
Posts: 29
Thanks: 0
Thanked 1 Time in 1 Post
Default Can somebody help me getting Bind to work on Centos 5?

I have set up bind on a centos 5 box on my network to act as a dns for my domain.
Bind is installed and starting ok.

This is my setup:

WAN "mywanip" -> ROUTER -> NAT:53 -> Centos 5 "192.168.0.28"
When i use online port checking tools it shows as connection successfull on port 53 WAN ip so I am assuming there is no problem there.

Domain.com -> Nameserver = "mywanip"

when I "ping" Domain.com I get reply from "mywanip"

when I "host" Domian.com I get :
Domain.com has address "mywanip"
Host Domain.com not found: 3(NXDOMAIN)
Host Domain.com not found: 3(NXDOMAIN)

when I "host" Domian.com from Centos5 box I get:
Domain.com has address "mywanip"
Host Domain.com not found: 2(SERVFAIL)
Host Domain.com not found: 2(SERVFAIL)

I am still new to Bind so I am guessing its my zone files that are not right, altho I have experimented with a few configurations that I found in tutorials but this is the furthest I can get.

Here is a copy of my named.conf and zone files:

Quote:
//
// Sample named.conf BIND DNS server 'named' configuration file
// for the Red Hat BIND distribution.
//
// See the BIND Administrator's Reference Manual (ARM) for details, in:
// file:///usr/share/doc/bind-*/arm/Bv9ARM.html
// Also see the BIND Configuration GUI : /usr/bin/system-config-bind and
// its manual.
//

options
{
// Those options should be used carefully because they disable port
// randomization
query-source port 53;
// query-source-v6 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";
#added
# listen-on port 53 { All; };

#added

};
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
//
// 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;
# all views must contain the root hints zone:
include "/etc/named.root.hints";

/* these are zones that contain definitions for all the localhost

/* 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 "/etc/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;
// all views must contain the root hints zone:
include "/etc/named.root.hints";

// include "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 "my.internal.zone" {

zone "my.internal.zone" {
type master;
file "de.com.zone";
};
zone "my.slave.internal.zone" {
type slave;
file "slaves/my.slave.internal.zone.db";
masters { /* put master nameserver IPs here */ 127.0.0.1; } ;
// put slave zones in the slaves/ directory so named can update them
};
zone "my.ddns.internal.zone" {
type master;
allow-update { key ddns_key; };
file "slaves/my.ddns.internal.zone.db";
// put dynamically updateable zones in the slaves/ directory so named can update them
};
};
key ddns_key
{
algorithm hmac-md5;
secret "PGKgJj2I9NVUSvcglyiAol8uy82rAIVZ0o0DPtgghucybko52 3LaUHba4tMA";
};
secret "PGKgJj2I9NVUSvcglyiAol8uy82rAIVZ0o0DPtgghucybko52 3LaUHba4tMA";
};
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:
*/
match-clients { any; };
match-destinations { any; };

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:
include "/etc/named.root.hints";

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

zone "de.external.com.zone" {
type master;
file "de.external.com.zone";
type master;
file "de.external.com.zone";
};
};

Quote:
de.com.zone
@ in soa localhost. root 1 3H 15M 1W 1D
ns localhost.

domain.com IN NS ns1.domain.com.
domain.com IN NS ns2.domain.com.
ns1 IN A 127.0.0.1
ns2 IN A 127.0.0.1

domain.com.com. IN A 192.168.0.28
localhost.domain.com. IN A 192.168.0.28
test.domain.com. IN A 192.168.0.39
web.domain.com. IN CNAME "some external link"
www IN CNAME domain.com.

Quote:
de.external.com.zone
@ in soa "mywanip". root 1 3H 15M 1W 1D
ns "mywanip".

domain.com IN NS ns1.domain.com.
domain.com IN NS ns2.domain.com.
ns1 IN A "mywanip"
ns2 IN A "mywanip"
domain.com. IN A "mywanip"
localhost.domain.com. IN A "mywanip"
test.domain.com. IN A "mywanip"
web.domain. IN CNAME "someexternallink"
www IN CNAME domain.

Any tips or observations would be helpfull, thank you
Reply With Quote
Sponsored Links