auto-trust-anchor-file

Hello,

Is there anyway how to check auto-trust-anchor-file ?
I Install new unbound 1.7.3 and getting error like below :

/usr/local/etc/unbound/unbound.conf:472: error: syntax error

read /usr/local/etc/unbound/unbound.conf failed: 1 errors in configuration file

[1536562934] unbound[1772:0] fatal error: Could not read config file: /usr/local/etc/unbound/unbound.conf

When i see this error belong to : auto-trust-anchor-file: “/usr/local/etc/unbound/root.key”
I have check the permission and path its read and writeable for unbound.
I have remove the root.key and starting unbound-anchor.

What else can i do ?
Thank you in advance.

Hi Batossai,

Hello,

Is there anyway how to check auto-trust-anchor-file ?
I Install new unbound 1.7.3 and getting error like below :

/usr/local/etc/unbound/unbound.conf:472: error: syntax error

read /usr/local/etc/unbound/unbound.conf failed: 1 errors in
configuration file

[1536562934] unbound[1772:0] fatal error: Could not read config file:
/usr/local/etc/unbound/unbound.conf

When i see this error belong to : auto-trust-anchor-file:
"/usr/local/etc/unbound/root.key"
I have check the permission and path its read and writeable for unbound.
I have remove the root.key and starting unbound-anchor.

What else can i do ?
Thank you in advance.

The error it reports is not in the root.key file, but in the
unbound.conf file. There is some weird or missing character(s) in
unbound.conf, line 472. Perhaps invisible UTF characters? The
statement you show look allright, and if you remove it you have (I
guess) also removed the syntax error.

So the permissions on root.key are not the issue, but the
auto-trust-anchor-file statement in that unbound.conf file is misspelled
or something along those lines; perhaps ; at the end of line or wrong
quotes? Syntax error is printed by the lexer, and it (also) deals with
unexpected characters and that sort of stuff.

Best regards, Wouter

Hi,

Actually at line 472 i just uncomment defaul unbound.conf.
I have try to type it one by one, and still found the same error.

Check the lines before, maybe some ending character is missing.