How can we visit the appstore during the technitium dns server running

[xgocn]

DNS App Store
Error! HttpClient could not resolve IP address for host: go.technitium.com

[ShreyasZare]

Thanks for the post. There is no issue with the domain resolving elsewhere so it seems to be a transient local issue. Please check the DNS logs for any errors to understand why the domain is failing to resolve from your network.

[xgocn]

for example, I run a slave root server with Technitium DNS Server and recursion closed, and I open Apps/App Store ,then got

then, I run

sudo systemctl enable systemd-resolved
sudo systemctl start systemd-resolved
sudo systemctl status systemd-resolved

will got

root@xiangtu:~# sudo systemctl enable systemd-resolved
sudo systemctl start systemd-resolved
sudo systemctl status systemd-resolved
Created symlink /etc/systemd/system/dbus-org.freedesktop.resolve1.service → /usr/lib/systemd/system/systemd-resolved.service.
Created symlink /etc/systemd/system/sysinit.target.wants/systemd-resolved.service → /usr/lib/systemd/system/systemd-resolved.service.
● systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled)
     Active: active (running) since Thu 2024-12-26 16:03:53 CST; 10s ago
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
             https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
             https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
   Main PID: 136886 (systemd-resolve)
     Status: "Processing requests..."
      Tasks: 1 (limit: 1942)
     Memory: 2.6M (peak: 2.8M)
        CPU: 73ms
     CGroup: /system.slice/systemd-resolved.service
             └─136886 /usr/lib/systemd/systemd-resolved

Dec 26 16:03:53 xiangtu systemd[1]: Starting systemd-resolved.service - Network Name Resolution...
Dec 26 16:03:53 xiangtu systemd-resolved[136886]: Positive Trust Anchors:
Dec 26 16:03:53 xiangtu systemd-resolved[136886]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Dec 26 16:03:53 xiangtu systemd-resolved[136886]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr>
Dec 26 16:03:53 xiangtu systemd-resolved[136886]: Using system hostname 'xiangtu'.
Dec 26 16:03:53 xiangtu systemd-resolved[136886]: Another process is already listening on UDP socket 127.0.0.53:53.
Dec 26 16:03:53 xiangtu systemd-resolved[136886]: Turning off local DNS stub support.
Dec 26 16:03:53 xiangtu systemd[1]: Started systemd-resolved.service - Network Name Resolution.
~

[ShreyasZare]

for example, I run a slave root server with Technitium DNS Server and recursion closed, and I open Apps/App Store ,then got

It does not matter. The internal DNS server resolution works even if you disable recursion. The HTTP client used inside DNS server resolves the domain names directly from the DNS server internally.

Note that, your OS will fail to resolve domain if recursion is disabled so you need to either allow recursion or configure the ACL to allow localhost.

You cannot run systemd-resolved together with the DNS server due to port conflict. That has nothing to do with the original issue you have.

As I suggested, please check the DNS logs from the admin panel and share any error log you see in there if you need help understanding that.