Bug for all IPv6 DNS server problems
*** Bug 426978 has been marked as a duplicate of this bug. ***
*** Bug 426977 has been marked as a duplicate of this bug. ***
*** Bug 426976 has been marked as a duplicate of this bug. ***
Machine 1: IPV6tester, FreeBSD, 10.66.65.104
Machine 2: IPv6testee, RHEL 5.1, 10.66.65.103
(1) the two interfaces is not used for testing DNSv6, but used for your remotely
(2) the two interfaces used for testing DNSv6 are rl0(192.168.0.10 freebsd6.2)
and eth0 (192.168.0.11 rhel5.1)
(3) the topology above is a logical topology, TAHI test suites will create it
note that the network configuration you saw last time is used for IPv6 DNS test.
now, you can login IPV6tester by ssh 10.66.65.104 and IPV6testee by ssh
10.66.65.103, and look at the ipv6 DNS test environment.
the two interfaces used for ipv6 DNS test are:
Machine 1: IPV6tester, FreeBSD, rl0 , 192.168.0.11
Machine 2: IPv6testee, RHEL 5.1, eth0, 192.168.0.10
if you want to view the test report of DNSv6 client, pls view the url below:
if you want to view the test report of DNSv6 server, pls view the url below:
Thanks for your info. I already checked all problems in IPv6 only environment
(RHEL5.1 and Fedora 8 machines). None of reported problems are related to IPv6.
Only one unexpected thing I found has been reported to upstream and is not IPv6
related (http://marc.info/?l=bind-users&m=120031166104693&w=2, about secondary
zones expiration). We will close this bug because BIND works in IPv6 environment
perfectly as server.