On 11/04/2018 11:48 AM, Benny Pedersen wrote:
Nov 3 03:22:50 localhost named[2301]: connection refused resolving '72_scores.cf/NS/IN': 2a04:1b00:6::1#53 Nov 3 03:22:50 localhost named[2301]: connection refused resolving '72_scores.cf/A/IN': 2a04:1b00:6::1#53 Nov 3 14:59:26 localhost named[2301]: connection refused resolving '20_misc.cf/NS/IN': 2a04:1b00:4::1#53
These are errors from named about not being able to connect to remote DNS servers. They have nothing to do with SpamAssassin or any of it's files.
Nov 3 14:59:26 localhost named[2301]: connection refused resolving '20_misc.cf/A/IN': 2a04:1b00:4::1#53
named is stating that it's connection to 2a04:1b00:4::1 was refused when trying to resolve an A record (INternet class) for the domain name "20_misc.cf".
That is DNS and has nothing to do with filenames that SpamAssassin is using.
so ns.cf blocks my named now,
I don't think so.
i cant resolve any cf domains with it
You may have a different issue resolving cf domains. But I HIGHLY doubt it has anything to do with the names of files.
Also, do you know that you can't resolve /any/ cf domains? What cf domains, other than the ones listed as refusing connections, have you tried?
The simple fact that named is saying that it can't connect to 2a04:1b00:4::1 as the DNS server for the 20_misc.cf domain tells me that it was able to communicate with the DNS servers for the cf top level domain to be able to find the DNS server for the 20_misc.cf domain.
Also, save for the following d.ns.cf logs, none of the other domain names are under the ns.cf domain name.
Nov 2 03:14:10 localhost named[2301]: connection refused resolving 'd.ns.cf/A/IN': 2a04:1b00:4::1#53 Nov 2 03:14:10 localhost named[2301]: connection refused resolving 'd.ns.cf/AAAA/IN': 2a04:1b00:4::1#53
I *REALLY* don't think your errors are coming from the fact that a config file has name collision with a domain name.
That's like saying your kid can't use the name "mom" because it has a different meaning in a different language. You might not like it, and thus choose not to use it. But there is nothing preventing it's use.
time to change imho
What exactly do you want to change? And why? Please show evidence that the name of the file is actually the problem.
All of that said, I do think that you have a problem. It looks like something is trying to do a DNS lookup of the name of config files. Something that I strongly doubt should be done.
-- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
