-
-
Notifications
You must be signed in to change notification settings - Fork 197
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
conditional_upstream timeouts #1403
Comments
Hi, The special use domains resolver is after the conditional one in the resolver chain, so requests handled by the conditional one never reach the SUDN resolver. I think you're just getting real time outs. You can try increasing the upstream timeout, and maybe doing manual tests from where blocky runs when you see timeouts in the logs. |
added the timeouts to the upstream.. don't see a timeouts for conditional.. (changed from default 2s to 10s)
still see these:
again with conditional enabled I no longer see speical use entries..
|
Yes the Is it all requests that timeout?
Yeah that's for the same reason: the conditional resolver handles the request, so the SUDN one never sees it. |
Seems like your container can't reach the outbound network. In such a case I would start with explicitly creating a new docker network and using it as default for the blocky container. |
172.19.0.2 was blocky now blocky is network host mode.. with no conditional statement, those errors never showed in the logs.. (let me try and say this another way.. )
The above stops showing when I enable this is in blocky..
(conditional enabled and restart)
(conditional disabled and restart)
and then I get these:
I'm good with the Mikrotik DNS server is a problem.. but then where are those Speical entries.. But when I dig the mikrotik dns server it has answers and seems to answer in an acceptable time. the 88.1 just forwards to the 88.254 for recursion.. (again) without the conditional I don't have those errors.. AND without the conditional I don't ever see 'Special' entries in the DNS anymore.. |
Can you please explain what you're doing, what you expect to see, and what you're seeing for this?
IIUC 88.254 is blocky. Any chance there's a query loop? Another test you could do is change the router to not query blocky at all, but a third party resolver, and configure blocky to use the router as sole upstream. |
I read through this issue again and
Sounds the most likely to me. Have you checked the logs of 1 and 254 for a resolution loop? |
docker image.. seem to be the same with the :latest tag as well..
I get tons of these:
Restarting without conditional_upstream
88.1 is serving functional dns (afaict)
config.yml:
fwiw, it is a mikrotik router with its own dns server.. 7.14 of the OS.. I do not know how it reacts to tcp queries (drill -t responds as it should on cmd line..)
I am not sure if I am doing something incorrect in my configuration..
I tried to manually define things to rule out default settings and such..
This is my commented out conditional section..
(as always)
Thank you in advance.
The text was updated successfully, but these errors were encountered: