No, the ::1 in IPv6 DNS1 or 2 or 3 does not get pushed to the client. It is the IPV6 loopback akin to IPV4 127.0.0.1
# cat /opt/etc/init.d/S62mystubby
#!/bin/sh
umask 133
ACTION=$1
CALLER=$(basename $0)
# Wait for NTP before starting
ntptimer=0
while [ "$(nvram get ntp_ready)" = "0" ] && [ "$ntptimer" -lt "300" ]; do
ntptimer=$((ntptimer+1))
sleep 1
done
if [ "$ntptimer" -ge "300" ]; then logger -st ${CALLER} "[*] NTP Failed To Start After 5 Minutes - Please Fix Immediately!"; echo; exit 1; fi
logger -t ${CALLER} "$1 Stubby DNS over TLS from $0"
# set environment PATH to system binaries
export PATH=/sbin:/bin:/usr/sbin:/usr/bin:$PATH
export TZ=$(cat /etc/TZ)
ENABLED=yes
PROCS=stubby
DESC=$PROCS
PATH=/opt/sbin:/opt/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
ansi_red="\033[1;31m";
ansi_white="\033[1;37m";
ansi_green="\033[1;32m";
ansi_yellow="\033[1;33m";
ansi_blue="\033[1;34m";
ansi_bell="\007";
ansi_blink="\033[5m";
ansi_std="\033[m";
ansi_rev="\033[7m";
ansi_ul="\033[4m";
start() {
[ "$CRITICAL" != "yes" -a "$CALLER" = "cron" ] && return 7
[ "$ENABLED" != "yes" ] && return 8
echo -e -n "$ansi_white Starting $DESC... $ansi_std"
if [ -n "`pidof $PROC`" ]; then
echo -e " $ansi_yellow already running. $ansi_std"
return 0
fi
cp /opt/etc/stubby/stubby.yml.minimal /opt/etc/stubby/stubby.yml
nohup /opt/sbin/stubby -C /opt/etc/stubby/stubby.yml -g -l > /opt/var/log/stubby.log 2>&1 &
COUNTER=0
LIMIT=10
while [ -z "`pidof $PROC`" -a "$COUNTER" -le "$LIMIT" ]; do
sleep 1;
COUNTER=`expr $COUNTER + 1`
done
if [ -z "`pidof $PROC`" ]; then
echo -e " $ansi_red failed. $ansi_std"
logger "Failed to start $DESC from $CALLER."
return 255
else
echo -e " $ansi_green done. $ansi_std"
logger "Started $DESC from $CALLER."
return 0
fi
}
stop() {
case "$ACTION" in
stop | restart | start )
echo -e -n "$ansi_white Shutting down $PROC... $ansi_std"
killall $PROC 2>/dev/null
COUNTER=0
LIMIT=10
while [ -n "`pidof $PROC`" -a "$COUNTER" -le "$LIMIT" ]; do
sleep 1;
COUNTER=`expr $COUNTER + 1`
done
;;
kill)
echo -e -n "$ansi_white Killing $PROC... $ansi_std"
killall -9 $PROC 2>/dev/null
;;
esac
if [ -n "`pidof $PROC`" ]; then
echo -e " $ansi_red failed. $ansi_std"
return 255
else
echo -e " $ansi_green done. $ansi_std"
return 0
fi
}
check() {
echo -e -n "$ansi_white Checking $DESC... "
if [ -n "`pidof $PROC`" ]; then
echo -e " $ansi_green alive. $ansi_std";
return 0
else
echo -e " $ansi_red dead. $ansi_std";
return 1
fi
}
reconfigure() {
SIGNAL=SIGHUP
echo -e "$ansi_white Sending $SIGNAL to $PROC... $ansi_std"
killall -$SIGNAL $PROC 2>/dev/null
}
for PROC in $PROCS; do
case $ACTION in
start)
check > /dev/null && stop
start
;;
stop | kill )
check && stop
;;
restart)
check > /dev/null && stop
start
;;
check)
check
;;
reconfigure)
reconfigure
;;
*)
echo -e "$ansi_white Usage: $0 (start|stop|restart|check|kill|reconfigure)$ansi_std"
exit 1
;;
esac
done
#logger "Leaving ${0##*/}."
$PREARGS $PROC $ARGS > /dev/null 2>&1 & if [ "`echo $PREARGS $PROC $ARGS | grep -c '>'`" = "0" ]; then
$PREARGS $PROC $ARGS > /dev/null 2>&1 &
else
eval $PREARGS $PROC $ARGS &
fi.
Not if you want to use stubbyWould it not be better then, set this:
To enable?
ok, thanks
Mar 4 21:46:39 dnsmasq[3127]: forwarded www.snbforums.com to ::1
Mar 4 21:46:39 dnsmasq[3127]: reply www.snbforums.com is 2606:4700:20::6819:ea0f
Mar 4 21:46:39 dnsmasq[3127]: reply www.snbforums.com is 2606:4700:20::6819:eb0f
Mar 4 21:46:39 dnsmasq[3127]: reply www.snbforums.com is 2606:4700:20::6819:ea0f
Mar 4 21:46:39 dnsmasq[3127]: reply www.snbforums.com is 2606:4700:20::6819:eb0fok, thanks
By leaving it blank, mean it will take ipv6 backloop address (localhost similar to ipv4 0:0:0:0, in ipv6 case, ::1)ok, thanks
Anyway to check then, if stubby is really working for ipv6 with it blank?
I use cloudflare which uses to many different resolvers worldwide. I test a number of ip leak test sites linked in Xentrk github and see different DNS IPs on every test. I just have 1.1.1.1 and 1.0.0.1 in my stubby yml.
Using more than one resolver is a good idea. Most ISPs provide a main and alternate DNS server via DHCP. Most routers and PC's have space for two DNS entries. You can put more than two resolvers in stubby.yml. With roundrobbin set to 1 stubby will use each resolver in turn which may be more efficient. I feel it is a good idea to remove ipv6 resolvers if you do not use ipv6 as stubby will error those out if ipv6 is not used.
so what are the full potential of the roundrobbin feature what does it do? , also my system fully supports ipv6 dual stack, but that might be a good suggestion for those who have no support for it.
