On Jul 28, 2011, at 8:27 AM, uifid...@gmail.com wrote:
> I'm trying to config a bind server which could answering queries (at
> least from 127.0.0.1 and 192.168.18.128) like "dig kia.czj" but I
> failed to. perhaps my ignorance about match-clients and
> match-destinations statements failed my att
On Jul 28, 2011, at 4:39 AM, Daniel McDonald wrote:
> On 7/28/11 3:16 AM, "uifid...@gmail.com" wrote:
>
>> my czj.zone
>> $TTL 86400
>> czj. IN SOA localhost. root.localhost. (
>> 1997022700 ; Serial
>> 2880
>
> -Original Message-
> From: bind-users-bounces+jlightner=water@lists.isc.org
> [mailto:bind-users-bounces+jlightner=water....@lists.isc.org] On Behalf Of
> Danilo Godec
> Sent: Friday, July 29, 2011 5:38 AM
> To: bind-users@lists.isc.org
> Subject: Re: no servers
On Behalf Of
Danilo Godec
Sent: Friday, July 29, 2011 5:38 AM
To: bind-users@lists.isc.org
Subject: Re: no servers could be reached
On 07/29/2011 10:36 AM, uifid...@gmail.com wrote:
> the zones file is located at /var/named/chroot/var/named/domainx.zones.
> #cat var/domainx.zone
On 07/29/2011 10:36 AM, uifid...@gmail.com wrote:
the zones file is located at /var/named/chroot/var/named/domainx.zones.
#cat var/domainx.zones should be var/named/domainx.zones
#cat var/domainx.zone should be var/named/domain.zone
Sorry for my typo.
So this should be OK then.
Your view state
the zones file is located at /var/named/chroot/var/named/domainx.zones.
#cat var/domainx.zones should be var/named/domainx.zones
#cat var/domainx.zone should be var/named/domain.zone
Sorry for my typo.
2011/7/29 Danilo Godec :
> On 07/29/2011 08:17 AM, uifid...@gmail.com wrote:
>>
>> cat var/named
On 07/29/2011 08:17 AM, uifid...@gmail.com wrote:
cat var/named/named.conf
//
// named.caching-nameserver.conf
//
options {
listen-on port 53 { 192.168.18.128; 127.0.0.1; };
listen-on-v6 port 53 { ::1; };
directory "/var/named";
dump-file "/var/named/da
#hostname
CentOS3
Is it matter?
2011/7/29 uifid...@gmail.com :
> still get "no servers could be reached", need help.
>
> #dig @127.0.0.1 nsc1.domainx
>
> ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5 <<>> @127.0.0.1 nsc1.domainx.
> ; (1 server found)
> ;; global options: printcmd
> ;; connection ti
still get "no servers could be reached", need help.
#dig @127.0.0.1 nsc1.domainx
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5 <<>> @127.0.0.1 nsc1.domainx.
; (1 server found)
;; global options: printcmd
;; connection timed out; no servers could be reached
cat /etc/resolv.conf
; generated by /sbin
Sorry, it's a typo in the maillist, but not in my file system. My
resolv.conf is in the right place.
2011/7/29 Michael McNally :
> On 7/28/11 12:16 AM, uifid...@gmail.com wrote:
>>
>> my /etc/resolve.conf
>
> Note: ^^^
>>
>> named-checkzone named-checkconf passed, I suppose the configure w
-users@lists.isc.org
Subject: Re: no servers could be reached
On 7/28/11 12:16 AM, uifid...@gmail.com wrote:
> my /etc/resolve.conf
Note: ^^^
>
> named-checkzone named-checkconf passed, I suppose the configure works
> but only get no servers could be reached.What's wrong with
On 7/28/11 12:16 AM, uifid...@gmail.com wrote:
my /etc/resolve.conf
Note: ^^^
named-checkzone named-checkconf passed, I suppose the configure works
but only get no servers could be reached.What's wrong with my config?
Your resolv.conf is in the wrong place. Let's see what happens w
I'm trying to config a bind server which could answering queries (at
least from 127.0.0.1 and 192.168.18.128) like "dig kia.czj" but I
failed to. perhaps my ignorance about match-clients and
match-destinations statements failed my attempt, or more likely, "SOA
and NS of localhost. seems wrong". I
On 7/28/2011 4:16 AM, uifid...@gmail.com wrote:
> view localhost_resolver {
> match-clients { localhost; };
> match-destinations { localhost; };
> recursion yes;
> include "/etc/named.rfc1912.zones";
> };
> view czj {
> match-clients { 192.168.18.128; localhost
On 7/28/11 3:16 AM, "uifid...@gmail.com" wrote:
> my czj.zone
> $TTL 86400
> czj. IN SOA localhost. root.localhost. (
> 1997022700 ; Serial
> 28800 ; Refresh
>
15 matches
Mail list logo
