odd behaviour: BIND 9.3.3rc2
Kevin Darcy
kcd at daimlerchrysler.com
Wed Aug 29 23:36:25 UTC 2007
Come now, is that really your named.conf? No match-clients, "recursion
yes" in your "external" view, and, if the file name is to be believed,
you're trying to include a hints file directly into named.conf?
Seems unlikely. Please post a more faithful rendition of what you're
actually running.
FWIW, I can resolve redelagos.com.br just fine. The
teresopolis.unimed.com.br zone has no A records at its apex, so that
doesn't resolve, but the apex MX records, and A records for other names
beneath the apex, such as www.teresopolis.unimed.com.br, resolve fine
for me.
- Kevin
Felipe Ceglia - PY1NB wrote:
> Hello again, bind gurus,
>
> I am running BIND 9.3.3rc2 on a centos box.
>
> It happens that I cant resolve some hosts, like:
>
> dig redelagos.com.br
> dig teresopolis.unimed.com.br
>
> And I can resolve it from other dns servers.
>
> Surely there is something wrong, but I cant figure what.
>
> Any ideas?
>
>
> My /etc/named.conf looks like:
>
> options
> {
> query-source port 53;
> query-source-v6 port 53;
> 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
> {
> channel default_debug {
> file "data/named.run";
> severity dynamic;
> };
> };
> view "internal"
> {
> include "/etc/named.root.hints";
> };
> //
> view "external"
> {
> recursion yes;
> zone "." IN {
> type hint;
> file "named.root";
> };
> zone "domain.com" {
> type master;
> file "named.domain.com";
> };
>
> };
>
>
>
>
>
More information about the bind-users
mailing list