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

Conditional DNS resolution for wildcards of TLD #1521

Open
Tuxdude opened this issue Jun 13, 2024 · 3 comments
Open

Conditional DNS resolution for wildcards of TLD #1521

Tuxdude opened this issue Jun 13, 2024 · 3 comments

Comments

@Tuxdude
Copy link

Tuxdude commented Jun 13, 2024

I would like to specify the upstream DNS server using conditional DNS resolution for a subset of TLDs.

Use Case

I use .foobar as the TLD for all of my devices and services on my internal private network. I have DNS entries on my DNS resolver at 192.168.1.1 which has host -> IP mappings as follows:

host1.foobar 192.168.1.41
host2.foobar 192.168.1.42
host3.foobar 192.168.1.43

I want blocky to resolve any hosts matching *.foobar using an authoritative DNS server in my internal private network which has the above mappings (i.e. basically my DHCP server / router which is currently maintaining these mappings).

What I tried so far

The following does not work:

conditional:
  mapping:
    .foobar: 192.168.1.1

Currently, the above still ends up using the DNS resolvers configured under upstreams. I have more than forty devices in my private network, and I don't want to use Custom DNS to specify each of these host->IP mappings.

From the documentation

The documentation mentions the above should work if my internal domain names were of the form *.foobar.foobaz. I don't see why it should be limited and why it can't be extended to also support *.foobar use case as the one I described above (the one I am using in my private network homelab setup).

conditional:
  mapping:
    foobar.foobaz: 192.168.1.1
Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Sep 11, 2024
@Tuxdude
Copy link
Author

Tuxdude commented Sep 11, 2024

Bumping this for triage by the repo owners and to prevent this issue getting automatically closed.

@github-actions github-actions bot removed the Stale label Sep 12, 2024
@dajul
Copy link

dajul commented Sep 15, 2024

This is working for me:

conditional:
  fallbackUpstream: false
  mapping:
    freeipa.home: 192.168.88.186,192.168.88.202
    home: 127.0.0.1:5301

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants