hello!
im in the middle on transfer my server to 14.2 slack, and on new system i add new local hostname - say, r1.domain.ca

i use named, i have master for this zone.

restart named.
in logfile all looks ok.
from the same server ping r1.domain.ca work great.

from my desktop, who going out via that server -
ping: cannot resolve r1.domain.ca: Unknown host


in the same time if i look by
host r1.domain.ca

or
nslookup r1.domain.ca

then all looks good, and i get returned ip for this hostname. but ping and trying to open that hostname in web browser does "unknown host" - what way that possible? :-O

ah yes, all my old third level hostnames, who i made a way ago, work good via ping. only that one new. i suppose, maybe client looks to another dns server to resolve, and while new zone not transfered....but why, then, via host / nslookup all is ok?

Hmm... are you sure that your named is configured as 'authoritative'?

Anyhoo, the best way to debug it is with tcpdump, so you can see the questions and answers:
# tcpdump -nlX -i eth0 port 53

named.conf:
acl recurseallow {10.10.0.0/24 ; 10.10.10.1/24 ; 127.0.0.1 ;};
options {
<------>directory "/var/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.
<------> */
<------> allow-recursion {recurseallow;};
//<----> query-source address * port 53;
<------>forward first;
<------>forwarders {
<------><------>8.8.8.8;
<------><------>#159.148.60.2;
<------><------>195.2.96.2;
<------><------>#193.41.195.5;
<------><------>};
};

//.
// a caching only nameserver config
//.

zone "." IN {
<------>type hint;
<------>file "caching-example/named.ca";
};


zone "domain.ca" {
<------>type master;
<------>file "domain.ca.zone";
<------>allow-update { none; };
<------>allow-query { any; };
<------>notify yes;
<------>allow-transfer { 174.37.196.55; //freedns.afraid.org
<------><------><------>173.244.206.26; //buddyns.com
<------><------><------>88.198.106.11; //buddyns.com
<------> };
<------>
};

I'm not running a DNS at the moment, but as far as I remember, the word 'authoritative' must be somewhere in the configuration file, otherwise the clients may ignore the IP address coming from it, since it is 'not authoritative' and therefore a test server / temporary server backup server that need not be trusted.

The example files from ISC.org all have the word in there, but commented out by default. Once your DNS is working properly, you have to uncomment it.