ASCAR while doing it ) ...
Once again, thanks to all
Have a nice day
Danny
On Feb 24 14, Pascal Hambourg :
> To: debian-user@lists.debian.org
> Date: Mon, 24 Feb 2014 22:46:23 +0100
> From: Pascal Hambourg
> Subject: Re: resolv.conf misbehaving
> User-Agent: Thunderbird 2.0.0.21
On Feb 25, 2014, at 9:12 AM, Patrick Ouellette wrote:
>
> Sounds like what you really want is for your local nameserver to forward the
> query if it doesn't have the answer. It might be helpful to look at the
> forwarders option for named.conf.
>
> resolv.conf would just need your local nam
Sounds like what you really want is for your local nameserver to forward the
query if it doesn't have the answer. It might be helpful to look at the
forwarders option for named.conf.
resolv.conf would just need your local name server then.
Pat
--
To UNSUBSCRIBE, email to debian-user-requ..
Danny a écrit :
>
>> Warning : this setup is wrong and may not work as you expect. All listed
>> nameservers should be equivalent. Multiple nameservers are only for
>> redundancy, not to provide multiple sources.
>>
>> If you query the first server for an information out of its scope, it
>> may re
Hi Danny,
> My apologies, I must have missed your reply
>
>> Warning : this setup is wrong and may not work as you expect. All
>> listed nameservers should be equivalent. Multiple nameservers are only
>> for redundancy, not to provide multiple sources.
>>
>> If you query the first server for an
Hi,
My apologies, I must have missed your reply
> Warning : this setup is wrong and may not work as you expect. All listed
> nameservers should be equivalent. Multiple nameservers are only for
> redundancy, not to provide multiple sources.
>
> If you query the first server for an information out
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
Hi Guys,
Looks like it was a combination of a few things.
First of all (according to man "resolvconf") I had to add "dns-" hooks to
/etc/network/interfaces.
DHCP was also a little problem (like some of you pointed out).
"resolv.conf" now has both the router and Debian as nameservers automatical
Hello,
Danny a écrit :
>
> However, I have noticed that my resolv.conf gets overwritten by something
> after
> every reboot. The Debian server resolves all local (internal) addresses and
> the
> ADSL router resolves all external addresses.
>
> Normally my resolv.conf looked like this
>
> name
2014-02-20 16:17 GMT+01:00 Danny :
> Hi guys,
>
> The past weekend I upgraded from Debian v3.0 to the latest Debian stable
> (7.0 or
> something) ... (wish I never did) ...
>
> However, I have noticed that my resolv.conf gets overwritten by something
> after
> every reboot. The Debian server resol
On 02/20/2014 11:28 AM, Patrick Ouellette wrote:
> Welcome to the (un)helpful world of "let me do that for you because it is
> easier" aka networkmanager and/or resolvconf.
>
> You will need to either update your /etc/network/interfaces entry for the
> server or edit /etc/resolvconf/resolv.conf.d/
On 20/02/14 15:17, Danny wrote:
Hi guys,
The past weekend I upgraded from Debian v3.0 to the latest Debian stable (7.0 or
something) ... (wish I never did) ...
However, I have noticed that my resolv.conf gets overwritten by something after
every reboot. The Debian server resolves all local (int
On Thu, Feb 20, 2014 at 05:17:22PM +0200, Danny wrote:
>
> Hi guys,
>
> The past weekend I upgraded from Debian v3.0 to the latest Debian stable (7.0
> or
> something) ... (wish I never did) ...
>
> However, I have noticed that my resolv.conf gets overwritten by something
> after
> every reboo
On 20/02/2014 10:17, Danny wrote:
> Hi guys,
>
> The past weekend I upgraded from Debian v3.0 to the latest Debian stable (7.0
> or
> something) ... (wish I never did) ...
>
> However, I have noticed that my resolv.conf gets overwritten by something
> after
> every reboot. The Debian server res
On Thu, Feb 20, 2014 at 05:17:22PM +0200, Danny wrote:
> Hi guys,
>
> The past weekend I upgraded from Debian v3.0 to the latest Debian stable (7.0
> or
> something) ... (wish I never did) ...
The correct way to upgrade is, unfortunately,
3.0->4.0->5.0->6.0->7.0->7.4. If you went from 3.0 straig
Danny wrote:
> However, I have noticed that my resolv.conf gets overwritten by something
> after
> every reboot.
apt-get purge resolvconf
Grüße,
S°
--
Sigmentation fault. Core dumped.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Troub
Hi guys,
The past weekend I upgraded from Debian v3.0 to the latest Debian stable (7.0 or
something) ... (wish I never did) ...
However, I have noticed that my resolv.conf gets overwritten by something after
every reboot. The Debian server resolves all local (internal) addresses and the
ADSL rout
17 matches
Mail list logo
