-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
DNS resolving 127.0.0.1 for my domain #470
Comments
@BaldEagleX02 what's the exact hostname just in case? We'll try reproducing it on our end. |
I have found out that when I dig my domain (mail.cfvmail.cf) I get the right IP but from your logs I see 127.0.0.1 and my browser can't connect. |
Chrome? It might be caching old DNS records, try clearing its own cache: |
I retried and it worked. Firefox was caching DNS records so when I changed the rules they weren't working as expected. |
Hoverer before I had changed the rules it was returning 127.0.0.1. Why? |
The problem is solved anyway |
@BaldEagleX02
Is it possible that you had the same hostname listed in custom rules or additional hosts-format filters that you've added in the settings? Thanks for reporting the issue either way ^.^ |
I have installed AdGuard Home on my Raspberry Pi.
When I resolve the RPi's hostname using the installed DNS it returns 127.0.0.1, so I tried setting
RPiPublicIP RPiHostname
in my rules but it doesn't work.I also checked the .yaml file but it is OK (my rule is installed correctly).
What can I do to fix this issue?
The text was updated successfully, but these errors were encountered: