Consider default private upstream servers

[EugeneOne1]

The syntax of upstream servers allows using # within the domain-specific server to make AdGuard Home use the default one for specified domains. Currently, it requires at least a single non-domain-specific server to be presented.

I suppose we may skip this step of validation for "Private reverse DNS servers" and use the default ones if those are already determined automatically and all the entries are domain-specific. @ameshkov, what do you think?

[ameshkov]

Could you please provide some examples?

[EugeneOne1]

@ameshkov, this is how it works for now:

This is what I'm suggesting:

These are supposed to be the same.

[ameshkov]

Makes sense

[alexindigo]

Looks like something is broken even when non domain specific entry is provided:

[SukkaW]

Makes sense

@ameshkov

I am also looking for this feature, but with a different reason:

# I want to have my gateway's built-in DNS to handle domains like `routerlogin.net`
[/routerlogin.net/]#
[/asusrouter.com/]#
# In short, I want "Private Preserve Upstream Servers" also used to handle the above domains
# I don't want to hardcode gateway IP here, since gateway IP might change, according to how VLAN is configured

# I then have a default server for public reachable domains
tcp://unfiltered.adguard-dns.com

# I then have another custom server for handling specific domain
[/acme.corp/]udp://corp-private-dns:53

[itsthejb]

@alexindigo Also realised I have the same issue for a long time. Actually bisected releases, and found that things broke in v0.107.46. I've rolled back to v0.107.45 and rDNS is working correctly again:

In my case:

• Using AGH DHCP
• Interface IP address is 192.168.2.1 is the AGH
• I want to point rDNS to AGH itself in order to resolve IP addresses in the logs and stats

I also tried the v0.108.0-b.62 and was disappointed to see the issue isn't resolved there. AGH is not very useful if you can't see hostname in logs/stats in order to understand what's happening on the network...

[alexindigo]

@ameshkov we have bug report with bisect here, is it something you can help with? Sounds like quite crucial feature for different setups.

[Gifford47]

Looks like something is broken even when non domain specific entry is provided:

I've the same issue here. Also if I defined local_ptr_upstreams in yaml config

[itsthejb]

Does this deserve a separate issue to get more attention? Or adequate to keep it here?

[SukkaW]

Does this deserve a separate issue to get more attention? Or adequate to keep it here?

This deserves a dedicated issue though. This issue is about a feature request.

[Gifford47]

ok, I created an Issue here ...

[stauffenberg2020]

ok, I created an Issue here ...

This seems to be a different than the feature request here?