We have this configured on our server
server ::/0 { bogus yes; };
Just recently noticed the config above can actually cause problems to
resolve hostnames. It works if hostname and the nameserver hosted it are on
same TLD, for example isc.org's nameserver are all on isc.org domain so
server does
On Tuesday, June 21, 2016, Mark Andrews wrote:
>
> server ::/0 { bogus yes; };
Eeeeww! That's gross, but in a bizarrely satisfying way.
W
>
> In message <
> cajs9+yby3vl3kehtjmt58ekqrf6qazfvt3khvy05q26lmpt...@mail.gmail.com
> >, Hillary Nelson writes:
> > We are moving our v6 DN
server ::/0 { bogus yes; };
In message
, Hillary
Nelson writes:
> We are moving our v6 DNS from F5 to anycast, since F5 can translate address
> from v6 to v4, our backend servers are still only v4 and we never have
> problem to resolve hostname with v4 only.
>
> Now for anycast, I want
We are moving our v6 DNS from F5 to anycast, since F5 can translate address
from v6 to v4, our backend servers are still only v4 and we never have
problem to resolve hostname with v4 only.
Now for anycast, I want to enable v6 with private address only, but seems
like named favors v6 and using it t
4 matches
Mail list logo
