[cj_cheema]

Hi
I have setup BIND as my local network's name resolution (DNS) server. I'm facing a problem that Neither I'm not able to resolve my dns ip address or vice versa on server nor from client. But I'm able to resolve localhost on dns server i'm pasting the results below:
Result of localhost resolution:-
[root@cjpunjabiradio ~]# nslookup 127.0.0.1
Server: 127.0.0.1
Address: 127.0.0.1#53

1.0.0.127.in-addr.arpa name = localhost.
[root@cjpunjabiradio ~]# nslookup localhost
Server: 127.0.0.1
Address: 127.0.0.1#53

Name: localhost
Address: 127.0.0.1

Result of resolution with my server ip address:-
[root@cjpunjabiradio ~]# nslookup 192.168.0.2
;; connection timed out; no servers could be reached

[root@cjpunjabiradio ~]# nslookup cjpunjabiradio
Server: 192.168.0.2
Address: 192.168.0.2#53

** server can't find cjpunjabiradio: NXDOMAIN

Also i'm pasting my zones files and name file configuration:

ZONES FILE
1.

@ IN SOA ns.cjpunjabiradio.co.in. root.cjpunjabiradio.co.in. (
2008062904 ; Serial (yyyymmddxx)
86400 ; Refresh (1 day)
7200 ; Retry (2 hours)
604800 ; Expire (7 days)
86400 ) ; Minimum (1 day)

IN NS ns.cjpunjabiradio.co.in

example.com. IN A 192.168.0.2
www IN CNAME cjpunjabiradio.co.in.
ftp IN CNAME cjpunjabiradio.co.in.

cjpunjabiradio IN A 192.168.0.2
node-1 IN A 192.168.0.3

2.

@ IN SOA ns.cjpunjabiradio.co.in. root.cjpunjabiradio.co.in. (
2008070205 ; Serial (yyyymmddxx)
86400 ; Refresh (1 day)
7200 ; Retry (2 hours)
604800 ; Expire (7 days)
86400 ) ; Minimum (1 day)

IN NS ns.cjpunjabiradio.co.in.

1 IN PTR cjpunjabiradio.co.in.
2 IN PTR node-1.cjpunjabiradio.co.in.

NEMED.CONF

//
// named.caching-nameserver.conf
//
// Provided by Red Hat caching-nameserver package to configure the
// ISC BIND named DNS server as a caching only nameserver
// (as a localhost DNS resolver only).
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//
// DO NOT EDIT THIS FILE - use system-config-bind or an editor
// to create named.conf - edits to this file will be lost on
// caching-nameserver package upgrade.
//
// ACl for controlling DNS behaviour.
acl "myaddresses" { 127.0.0.1; 192.168.0.2; };
acl "trusted" { 192.168.0.3; };
options {
# Bind to specified interfaces
listen-on port 53 { myaddresses; };
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";
query-source port 53;
query-source-v6 port 53;
allow-query { localhost; trusted; };
allow-recursion { localhost; trusted; };

/* Now that systems i want to allow for zone transfer mention below */
allow-transfer { localhost; 192.168.0.2; };

# Use a recursive, upstream name server
forwarders { 59.179.243.70; 203.94.243.70; 192.168.0.2; };
forward only;
};
logging {
channel default_debug {
file "data/named.run";
severity dynamic;
};
};
view localhost_resolver {
match-clients { localhost; };
match-destinations { localhost; };
recursion yes;
include "/etc/named.rfc1912.zones";
};
# I have mentioned the zone files for BIND. Zones are two types forward and reverse.
zone "cjpunjabiradio.co.in" {
type master;
file "/var/named/named.cjpunjabiradio.co.in";
};

zone "0.168.192.in-addr.arpa" {
type master;
file "/var/named/named.0.168.192.in-addr.arpa";
};

If you find any mistake please guide. Welcome for your comments and solution.

Thanks and Regards
Charanjit Cheema

[phoenic]

The cjpunjabiradio.co.in. is your domain name, which was defined in your SOA record. It is a domain, not a host. You should write your zone file like this:
A record zone file:
$TTL 86400
@ IN SOA ns.cjpunjabiradio.co.in. root.cjpunjabiradio.co.in. (
2008062904 ; Serial (yyyymmddxx)
86400 ; Refresh (1 day)
7200 ; Retry (2 hours)
604800 ; Expire (7 days)
86400 ) ; Minimum (1 day)
IN NS ns.cjpunjabiradio.co.in.
ns.cjpunjabiradio.co.in. IN A 192.168.0.2
www.cjpunjabiradio.co.in. IN CNAME ns.cjpunjabiradio.co.in.
ftp.cjpunjabiradio.co.in. IN CNAME ns.cjpunjabiradio.co.in.
node-1 IN A 192.168.0.3

PTR record zone file:
$TTL 86400
@ IN SOA ns.cjpunjabiradio.co.in. root.cjpunjabiradio.co.in. (
2008070205 ; Serial (yyyymmddxx)
86400 ; Refresh (1 day)
7200 ; Retry (2 hours)
604800 ; Expire (7 days)
86400 ) ; Minimum (1 day)

IN NS ns.cjpunjabiradio.co.in.
2 IN PTR ns.cjpunjabiradio.co.in.
3 IN PTR node-1.cjpunjabiradio.co.in.

[Lazydog]

First things first.

Originally Posted by phoenic

The cjpunjabiradio.co.in. is your domain name, which was defined in your SOA record. It is a domain, not a host. You should write your zone file like this:

Stop giving bad/incorrect advice. Because the domain is defined you do not need to use FQDN in the zone files.

cj_cheema
What does your resolve file have listed?
Is it setup to resolve your domain?

[phoenic]

Originally Posted by Lazydog

First things first.



Stop giving bad/incorrect advice. Because the domain is defined you do not need to use FQDN in the zone files.

cj_cheema
What does your resolve file have listed?
Is it setup to resolve your domain?

well, well, come on. show your advice, write down your zone file(s).

[Lazydog]

$ORIGIN .
$TTL 36000 ; 10 hours
mydomain.foo IN SOA ns.mydomain.foo. support.mydomain.foo. (
2007101301 ; serial
3600 ; refresh (1 hour)
900 ; retry (15 minutes)
604800 ; expire (1 week)
3600 ; minimum (1 hour)
)
NS ns1
NS ns2
NS ns3
NS ns4
$ORIGIN mydomain.foo.
arm A 192.168.4.1
finger A 192.168.4.5
foot A 192.168.4.3
leg A 192.168.4.2