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

FS#2332 - Custom DNS servers settings not work on WAN6 interface #8418

Closed
openwrt-bot opened this issue Jun 22, 2019 · 2 comments
Closed

FS#2332 - Custom DNS servers settings not work on WAN6 interface #8418

openwrt-bot opened this issue Jun 22, 2019 · 2 comments
Labels

Comments

@openwrt-bot
Copy link

lzp729:

Supply the following if possible:

  • Device problem occurs on
    x86-64 virtual machine hosted by ESXI6.7u2

  • Software versions of OpenWrt/LEDE release, packages, etc.
    OpenWrt 18.06.2 r7676-cddd7b4c77 / LuCI openwrt-18.06 branch (git-19.170.32094-4d6d8bc)

  • Steps to reproduce
    all steps performed on LUCI

  1. Set WAN interface to ignore peer DNS to use custom DNS 127.0.0.1
  2. Set WAN6 interface to ignore peer DNS to use custom DNS ::1
  3. Start WAN (PPPOE) and WAN6 (DNCPv6 client)

====issue: Check effective DNS, custom WAN6 DNS setting is ignored====
/tmp/resolv.conf.auto

Interface lan

nameserver 127.0.0.1

Interface wan

nameserver 127.0.0.1

Interface wan_6

nameserver 240e:58:c000:1600:180:168:255:118
nameserver 240e:58:c000:1000:116:228:111:18

@openwrt-bot
Copy link
Author

dedeckeh:

As you're using PPPoE the network config has an issue as two wan IPv6 interfaces are created; wan6 by network config and wan_6 automatically created by the PPPoE protocol handler.
The creation of the automatic wan_6 can be disabled by setting ipv6 to 1 in the network wan interface config.
Can you give this a try and the check the peerdns behavior again ?

@openwrt-bot
Copy link
Author

z0id:

Similar setup with IPv6/4 dual stack & PPPoE on OpenWrt 18.06.2.

If I set custom IPv6 DNS via LuCI, it no longer displays any DNS in status page for IPv6.

Setting network.wan.ipv6 to 1 instead of auto seems to break DHCPv6, IPv6 is always "Not connected".

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

No branches or pull requests

1 participant