Hi,

I have set up DNS server set up on my RH 5.5 system. It is working perfectly as Caching only Server but but when i tried to make it a primary server for a zone it didn't resolved. I am actually a newbie so please correct me if i am wrong somewhere. Here are my configuration files

------ named.conf---------

zone "myinternaldomain.com" {
type master;
file "myinternaldomain.com.zone";
};

----------Zone file ----------------

$TTL 86400
$ORIGIN myinternaldomain.com.
@ IN SOA LinuxServer.myinternaldomain.com. root.myinternaldomain.com.(
1997022700 ; Serial
28800 ; Refresh
14400 ; Retry
3600000 ; Expire
86400 ) ; Minimum


IN NS Linuxserver.myinternaldomain.com.
LinuxServer 3600 IN A 192.168.181.128

And here are the results when i try running the dig lookup command


[root@LinuxServer named]# dig @192.168.181.128 myinternaldomain.com

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> @192.168.181.128 myinternaldomain.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 6536
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

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

;; AUTHORITY SECTION:
com. 870 IN SOA a.gtld-servers.net. nstld.verisign-grs.com. 1295367407 1800 900 604800 86400

;; Query time: 2 msec
;; SERVER: 192.168.181.128#53(192.168.181.128)
;; WHEN: Tue Jan 18 08:17:47 2011
;; MSG SIZE rcvd: 111


192.168.181.128 : this is the IP address of the local system running as DNS server.

So please please help !!!

Thanks in advance..

You get a NXDOMAIN meaning that your dns works, but does not have an entry for myinternaldomain.com. Add it and you;be ok:
Regards

Thanks Bathory for the reply. I haven't tried it yet but i guess it will probably cos even to me it seems the possible issue after your explanation.

Thanks once again..

Hi Bathory,

Sorry to say but it didn't worked. I am still getting the same output and still unable to resolve.



dig @192.168.181.128 myinternaldomain.com

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> @192.168.181.128 myinternaldomain.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 59532
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

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

;; AUTHORITY SECTION:
com. 900 IN SOA a.gtld-servers.net. nstld.verisign-grs.com. 1295443575 1800 900 604800 86400

;; Query time: 45 msec
;; SERVER: 192.168.181.128#53(192.168.181.128)
;; WHEN: Wed Jan 19 05:26:58 2011
;; MSG SIZE rcvd: 111




nslookup
> 192.168.181.128
Server: 192.168.181.128
Address: 192.168.181.128#53

** server can't find 128.181.168.192.in-addr.arpa.: NXDOMAIN

Hi,

You have to increase the serial by one (from 1997022700, make it 1997022701) and reload bind

The reverse lookup is not working maybe because you don't have setup a reverse zone. IF you post the complete named.conf and the reverse zone file, if any, we could help better.

Here is the named.conf


//
// 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";

};
logging
{
* 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
// "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
* 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" {
type master;
file "my.internal.zone.db";
};
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
};

zone "myinternaldomain.com" {
type master;
file "myinternaldomain.com.zone";
};

};
#key ddns_key
#{
# algorithm hmac-md5;
# secret "use /usr/sbin/dns-keygen to generate TSIG keys";

#};


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

allow-query-cache { none; };
// Disable lookups for any cached data and root hints

// 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 "my.external.zone" {
type master;
file "my.external.zone.db";
};


And one more thing is it like that i have to create this domain "myinternaldomain.com" also for resolving it because i do not know how to create an internal domain. I tried googling for it quite a long but didnt found anything worth. So it will be really appericiable of you if you could help.

Thanks ...

There is no reverse lookup and more over i am not doing reverse lookup so will be it needed then also.

If you don't want reverse lookups don't create a reverse zone. I just pointed out why you got the error for nslookup 192.168.181.128

Regarding named.conf, comment out or remove the view "localhost_resolver" and restart bind, because you don't need a caching only dns

Thanks a lot Bathory... It worked this time but one more question, but if I want a caching only dns also as well as primary for some zone.

and Nslookup still throwing the same error is still throwing the same error.

This is how the current configuration works. Your name server is authoritative for the zone(s) you have defined and it's also caching using the hint zone to resolve other domains.

Since you don't have a reverse zone it's normal to throw this error.

1 members found this post helpful.