Kitz Forum

Internet => General Internet => Topic started by: Weaver on June 26, 2020, 10:51:20 AM

Title: Error reported by BIND in DNS config
Post by: Weaver on June 26, 2020, 10:51:20 AM
I got an email from my ISP Andrews and Arnold telling me that because I had messed up some of the DNS config for one of my domains, BIND had reported an error and would not load. The problem is to do with the rules for coexistence of CNAME records with other records. I read RFC1912 section 2.4 but I’m too stupid to understand it. Could anyone help me at a level suitable for an utter wally such as myself?

I don’t know what the rules related to CNAMEs are here. I wish I could write some tool to check the AA DNS config myself. I don’t see a way of downloading all of the DNS config from clueless but perhaps good old copy-paste would get me there, and then it would just be a matter of dull grunt work if I only knew what the required check rules are.

It’s a shame that AA’s clueless.aa.net.uk web server UI doesn’t do the required CNAME-related legality checks for me.
Title: Re: Error reported by BIND in DNS config
Post by: d2d4j on June 26, 2020, 11:32:46 AM
Hi

@weaver - you need give more details if you want help

I would think aa would have provided the failed cname so should be easy to spot/correct

Our ns/dns would not allow dns errors so it would not load

Many thanks

John
Title: Re: Error reported by BIND in DNS config
Post by: Weaver on June 26, 2020, 11:58:14 AM
AA did point me to the CNAMEs that are giving the problem, I emailed back asking for clarification. i can’t give you details yet as I don’t understand enough about the issue.

My question is just as much about that RFC, which I simply don’t understand.

From what I can see, it’s some rule about existence of other records being disallowed where either the lhs or rhs of a CNAME (which?) breaks some rule relating to some other record’s content or existence. The RFC provides an example but I’m too stupid to understand it, and also I don’t know why it should be a problem whatever it is.

I didn’t know about this problem, never experienced it before somehow. I admit that I have been overusing CNAMEs for ease of maintainability so i would ideally only have to change things in one place, not change a whole load of duplicated references to things.



I didn’t get any improvement in my understanding as the reply came back from AA saying that I had fixed the errors, which I presume I must have managed to do because of a partial cull on CNAMEs but it could be some other change i have made very recently, but anyway I now have no idea what I did to fix the issue.

I’m told that a new yet-to-be-released version of the clueless.aa.net.uk AA control server will do the required checking.
Title: Re: Error reported by BIND in DNS config
Post by: Chrysalis on June 27, 2020, 05:46:07 AM
until can see the records in question, its hard to provide help, its likely a syntax error.
Title: Re: Error reported by BIND in DNS config
Post by: Weaver on June 27, 2020, 11:45:37 PM
hi chrys - this is entered through AA’S web ui management control panel, so not directly interacting with BIND.

I’m trying to understand that RFC example here and failing.