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.

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

local DNS #1551

Closed
ghost opened this issue Apr 6, 2020 · 4 comments
Closed

local DNS #1551

ghost opened this issue Apr 6, 2020 · 4 comments
Labels

Comments

@ghost
Copy link

ghost commented Apr 6, 2020

Would it be possible to add the possibility of storing IP for a certain time to AdGuardHome to become a local DNS in all respects?

@ameshkov
Copy link
Member

ameshkov commented Apr 7, 2020

Could you please elaborate, I don't fully understand the question. What IP you are talking about?

@ghost
Copy link
Author

ghost commented Apr 7, 2020

It would be nice if AdGuard Home allowed to keep a mini database containing all the queries that have been resolved in the last 24 hours maybe, or even more.
Doing so would save you from having to query for hostname resolution over and over again if you visit the same site.
It would be a feature that if implemented ad hoc would bring the advantage of not having to resolve hostnames every time but would be enough once to have the ip already in the mini database, perhaps associated with the domain to which it is connected.
Doing so would save you milliseconds in asking DNS as CloudFlare which is the IP of a machine to which you have to connect, for example.
All this would make AdGuard Home an even more complete DNS server! I think that an example of this can be had with the Bind program for linux, let me know if it can be done, it would be magnificent, the work you have done / do with this git is already so beautiful, but I think this suggestion would still improve plus the potential!

@ameshkov
Copy link
Member

ameshkov commented Apr 8, 2020

Well, it sounds like a cache to me, and AGH already has one.

The difference is that DNS cache works differently, it stores data for a time-to-live period specified in every DNS record. The good news is that in AGH you can override this and set whatever TTL you'd like to have, but this will be available in v0.102 (see #1214 )

@ghost
Copy link
Author

ghost commented Apr 8, 2020

Perfect, if it is already available I have not noticed, thanks for the availability and good work!

@ghost ghost closed this as completed Apr 8, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant