Replies: 3 comments 9 replies
-
Do "any services hosted on the cloud" have the same domain name? |
Beta Was this translation helpful? Give feedback.
-
If I am reading this correctly: blocky/resolver/rewriter_resolver.go Lines 59 to 85 in 01b7947 Here in line 78, we revert the request back to the original, line 80 will be true since my DNS server indeed returned No Answer, shouldn't line 84 fallback to the parallelresolver and resolve with my default resolver? Lines 408 to 409 in 01b7947 Which means, should this not work already and send the original request to uptime.public.site to the default resolver? |
Beta Was this translation helpful? Give feedback.
-
Just for my understanding: If you have a limited number of sites, you can specify a mapping for each site -> but this must be maintained ;( |
Beta Was this translation helpful? Give feedback.
-
I have a domain, where some services are hosted internally, and some on the cloud.
My current setup looks like this for my public domain resolution from inside:
Pi-Hole -> conditional forward public.site to bind9 -> RPZ zone for internal entry mapping to internal domain private.lan (handled by another authoritative server for private.lan) -> Any unresolved domain -> external lookup through cloudflared.
I would like to simplify this with blocky. Right now, I have it as follows, where 10.10.10.4 is the internal authoritative resolver for private.lan.
This works perfectly well for any domains that are hosted internally. But for any services hosted on the cloud, it is not accessible since it does not have a private.lan address. How can I achieve this flow through blocky?
Or will I be able to do this once the #355 or #476 is solved, by setting the first resolver to the internal one and the next to the public one? How can I undo the rewrite before querying the public resolver? Can we have a fallback for the rewrite if it receives an NXDOMAIN?
Beta Was this translation helpful? Give feedback.
All reactions