Hello,
At this point I am hoping that somebody might have a workaround so that we can
exclude domains from this behavior if they are broken on the far end. Does
anybody have a workaround for this?
We are a small ISP and run BIND compiled from source. We currently run 9.16.x
Every time we try to
Doing some checking on this locally trying to understand what may be
happening. I stumbled across this:
view.bankeasy.com is a cname to view.gtm.bankeasy.com
However if I try to dig for gtm.bankeasy.com that is where the oddities
show up:
dig @ns1.dakotanames.com gtm.bankeasy.com
; <<>> Di
Well if the bank is stupid enough to use NS records that point to nameservers
that
do not exist on the internet then lookups FAIL.
% dig ns gtm.bankeasy.com
;; BADCOOKIE, retrying.
; <<>> DiG 9.19.18-dev <<>> ns gtm.bankeasy.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUER
3 matches
Mail list logo