RE: when i check resolver.log just now , i found some error info about AAAA ( ipv6)

To be clear, "turning off" IPv6 in named (via the -4 flag or other means), doesn't mean named won't try to resolve any records, especially if one of your (presumably IPv6-enabled) clients requests them. So, even with IPv6 "turned off", if there are nameservers on the Internet that -- for

Re: when i check resolver.log just now , i found some error info about AAAA ( ipv6)

In article , "Darcy Kevin (FCA)" wrote: > Really, there's no excuse, in this day and age, for a DNS-serving device -- > even a load-balancer pretending to be a nameserver -- to botch its responses > to

RE: when i check resolver.log just now , i found some error info about AAAA ( ipv6)

I don't know about other GSLBs, but Cisco GSSes could be made to respond relatively sanely, with some careful configuration. We had to set up a "shadow" version of each GSLB-delegated subzone on BIND, and the GSSes would proxy all queries they couldn't handle themselves to/from this "shadow"

Re: when i check resolver.log just now , i found some error info about AAAA ( ipv6)

In message , "Darcy Kevin (FCA)" writes: > I don't know about other GSLBs, but Cisco GSSes could be made to respond > relatively sanely, with some careful configuration. We had to set up a > "shadow" version of each GSLB-delegated subzone on