On Sun, 2018-01-14 at 19:30 +0000, Alex Lasoriti wrote: > On 2018-01-14 17:20, Ian Zimmerman wrote: > > > > On 2018-01-14 17:07, Per Jessen wrote: > > > > > > > > AFAIK, bind does not accept NS records with CNAMEs, only A or > > > AAAA > > > records. It looks like spamhaus updated their nameserver config > > > and > > > added cloudflare by way of CNAME. > Hi all, > > this was a "sunday experiment" done on only one of our current 20 NS > records, > addressing in total about 75 nameservers. So it affected more of > less 5% of the > lookups (that did not fail, just had to be retried). It's my fault > and you > can blame me personally :) We are now back to the normal setup - the > CNAME > is no longer there and will not come back. Sorry for the extra noise > in > logs; I am quite confident that nothing was really seriously broken, > but I understand that it may have annoyed some people. > Thanks for the explanation Alex, I wasn't annoyed, just baffled. As you said, everything is back to normal.
Chris -- Chris KeyID 0xE372A7DA98E6705C 31.11972; -97.90167 (Elev. 1092 ft) 15:18:27 up 4 days, 6:06, 1 user, load average: 0.21, 0.25, 0.30 Description: Ubuntu 16.04.3 LTS, kernel 4.13.0-26-generic
signature.asc
Description: This is a digitally signed message part
