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

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

at horrible platform. - Kevin -Original Message- From: bind-users-boun...@lists.isc.org [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Barry Margolin Sent: Wednesday, April 13, 2016 4:45 PM To: comp-protocols-dns-b...@isc.org Subject: Re: when i check resolver.log just now

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)

s.isc.org] On Behalf Of Mark Andrews Sent: Wednesday, April 13, 2016 12:33 AM To: johnzeng Cc: bind-us...@isc.org Subject: Re: when i check resolver.log just now , i found some error info about ( ipv6) Just another broken nameserver that doesn't handle queries correctly. It ans

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

Just another broken nameserver that doesn't handle queries correctly. It answers authoritatively for dlb.g5.letvlb.com/A but returns a referral for dlb.g5.letvlb.com/ with unrelated additional records. Mark % dig dlb.g5.letvlb.com @106.38.226.245 ; <<>> DiG 9.11.0a1 <<>>