This is a discussion on Re: IPV6 forwarders problem within the Bind Users forums, part of the DNS and Related Forums category; >>>>> On Thu, 1 Jul 2004 07:46:40 -0400, >>>>> "...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
>>>>> 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 well > as a combination of differnet ipv4 addresses with no luck. > I've also tried pointing the forwarders to an true ipv6 dns server and > my server still does not resolve. I'm only able to resolve if I 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 |