Hi
It seems nsupdate.exe in 9.6.1-P1 does not properly locate IPv6 nameservers.
C:\Temp\bind-9.6.1-P1>dig +short ns-v6-1.chaz6.com. in
2001:16d8:dd22:38::2
2001:16d8:ee0f:38::2
C:\Temp\bind-9.6.1-P1>nsupdate
> server 2001:16d8:dd22:38::2
> update add localhost.dyn.ipv6.chaz6.com. 7200 IN A
On 22/11/09 21:01, Chris Buxton wrote:
Change the zone from type forward to type slave, and add
allow-update-forwarding.
zone "dyn.example.com." {
type slave;
masters { ::1; };
allow-update-forwarding { local-networks; };
};
Then in the external-in view, change allow-up
On Nov 22, 2009, at 1:49 AM, Chris Hills wrote:
> Hi
>
> I have a zone "example.com" configured in two views, internal-in and
> external-in. I have a dynamic zone "dyn.example.com" configured only as an
> external zone. Internal clients can lookup hosts in dyn.example.com, but
> cannot update (
Pamela Rock wrote:
> Hit the wrong key, sorry about that...
>
> I've got a closed lab testing BIND and I've got an interesting problem with
> IPv6 queries. Now I have 3 systems all running IPv4 and IPv6. IPv4 queries
> work fine across all systems. IPv6 UDP queries work fine as well. When I
Hit the wrong key, sorry about that...
I've got a closed lab testing BIND and I've got an interesting problem with
IPv6 queries. Now I have 3 systems all running IPv4 and IPv6. IPv4 queries
work fine across all systems. IPv6 UDP queries work fine as well. When I test
IPv6 TCP queries I get
I've got closed lab testing BIND and I've got an interesting problem with IPv6
queries. Now I have 3 systems all running IPv4 and IPv6. IPv4 queries work
fine across all systems. IPv6 UDP queries
___
bind-users mailing list
bind-users@lists.
Hi
I have a zone "example.com" configured in two views, internal-in and
external-in. I have a dynamic zone "dyn.example.com" configured only as
an external zone. Internal clients can lookup hosts in dyn.example.com,
but cannot update ("not authorised") as the updates are matched by the
zone i
7 matches
Mail list logo
