mirrors/dae
1
0
Fork 0
mirror of https://github.com/daeuniverse/dae.git synced 2025-01-09 06:47:04 +07:00
Code Issues Packages Projects Releases Wiki Activity
d5172bde64
dae/docs/getting-started/external-dns.md
Kevin Yu eac04e991b
ci: add check-docs workflow (#93) 
* ci: add check-docs workflow

* chore: ignore node_modules

* chore(deps): add package-lock

* style: apply formatting

* style: apply formatting

* fix: fix typo

* fix: fix all proposed changes by markdown-lint

* fix: fix trailing spaces

* fix(troubleshooting.md): apply minor fi

* fix(getting-started): apply minior fix

* ci: dont' kick off build when changes made to check-doc.yml

* ci: ONLY kick off build when target workflow file changes

* trigger build

* fix(build.yml): fix syntax

* trigger build

* fix: fix broken syntax
2023-05-21 00:41:44 +08:00

3.7 KiB
Raw Blame History

Use External DNS

Note

DNS request should be forwarded by dae for domain based traffic split. This guide will show you how to configure dae with external DNS.

If you use a external DNS like AdguardHome, you could refer to the following guide.

External DNS on localhost

If you set up an external DNS on localhost, you may want to let the DNS queries to dns.google.com proxied. For example, if you have the following configuration in AdguardHome:

Listen on: the same machine with dae, port 53.

China mainland: udp://223.5.5.5:53
Others: https://dns.google.com/dns-query

You should configure dae as follows:

  1. Complete wan_interface in "global" section to proxy requests of AdguardHome.

  2. Insert following rule as the first line of "routing" section to avoid loops.

    pname(AdGuardHome) && l4proto(udp) && dport(53) -> must_direct

    And make sure domain dns.google.com will be proxied in routing rules.

  3. Add upstream and request to section "dns".

    dns {
  upstream {
    adguardhome: 'udp://127.0.0.1:53'
  }
  routing {
    request {
      fallback: adguardhome
    }
  }
}

  4. If you bind to WAN, make sure your /etc/resolv.conf does NOT use your local external DNS directly. For example, you can set it as nameserver 119.29.29.29, and then DNS traffic will be hijacked by dae when the packets are sent through NIC. Most of the time, /etc/resolv.conf will be modified back by your DNS service like dnsmasq after rebooting, which is hard to deal with. We recommended you to uninstall them or give sudo chattr +i /etc/resolv.conf if you encounter such situation.

  5. If you bind to LAN, make sure your DHCP server will distribute dae as the DNS server (DNS request should be forwarded by dae for domain based traffic split).

  6. If there is still a DNS issue and there are no warn/error logs, you have to change your listening port of external DNS (here is AdGuardHome) from 53 to non-53 port. See #31.

  7. If you use PVE, refer to #37.

External DNS on another machine in LAN

If you set up a external DNS on another machine in LAN, you may want to let the DNS queries to dns.google.com proxied. For example, if you have following configuration in AdguardHome:

Listen on: 192.168.30.3:53 (mac address: 8c:16:45:36:1c:5a)

China mainland: udp://223.5.5.5:53
Others: https://dns.google.com/dns-query

You should configure dae as follows:

  1. Fill in lan_interface in "global" section to proxy requests of AdguardHome.

  2. Insert following rule as the first line of "routing" section to avoid loops.

    sip(192.168.30.3) && l4proto(udp) && dport(53) -> must_direct
# Or use MAC address if in the same link:
# mac(8c:16:45:36:1c:5a) && l4proto(udp) && dport(53) -> must_direct

    And make sure domain dns.google.com will be proxied in routing rules.

  3. Add upstream and request to section "dns".

    dns {
  upstream {
    adguardhome: 'udp://192.168.30.3:53'
  }
  routing {
    request {
      fallback: adguardhome
    }
  }
}

  4. If you bind to LAN, make sure your DHCP server will distribute dae as the DNS server (DNS request should be forwarded by dae for domain based traffic split).

  5. If there is still a DNS issue and there are no warn/error logs, you have to change your listening port of external DNS (here is AdGuardHome) from 53 to non-53 port. See #31.

  6. If you use PVE, refer to #37.