Alexander Kirillov <[EMAIL PROTECTED]> writes:
> ;BIND DUMP V8
> $ORIGIN 10.10.IN-ADDR.ARPA.
> 0 3600 IN SOA baikal.iproducts.test.
> root.baikal.iproducts.test. (
> 20050421 3600 900 3600000 3600 ) ;Cl=5
> 3600 IN NS baikal.iproducts.test. ;Cl=5
> $ORIGIN 0.10.10.IN-ADDR.ARPA.
> 2 3600 IN PTR volga.iproducts.test. ;Cl=5
> 1 3600 IN PTR baikal.iproducts.test. ;Cl=5
> 3 3600 IN PTR g40.iproducts.test. ;Cl=5
> ;10 3600 IN PTR wisla.iproducts.test. ;Cl=5
[...]
Jo Are Rosland <[EMAIL PROTECTED]>:writes:
> Hmm. I guess you could try to define the zone 168.192.in-addr.arpa
> instead. Then you'd have this in named.conf:
> zone "168.192.in-addr.arpa" IN \
> { type master; file "pri/168.192.zone"; notify no; };
While both of these suggestions work and both were very helpfull in
helping me gain some more detailed knowledge of the working of bind I
got a suggestion on the bind newsgroup where I also had a thread on
this subject that is much simpler than either way discussed in this
thread.
Both of you spotted this error in db.192.168.1
IN NS reader
needed to say
IN NS reader.local.lan.
Then with this further change:
From:
192.168.1.2 IN PTR rdmz.local.lan.
192.168.1.1 IN PTR fwdmz.local.lan.
to
2 IN PTR rdmz.local.lan.
1 IN PTR fwdmz.local.lan.
The whole file:
>From this db.192.168.1
==================== 8< ===============
$TTL 1D
@ IN SOA reader.local.lan. reader.reader.local.lan. (
200405190 ; serial
28800 ; refresh (8 hours)
14400 ; retry (4 hours)
2419200 ; expire (4 weeks)
86400 ; minimum (1 day)
)
;
; Name servers (The name '@' is implied)
;
IN NS reader
;
; Addresses point to canonical names
;
192.168.1.2 IN PTR rdmz.local.lan.
192.168.1.1 IN PTR fwdmz.local.lan.
To this db.192.168.1
==================== 8< ===============
$TTL 1D
@ IN SOA reader.local.lan. reader.reader.local.lan. (
200405190 ; serial
28800 ; refresh (8 hours)
14400 ; retry (4 hours)
2419200 ; expire (4 weeks)
86400 ; minimum (1 day)
)
;
; Name servers (The name '@' is implied)
;
IN NS reader.local.lan.
;
; Addresses point to canonical names
;
2 IN PTR rdmz.local.lan.
1 IN PTR fwdmz.local.lan.
Just those small changes is all that was needed for the setup to work
with no errors and nslookup knows about all hostnames both alpha and
numeric. The more far reaching changes discussed in this thread were
not necessary.
dig -x 192.168.1 any
(Without implimenting Jo Are suggestions about hostnaming in
db.local.lan (which are now implemented ... thanks Jo)
Now shows the expected results.
; <<>> DiG 9.3.2 <<>> -x 192.168.1 any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59543
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
;; QUESTION SECTION:
;1.168.192.in-addr.arpa. IN ANY
;; ANSWER SECTION:
1.168.192.in-addr.arpa. 86400 IN SOA reader.local.lan.
reader.reader.local.lan. 200405190 28800 14400 2419200 86400
1.168.192.in-addr.arpa. 86400 IN NS reader.local.lan.
;; ADDITIONAL SECTION:
reader.local.lan. 86400 IN A 192.168.1.2
reader.local.lan. 86400 IN A 192.168.0.4
;; Query time: 11 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Mar 6 08:45:20 2006
;; MSG SIZE rcvd: 145
--
gentoo-user@gentoo.org mailing list
