Internernal view is answering to external ping

[Barry Margolin]

In article <mailman.982.1375317436.20661.bind-users at lists.isc.org>,
 IT Support <it.compilation at gmail.com> wrote:

> Thanks Mark for the advice, that output is my whole named.conf, please 
> let me know if I need to post another output file

It contains:

include "/etc/bind/named.conf.options";
include "/etc/bind/named.conf.local";

One of these files should contain the view configuration.

> 
> This is what do i have on my bind folder:
> 
> named.conf
> named.conf.dpkg-dist
> named.conf.local
> named.conf.local.bfRFC1918
> named.conf.local.orig
> named.conf.options
> named.conf.options.dpkg-di
> mydomain.com.hosts
> mydomain.com.hosts.lan
> db.0
> db.127
> db.192
> 192.168.0
> db.192.168.0.internal
> db.192.168.0.internal.jnl
> db.192.168.external
> db.192.168.internal
> db.192.168.internal.jnl
> db.192.internal
> db.192.jnl
> db.255
> db.empty
> db.local
> db.root
> root b
> 
> On 31/07/2013 7:09 PM, Mark Andrews wrote:
> > Post your *full* config not half of it.  How the hell do you expect
> > people to identify problems unless you give them the neccessary
> > details.
> >
> > Do you give you car mechanic only access to the boot when you have
> > a engine problem?
> >
> > You said you created views yet you didn't send anything that described
> > how the views were configured.
> >
> > Mark
> >
> > In message <51F9A4DC.6040205 at gmail.com>, IT Support writes:
> >> Dear Carl
> >>
> >> Thanks for your answer here the output:
> >>
> >> acl allowed-users {
> >>           localhost;
> >> 200.57.66.77/28;
> >>           192.168.0.0/23;
> >>           189.0.0.0/8;
> >>           172.16.102.1;
> >>           172.28.76.0/24;
> >>           };
> >>
> >> acl internal {
> >>           localhost;
> >> 200.57.66.77/28;
> >>           192.168.0.0/23
> >>           };
> >>
> >> acl slaves {
> >> 200.57.66.78;
> >>           };
> >>
> >> // This is the primary configuration file for the BIND DNS server named.
> >> //
> >> // Please read /usr/share/doc/bind9/README.Debian.gz for information on 
> >> the
> >> // structure of BIND configuration files in Debian, *BEFORE* you customize
> >> // this configuration file.
> >> //
> >> // If you are just adding zones, please do that in
> >> /etc/bind/named.conf.local
> >>
> >> include "/etc/bind/named.conf.options";
> >>
> >> // prime the server with knowledge of the root servers
> >> //zone "." {
> >> //      type hint;
> >> //      file "/etc/bind/db.root";
> >> //};
> >>
> >> // be authoritative for the localhost forward and reverse zones, and for
> >> // broadcast zones as per RFC 1912
> >>
> >> //zone "localhost" {
> >> //      type master;
> >> //      file "/etc/bind/db.local";
> >> //};
> >> //zone "127.in-addr.arpa" {
> >> //      type master;
> >> //      file "/etc/bind/db.127";
> >> //};
> >>
> >> //zone "0.in-addr.arpa" {
> >> //      type master;
> >> //      file "/etc/bind/db.0";
> >> //};
> >>
> >> //zone "255.in-addr.arpa" {
> >> //      type master;
> >> //      file "/etc/bind/db.255";
> >> //};
> >>
> >> //zone "168.192.IN-ADDR.ARPA" {
> >> //        type master;
> >> //        file "/etc/bind/db.192";
> >> //};
> >>
> >> //zone "10.IN-ADDR.ARPA" {
> >> //      type master;
> >> //      file "/etc/empty";
> >> //};
> >>
> >> //zone "16.172.IN-ADDR.ARPA" {
> >> //      type master;
> >> //      file "/etc/empty";
> >> //};
> >>
> >>
> >>
> >> // zone "com" { type delegation-only; };
> >> // zone "net" { type delegation-only; };
> >>
> >> // From the release notes:
> >> //  Because many of our users are uncomfortable receiving undelegated
> >> answers
> >> //  from root or top level domains, other than a few for whom that 
> >> behaviour
> >> //  has been trusted and expected for quite some length of time, we have 
> >> now
> >> //  introduced the "root-delegations-only" feature which applies
> >> delegation-only
> >> //  logic to all top level domains, and to the root domain.  An
> >> exception list
> >> //  should be specified, including "MUSEUM" and "DE", and any other top
> >> level
> >> //  domains from whom undelegated responses are expected and trusted.
> >> // root-delegation-only exclude { "DE"; "MUSEUM"; };
> >>
> >> include "/etc/bind/named.conf.local";
> >> logging {
> >>           category lame-servers { null; };
> >>           category edns-disabled { null; };
> >>           };
> >> key dhcpupdate {
> >>           algorithm hmac-md5;
> >>           secret "ddjsdfruifhrfr88r8rr5544==";
> >>           };
> >>
> >> Thanks in advance.

-- 
Barry Margolin
Arlington, MA