knot resolver along cloudlared

[malikshi]

i saw the latest wiki about install knot resolver

-- are to be obtained from IP address 127.0.0.1 port 6053
-- This disables DNSSEC validation!
policy.add(policy.suffix(
    policy.STUB('127.0.0.1@6053'),
    {todname('1.168.192.in-addr.arpa')}))

-- 127.0.0.1 port 6053 for proxy (dnscrypt-proxy or cloudflared)

i set my cloudflared with port 5053 and cloudlfared from this repo also use 5053 but in wiki knot using 6053 little bit make me confused about knot

[trinib]

i saw the latest wiki about install knot resolver

-- are to be obtained from IP address 127.0.0.1 port 6053
-- This disables DNSSEC validation!
policy.add(policy.suffix(
    policy.STUB('127.0.0.1@6053'),
    {todname('1.168.192.in-addr.arpa')}))

-- 127.0.0.1 port 6053 for proxy (dnscrypt-proxy or cloudflared)

i set my cloudflared with port 5053 and cloudlfared from this repo also use 5053 but in wiki knot using 6053 little bit make me confused about knot

@malikshi thanks I missed that

@jo20201 had just choose that port (6053) for DNScrypt, I think it works faster for him at his location instead what I recommended in DNScrypt wiki(5353). Port 5053 is used/recommended by Cloudflare.

[malikshi]

i think put it another mention about this outside config much better so users can read and makes changes according to their config.. mostly users just copy pasta.

[trinib]

i think put it another mention about this outside config much better so users can read and makes changes according to their config.. mostly users just copy pasta.

I will set it to 5353 to the same i have in dnscrypt wiki for less confusion

you can test 'The Registered Ports (1024-49151) – which can be used by applications, specific services, and users'

But port like 5353, 5335, etc are recommeded by dns softwares

[malikshi]

But port like 5353, 5335, etc are recommeded by dns softwares

yes. recommendation from dns softwares itself much better on mostly cases i think.

[malikshi]

found typo in this line 17
'hints > iterate'', -- Allow loading /etc/hosts or custom root hints

[trinib]

@malikshi fixed wiki

[malikshi]

thank you for your hard work. fast ever!

[trinib]

i think put it another mention about this outside config much better so users can read and makes changes according to their config.. mostly users just copy pasta.

Yea your right I should write this outside config file

[trinib]

@malikshi This should help out a lot right ?

[malikshi]

yes it is. thanks you very much.
sir i want to ask how much resources for AGH in VPS? i have vps 2GB RAM with 2 vCPU. i planning to use agh filtering to work along with wireguard/openvpn or kind of proxy i use. currently cloudflard+knot-resolver, but i don't know to set client dns from agh. do you have reference for it?

[trinib]

yes it is. thanks you very much. sir i want to ask how much resources for AGH in VPS? i have vps 2GB RAM with 2 vCPU. i planning to use agh filtering to work along with wireguard/openvpn or kind of proxy i use. currently cloudflard+knot-resolver, but i don't know to set client dns from agh. do you have reference for it?

2gb is good.. what ever port dns resolvers listen on from local address (127.0.0.1), need to be in adguard dns resolvers.