Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

/etc/unbound/unbound.conf.d/hosts.conf is repeatedly corrupted #399

Open
mpuz opened this issue Oct 1, 2023 · 2 comments
Open

/etc/unbound/unbound.conf.d/hosts.conf is repeatedly corrupted #399

mpuz opened this issue Oct 1, 2023 · 2 comments

Comments

@mpuz
Copy link

mpuz commented Oct 1, 2023 •
edited

/etc/unbound/unbound.conf.d/hosts.conf is being corrupt or contains symbols that can't be read by unbound
(probably "<", ">")
and cause unbound error and slowing down of all connections

Ubuntu server 20
@ManniLoe
Copy link

The hosts.conf File for unbound has incorrect content because one of the used blocklists (UNBOUND_CONFIG_HOST_URL) "https://combinatronics.io/complexorganizations/content-blocker/main/assets/hosts" ist not reachable.

cat hosts.conf

local-zone: "<html>^M" always_refuse
local-zone: "<head><title>301" always_refuse
local-zone: "<body>^M" always_refuse
local-zone: "<center><h1>301" always_refuse
local-zone: "<hr><center>nginx/1.22.1</center>^M" always_refuse
local-zone: "</body>^M" always_refuse
local-zone: "</html>^M" always_refuse

@Prajwal-Koirala
Copy link
Member

Update: Issue Resolved

Dear,

I'm pleased to inform you that the issue you reported has been resolved. We have implemented the necessary changes, and we believe the problem is now fixed.

Please verify the fix:

We kindly request your assistance in verifying the resolution. Could you please perform the following steps to confirm that the issue is resolved on your end?

  1. [List the specific steps or actions the user should take to verify the fix.]

  2. [Provide any additional information or guidance that may be relevant to the verification process.]

If the issue is indeed resolved, please reply to this comment with a confirmation. If you encounter any issues or have further questions, please don't hesitate to let us know, and we will be happy to assist you further.

Thank you for your patience and for reporting this issue to us. We greatly appreciate your contributions to improving our project.

Best regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ManniLoe @mpuz @Prajwal-Koirala