Upstream DNS servers - using unbound - ipv6 syntax on nonstandard port? #2827
Replies: 2 comments 3 replies
-
Since your unbound listens to |
Beta Was this translation helpful? Give feedback.
-
I'm comming from pihole + unbound So difference is the port declaration # (pihole) vs : (adguard) Ipv4 127.0.0.1:5335 works It would be much appreciated if some working guide can be provided for normal installation or docker installation. In addition in combination with unbound should the adguard dns cache be disabled as we already use unbounds cache. Whats recommended? |
Beta Was this translation helpful? Give feedback.
-
Running adguard home and unbound together on a rhel8 box. Port 53 for dns/adugard and 5335 for unbound. Adguard home + unbound is working great for ipv4. The RHEL box and unbound (using dig) all work for ipv6 at the command line. Also, adguard home with public ipv6 dns upstream servers work.
Here is my question. What is the correct syntax for a the ipv6 unbound server locally on port 5335? Tried ::1:5335 and other things. Just keep getting the error: Server "::1#5335": could not be used, please check that you've written it correctly.
#ipv4 unbound server locally - works fine
127.0.0.1:5335
#ipv6 public server - works fine
2620:fe::fe
#here is my question! what should this format be???
0::1#5335
Beta Was this translation helpful? Give feedback.
All reactions