Subj : Re: DNS Nodelist available for fsxnet
To   : Digital Man
From : deon
Date : Fri Nov 17 2023 02:25 pm

  Re: Re: DNS Nodelist available for fsxnet
  By: Digital Man to deon on Mon Nov 13 2023 08:06 pm

Howdy,

 > It appears BIND doesn't like your nameserver configuration:
 >
 > 2023-11-13T11:28:13.722844-08:00 git named[897]: skipping nameserver
 > 'clrghouz.bbs.dege.au' because it is a CNAME, while resolving
 > 'f183.n1.z21.fsxnet.nz/TXT'

Its interesting, because I use bind as well (not authorative for the domains in question), and dont have any trouble. Its probably because my bind forwards to upstream DNSes that handle it OK.

I think this is one of those cases, where the spec was written in 1997 and hasnt modernised to today's use of the internet. I recall great debate about this around 2009, because MX records too shouldnt have CNAMEs and there were a few that had (IMHO) valid opinions of why it can/should. Bind does have an option for it to accept CNAME MX records, havent tested it to see if it accepts CNAME NS records (or there is another override).

The implementation of CNAMEs can be useful in todays hosted and distributed world, and I know many (major?) DNS servers can handle it (evident by the number of queries making it to me).

Anyway, I've asked Paul to change to use my CNAME target for z21 (which does have the A/AAAA records), which will hopefully help those that are seeing the server errors.


....лоеп
--- SBBSecho 3.20-Linux
 * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

.