Re: resolv.conf misbehaving
Danny a écrit :
>
> "resolv.conf" now has both the router and Debian as nameservers automatically.
>
> e can now do "dig fever.havannah.local" and it resolves correctly. It queries
> the Debian (10.0.0.5) server by default, which I want.
>
> However, if I do "dig -x 10.0.0.5" (the Debian server which is
> fever.havannah.local) it fails to resolve simply because it queries the router
> (10.0.0.2) instead of the Debian server which is 10.0.0.5. It is not even making
> attempts to query the Debian server.
>
> But if I force dig with "dig @10.0.0.5 -x 10.0.0.5" it resolves correctly.
>
> Is it because 10.0.0.2 (router) is pushed into resolv.conf first?
>
> Any pointers?
My previous reply explains what's wrong. I warned you. This setup is
fundamentally flawed.
Reply to: