RE: IPV6 forwarders problem

I've notice the following symptoms. If the issue a dig, dig www.aol.com
@bluehawk, command from an ipv4 client to the ipv6/ipv4 server I'm able
to resolve addresses. Now when I dig from a ipv6 client to the ipv6/ipv4
server I'm not able to resolve.

I check the -g option and I could not see anything useful. Here goes:

Jul 01 08:40:38.084 loading configuration from '/etc/named.conf'
Jul 01 08:40:38.086 listening on IPv6 interfaces, port 53
Jul 01 08:40:38.087 listening on IPv4 interface lo, 127.0.0.1#53
Jul 01 08:40:38.087 binding TCP socket: address in use
Jul 01 08:40:38.088 listening on IPv4 interface eth0, 10.10.7.249#53
Jul 01 08:40:38.088 binding TCP socket: address in use
Jul 01 08:40:38.093 command channel listening on 127.0.0.1#953
Jul 01 08:40:38.093 ignoring config file logging statement due to -g
option
Jul 01 08:40:38.097 dns_master_load:
crl-subnet/ipv6.crl.comp.com.arpa:10: ipv6.crl.comp.com: not at top of
zone
Jul 01 08:40:38.098 zone ipv6.crl.comp.com.arpa/IN: loading master file
crl-subnet/ipv6.crl.comp.com.arpa: not at top of zone
Jul 01 08:40:38.099 dns_master_load:
crl-subnet/ipv6.crl.comp.com.arpa:10: ipv6.crl.comp.com: not at top of
zone
Jul 01 08:40:38.099 zone ipv6.crl.hol.comp.com.arpa/IN: loading master
file crl-subnet/ipv6.crl.comp.com.arpa: not at top of zone
Jul 01 08:40:38.101 zone 0.0.127.in-addr.arpa/IN: loaded serial
2004063001
Jul 01 08:40:38.103 zone ipv6.crl.comp.com/IN: loaded serial 2004063009
Jul 01 08:40:38.105 zone ipv6.crl.hol.comp.com/IN: loaded serial
2004063009
Jul 01 08:40:38.106 zone localhost/IN: loaded serial 2004063000
Jul 01 08:40:38.107 running
Jul 01 08:40:38.107 zone ipv6.crl.comp.com/IN: sending notifies (serial
2004063009)
Jul 01 08:40:38.108 zone ipv6.crl.hol.comp.com/IN: sending notifies
(serial 2004063009)
Jul 01 08:40:38.109 received notify for zone 'ipv6.crl.comp.com'
Jul 01 08:40:38.611 received notify for zone 'ipv6.crl.comp.com'
Jul 01 08:40:38.611 received notify for zone 'ipv6.crl.hol.comp.com'
Jul 01 08:40:38.612 received notify for zone 'ipv6.crl.hol.comp.com'


-----Original Message-----
From: jinmei@isl.rdc.toshiba.co.jp [mailto:jinmei@isl.rdc.toshiba.co.jp]

Sent: Thursday, July 01, 2004 8:20 AM
To: Baccari, Lou
Cc: comp-protocols-dns-bind@isc.org
Subject: Re: IPV6 forwarders problem


>>>>> On Thu, 1 Jul 2004 07:46:40 -0400,
>>>>> "Baccari, Lou" <lou.baccari@hp.com> said:

> Thanks for your suggestion and I have tried your recommendation as=20
> well as a combination of differnet ipv4 addresses with no luck.

> I've also tried pointing the forwarders to an true ipv6 dns server=20
> and my server still does not resolve. I'm only able to resolve if I=20
> disable 'liston-on-v6'.

> Any other suggestions?

As I said in the previous message, please try to run named with the -g
option. Then it will provide some initial log messages to stderr like
this:

% ./named -c named.conf -g
Jul 01 21:19:17.344 starting BIND 9.2.4rc4 -c named.conf -g
Jul 01 21:19:17.349 using 1 CPU
Jul 01 21:19:17.356 loading configuration from
'/home/jinmei/src/bind-9.2.4rc4/bin/named/named.conf'
Jul 01 21:19:17.362 listening on IPv6 interfaces, port 9053
Jul 01 21:19:17.367 listening on IPv4 interface fxp0,
203.178.141.201#9053 Jul 01 21:19:17.371 listening on IPv4 interface
lo0, 127.0.0.1#9053 ...

It *may* have useful information to diagnose the issue.

JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba
Corp.
jinmei@isl.rdc.toshiba.co.jp