BIND question

[Lora Ganeva]

I have the following situation:
My nameserver turns to the forwarder server for a query for a zone, for which it has a nameserver defined.Why?
Any help would be greatly appreciated.

[John Bolene]

turn on debugging to see what is being requested

nslookup
set deb
name to query goes here
cntl-d to quit


On my name server, it goes thru all the local lookups before doing the forward.

[Lora Ganeva]

I did it..My nameserver asks the forwarder

[harry d brown jr]

Lora,

What does /etc/resolv.conf look like? /etc/nsswitch.conf??

live free or die
harry

[Sean OB_1]

What is the zone file config from named.conf for that zone?

You can setup a particular zone one your nameserver to forward to another server.

[Lora Ganeva]

I have no configuration in named.conf-just in the db file for the main zone I have configured a NS record for the another zone.

[Kellogg Unix Team]

Lora,

Is this zone a sub-domain for your nameserver? Who is primary for this zone? Have you tried becoming secondary for this zone to see if its stops forwarding?

If you can attach your named.conf (or named.boot) file and what version of BIND you are using, that will help to diagnose the issue.

...Manjeet

[Lora Ganeva]

hpov: / > vi /etc/named.conf
"/etc/named.conf" 113 lines, 1753 characters
// generated by named-bootconf.pl

options {
check-names response fail; // do not change this
check-names slave warn;
directory "/etc"; // running directory for named
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;

auth-nxdomain no;
notify yes;

// forwarders {
// 212.39.88.2;
// };
};

//
// type domain source file
//
zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "db.127.0.0";
};

zone "16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16";
};

//zone "10.10.10.IN-ADDR.ARPA" {
// type master;
// file "db.10.10.10";
//};

zone "." {
type hint;
file "db.cache";
};

zone "5.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.5";
};

zone "globul.bg" {
type master;
file "db.globul";
};

zone "net.globul.bg" {
type master;
file "db.net";
};



zone "1.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.1";
};

zone "3.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.3";
};

zone "34.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.34";
};

zone "54.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.54";
};

zone "74.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.74";
};

zone "33.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.33";
};

zone "32.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.32";
};

zone "73.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.73";
};

zone "53.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.53";
};

logging {
channel log {syslog;
severity debug;};
};

My nameserver is not a primary for this zone, neither secondary

[Lora Ganeva]

hpov: / > vi /etc/named.conf
"/etc/named.conf" 113 lines, 1753 characters
// generated by named-bootconf.pl

options {
check-names response fail; // do not change this
check-names slave warn;
directory "/etc"; // running directory for named
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;

auth-nxdomain no;
notify yes;

// forwarders {
// 212.39.88.2;
// };
};

//
// type domain source file
//
zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "db.127.0.0";
};

zone "16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16";
};

//zone "10.10.10.IN-ADDR.ARPA" {
// type master;
// file "db.10.10.10";
//};

zone "." {
type hint;
file "db.cache";
};

zone "5.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.5";
};

zone "globul.bg" {
type master;
file "db.globul";
};

zone "net.globul.bg" {
type master;
file "db.net";
};



zone "1.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.1";
};

zone "3.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.3";
};

zone "34.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.34";
};

zone "54.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.54";
};

zone "74.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.74";
};

zone "33.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.33";
};

zone "32.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.32";
};

zone "73.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.73";
};

zone "53.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.53";
};

logging {
channel log {syslog;
severity debug;};
};

My nameserver is not a primary for this zone, neither secondary

[Lora Ganeva]

hpov: / > vi /etc/named.conf
"/etc/named.conf" 113 lines, 1753 characters
// generated by named-bootconf.pl

options {
check-names response fail; // do not change this
check-names slave warn;
directory "/etc"; // running directory for named
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;

auth-nxdomain no;
notify yes;

// forwarders {
// 212.39.88.2;
// };
};

//
// type domain source file
//
zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "db.127.0.0";
};

zone "16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16";
};

//zone "10.10.10.IN-ADDR.ARPA" {
// type master;
// file "db.10.10.10";
//};

zone "." {
type hint;
file "db.cache";
};

zone "5.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.5";
};

zone "globul.bg" {
type master;
file "db.globul";
};

zone "net.globul.bg" {
type master;
file "db.net";
};



zone "1.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.1";
};

zone "3.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.3";
};

zone "34.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.34";
};

zone "54.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.54";
};

zone "74.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.74";
};

zone "33.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.33";
};

zone "32.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.32";
};

zone "73.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.73";
};

zone "53.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.53";
};

logging {
channel log {syslog;
severity debug;};
};

My nameserver is neither primary not secondary for this zone

[Kellogg Unix Team]

Lora,

I think you are using v8.1, correct? I looked at your named.conf file and forwarding option is turned off. What is the name of this zone that you are trying to define NS record for? If it isn't a part of globul.bg or net.globul.bg (e.g. corp.globul.bg or site.net.globul.bg respectively), the server is not even going to look at your db.globul and db.net database and will/should go to the servers defined in db.cache for further resolution.

Can you also send the contents of db.cache and let us know what zone you are trying to resolve?

...Manjeet

P.S. You can attach the file instead of pasting it.

[Lora Ganeva]

I have turned the forwarders option off after I have discovered that this is the case for the problem.
Version 8.1..yes, I'm using this version.
the zone I'm trying to define a ns record for is proba.bg-this is not a part of globul.bg, neither net.globul.bg

[Kellogg Unix Team]

If you are putting NS record for proba.bg inside globul.bg or net.globul.bg, its not going to work. The way DNS works(I think) is as follows -

When started, it reads named.conf file and finds that its only authoritative for globul.bg and net.globul.bg. If forwarders option is defined, for proba.bg, it will go to forwarder host. If forwarders option is removed, it will check db.cache and if there is a host authoritative for bg domain, it will go there and look for NS record for proba.bg.

You can try defining NS record for proba.bg in your db.cache and see if it get resolved that way. The correct way will be to refer all your unresolved queries to the top domain master(or slave) which is .bg in your case and let him resolve proba.bg for you.

The other option is to become secondary(slave) for this domain, ask proba.bg domain to put NS record for you and happily resolve the queries! This way, you can continue to use forwarders for other unresolved names.

HTH
...Manjeet

[Sean OB_1]

Manjeet is correct.

Your DNS will not resolve anything for this domain since there is no zone defined in named.conf.

Instead it will pass it up the chain of servers via the db.hint file. Hopefully one of the root servers knows where to point it to.

Sean

[Lora Ganeva]

No,
The fact is that I my nameserver turned to the forwarder for the zone for which I have defined a ns record in my db. file...and this continued untill I turned off the forwarder.
Thanks anyway

[Kellogg Unix Team]

Are you saying that if you put forwarders option, then your servers goes to forwarder server for globul.bg and net.globul.bg as well?

How does your db.cache look like?