Custom DNS Entries KNOT Resolver

Hi everyone,

I need some custom DNS and MX records for my local network.

Since switching to Knot Resolver, my previous configuration no longer works, of course.

So I had to adjust the Knot Resolver configuration files.

The problem is that these files include the note “will be overwritten during an update.”

Is there another best practice for accomplishing this?

Best regards

You should be able to add your records to /etc/knot-resolver/config.yaml as described here:

Then reload the configuration with:
/etc/init.d/knot-resolver reload

However, I haven’t found a local configuration file that can be customized like Unbound’s local configuration.

Well that what I did, but at the top of that file is written:

Knot Resolver Configuration File For IPFire

DO NOT EDIT as any changes will be overwritten

So thats not a long term solution I guess :wink:

Perhaps you could add a script to /etc/sysconfig/rc.local to automate this update at startup.
I don’t see any other solution for the moment.

Or perhaps this should be submitted as a feature request?

Yes, a feature request would be great.

Could you create one for me or where I have to do that?

best would be if it could be done in the ui, or at last in a easy way in the config-files, that it will be persistet.

I think Edit Host GUI page is what you are looking for.

It may take while before dns records update to clients but you can try to clear clients dns cache, reconnect or reboot etc. to speed up the process.

and how to create MX-Records there?

I need them as well as you can see in the initial request :wink:

I’m just another user, like you.
My reports are not always understood and are often rejected, so I think you could submit the request yourself.

To do that, the IPFire developers would need to be convinced that your use case would also benefit other users.
Can I request features here?

Or if you think it’s a bug

OK, i will :slight_smile:

I think it is a feature request.
From the history of the core versions, it is a lack of functionality. Unbound config allowed a local config.
But the configuration of knot isn’t done by easy plain text files. Knot uses YAML and LUA, therefore it isn’t just an addition of include knotr.cfg.local to the main config file ( written by the WUI ).

I opened a bug, lets see. Cause before it was possible do create static mx records,…
Now not anymore so i think its a bug.

I think it is possible to create these records now, also.
But the process of including that local manual extensions may be more complex and isn’t implemented yet.