Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #256939 > unrolled thread

how to change default nameserver?

Back to article view | Back to linux.debian.user

Contents

  how to change default nameserver? coreyh@free.fr - 2023-04-09 10:30 +0200
    Re: how to change default nameserver? Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-04-09 11:00 +0200
    Re: how to change default nameserver? gene heskett <gheskett@shentel.net> - 2023-04-09 14:20 +0200
      Re: how to change default nameserver? zithro <slack@rabbit.lu> - 2023-04-09 17:00 +0200
        Re: how to change default nameserver? Greg Wooledge <greg@wooledge.org> - 2023-04-09 17:10 +0200
          Re: how to change default nameserver? gene heskett <gheskett@shentel.net> - 2023-04-09 21:50 +0200
        Re: how to change default nameserver? Greg Wooledge <greg@wooledge.org> - 2023-04-09 17:30 +0200
          Re: how to change default nameserver? zithro <slack@rabbit.lu> - 2023-04-09 22:30 +0200
          Re: how to change default nameserver? gene heskett <gheskett@shentel.net> - 2023-04-10 18:10 +0200
            Re: how to change default nameserver? Greg Wooledge <greg@wooledge.org> - 2023-04-10 19:40 +0200
              Re: how to change default nameserver? gene heskett <gheskett@shentel.net> - 2023-04-10 21:50 +0200
                Re: how to change default nameserver? zithro <slack@rabbit.lu> - 2023-04-10 23:00 +0200
                  Re: how to change default nameserver? Greg Wooledge <greg@wooledge.org> - 2023-04-10 23:00 +0200
                    Re: how to change default nameserver? zithro <slack@rabbit.lu> - 2023-04-11 00:10 +0200
                      Re: how to change default nameserver? Andy Smith <andy@strugglers.net> - 2023-04-11 00:30 +0200
                        Re: how to change default nameserver? zithro <slack@rabbit.lu> - 2023-04-11 18:40 +0200
                      Re: how to change default nameserver? gene heskett <gheskett@shentel.net> - 2023-04-11 05:20 +0200
                        Re: how to change default nameserver? Richard Hector <richard@walnut.gen.nz> - 2023-04-11 05:50 +0200
                        Re: how to change default nameserver? Richard Hector <richard@walnut.gen.nz> - 2023-04-11 09:00 +0200
                          Re: how to change default nameserver? Greg Wooledge <greg@wooledge.org> - 2023-04-11 13:30 +0200
                            Re: how to change default nameserver? zithro <slack@rabbit.lu> - 2023-04-11 22:00 +0200
                              Re: how to change default nameserver? Greg Wooledge <greg@wooledge.org> - 2023-04-11 22:20 +0200
                                Re: how to change default nameserver? zithro <slack@rabbit.lu> - 2023-04-11 22:50 +0200
                                Re: how to change default nameserver? zithro <slack@rabbit.lu> - 2023-04-12 01:30 +0200
                  Re: how to change default nameserver? gene heskett <gheskett@shentel.net> - 2023-04-11 05:00 +0200
                    Re: how to change default nameserver? zithro <slack@rabbit.lu> - 2023-04-11 16:10 +0200
                      Re: how to change default nameserver? gene heskett <gheskett@shentel.net> - 2023-04-11 19:20 +0200
                        Re: how to change default nameserver? Greg Wooledge <greg@wooledge.org> - 2023-04-11 19:40 +0200
                        Re: how to change default nameserver? "Andrew M.A. Cater" <amacater@einval.com> - 2023-04-11 19:40 +0200
                          Re: how to change default nameserver? gene heskett <gheskett@shentel.net> - 2023-04-11 22:30 +0200
                            Re: how to change default nameserver? zithro <slack@rabbit.lu> - 2023-04-12 16:30 +0200
                          Re: how to change default nameserver? Max Nikulin <manikulin@gmail.com> - 2023-04-12 05:30 +0200
                        Re: how to change default nameserver? zithro <slack@rabbit.lu> - 2023-04-11 19:50 +0200
                          Re: how to change default nameserver? Nicholas Geovanis <nickgeovanis@gmail.com> - 2023-04-11 21:20 +0200
                          Re: how to change default nameserver? gene heskett <gheskett@shentel.net> - 2023-04-12 01:20 +0200
            Re: how to change default nameserver? Andy Smith <andy@strugglers.net> - 2023-04-10 21:20 +0200
    Re: how to change default nameserver? Greg Wooledge <greg@wooledge.org> - 2023-04-09 14:50 +0200

Page 1 of 2  [1] 2  Next page →

#256939 — how to change default nameserver?

greetings,

I know I can edit the entries in /etc/resolv.conf, but it will be 
overwritten by DHCP server.
I searched the internet and got one of the answers:

apt install resolvconf
echo "nameserver 127.0.0.1" >> /etc/resolvconf/resolv.conf.d/head

what's the difference for /etc/resolv.conf and the method above?

Thanks & Happy weekend.
corey hickman

[toc] | [next] | [standalone]

#256941

Am Sun, Apr 09, 2023 at 04:20:49PM +0800 schrieb coreyh@free.fr:
> greetings,
> 
> I know I can edit the entries in /etc/resolv.conf, but it will be
> overwritten by DHCP server.
> I searched the internet and got one of the answers:
> 
> apt install resolvconf
> echo "nameserver 127.0.0.1" >> /etc/resolvconf/resolv.conf.d/head
> 
> what's the difference for /etc/resolv.conf and the method above?
 
There is a thrid method I use. I have add the following lines to
/etc/dhcp/dhclient.conf:

interface "bond0" {
supersede domain-name-servers 127.0.0.1;
}

My interface is bond0. Yours might be different.

Kind regards,
Christoph
-- 
Ist die Katze gesund
schmeckt sie dem Hund.

[toc] | [prev] | [next] | [standalone]

#256956

On 4/9/23 04:20, coreyh@free.fr wrote:
> greetings,
> 
> I know I can edit the entries in /etc/resolv.conf, but it will be 
> overwritten by DHCP server.
> I searched the internet and got one of the answers:
> 
> apt install resolvconf
> echo "nameserver 127.0.0.1" >> /etc/resolvconf/resolv.conf.d/head
> 
> what's the difference for /etc/resolv.conf and the method above?

I'm not sure, and my methods have been heavily denegrated by the dhcp 
fans, but in my case with a many machine local net, and no dhcpd running 
on the system, and the changes with each new release, I find the one 
repeatable method to solve dns problem, is to compose an 
/etc/resolv.conf with 2 lines:

mameserver ipv4 address of router
search hosts, nameserver

And sudo chattr +i /etc/resolv.conf

quickly so NM can't change it. It will remove the search line, killing 
your local network, in which case you can ping yahoo.com, but not 
another machine on your local net. Your ISP's dns has no knowledge of 
your local net which is as it should be.

My router runs something like dnsmasq as its running dd-wrt, and 
theoretically a dns request then searchs the host file for a matching 
name, failing that my whole local system then query's the router, which 
if not cached by dnsmasq, sends the query on to my ISP's dns server, and 
I get answers in around 30 milliseconds. And it all just works. With the 
router NAT-ing, all machines here can browse the whole planet, as 
transparently as border facilities allow.

My main problem with each new release is the ever changing methods of 
establishing each machines repeatable, permanent, name and local address 
on a completely static system described in the /etc/hosts file. Reliably 
setting a domainname used to be once and done, but since bullseye its 
only for this reboot, but I've not found a place to make it permanent 
across reboots, yet...

If anyone knows how to do that on bullseye, I'm all ears. Hopefully it 
will continue to work with bookworm but I'm not a betting man. I'm still 
looking for a way to re-establish cups printer sharing, which Just 
Worked with buster, but is now blocked on bullseye from other bullseye 
machines, but still works with buster machines to this bullseye machine. 
WTH???

Thanks for reading, take care and stay well, all.
> 
> Thanks & Happy weekend.
> corey hickman
> 
> .

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[toc] | [prev] | [next] | [standalone]

#256969

On 09 Apr 2023 14:14, gene heskett wrote:

> I'm not sure, and my methods have been heavily denegrated by the dhcp 
> fans, but in my case with a many machine local net, and no dhcpd running 
> on the system, and the changes with each new release, I find the one 
> repeatable method to solve dns problem, is to compose an 
> /etc/resolv.conf with 2 lines:
> 
> mameserver ipv4 address of router
> search hosts, nameserver
> 
> And sudo chattr +i /etc/resolv.conf
> 
> quickly so NM can't change it. It will remove the search line, killing 
> your local network, in which case you can ping yahoo.com, but not 
> another machine on your local net. Your ISP's dns has no knowledge of 
> your local net which is as it should be.
> 
> My router runs something like dnsmasq as its running dd-wrt, and 
> theoretically a dns request then searchs the host file for a matching 
> name, failing that my whole local system then query's the router, which 
> if not cached by dnsmasq, sends the query on to my ISP's dns server, and 
> I get answers in around 30 milliseconds. And it all just works. With the 
> router NAT-ing, all machines here can browse the whole planet, as 
> transparently as border facilities allow.

It seems you misconfigured a few things.
- Either you use DHCP, and the DNS will be provided by the DHCP server, 
so don't touch resolv.conf (the DHCP server CAN provide 127.0.0.1 as DNS 
server)
- or you use static addressing, and you can simply remove the 
dhcp-client package, so resolv.conf will be left alone.

Also, the line "search hosts, nameserver" is wrong. The place to put 
such settings is "/etc/nsswitch.conf".
"search" is used to resolve hostnames to FQDN.
So if you put "search example.com", and you try to connect to a machine 
with for example "ssh hostname", the DNS client will try to append 
example.com to hostname, and try to resolve "hostname.example.com".

Finally, if using static addressing, I can't see why NetworkManager is 
useful.

So to recap, if your LOCAL domain is example.com, and your DNS server is 
192.168.1.1, a resolv.conf would look like:
# /etc/resolv.conf
nameserver 192.168.1.1
search example.com
#

Man pages:
man resolv.conf
man nsswitch.conf

[toc] | [prev] | [next] | [standalone]

#256970

On Sun, Apr 09, 2023 at 04:53:17PM +0200, zithro wrote:
> - Either you use DHCP, and the DNS will be provided by the DHCP server, so
> don't touch resolv.conf (the DHCP server CAN provide 127.0.0.1 as DNS
> server)
> - or you use static addressing, and you can simply remove the dhcp-client
> package, so resolv.conf will be left alone.

That's not always true.  Sometimes you want the IP address from DHCP,
but you want to provide your own DNS.  There are LOTS of scenarios where
this is desirable.

That's why this is such an important topic, and why it keeps coming up
over and over again.

That's why we have a wiki page which describes several different solutions,
so that each sysadmin who runs into this problem can find a suitable one.

https://wiki.debian.org/resolv.conf

[toc] | [prev] | [next] | [standalone]

#256987

On 4/9/23 11:04, Greg Wooledge wrote:
> On Sun, Apr 09, 2023 at 04:53:17PM +0200, zithro wrote:
>> - Either you use DHCP, and the DNS will be provided by the DHCP server, so
>> don't touch resolv.conf (the DHCP server CAN provide 127.0.0.1 as DNS
>> server)
>> - or you use static addressing, and you can simply remove the dhcp-client
>> package, so resolv.conf will be left alone.
> 
> That's not always true.  Sometimes you want the IP address from DHCP,
> but you want to provide your own DNS.  There are LOTS of scenarios where
> this is desirable.
> 
> That's why this is such an important topic, and why it keeps coming up
> over and over again.
> 
> That's why we have a wiki page which describes several different solutions,
> so that each sysadmin who runs into this problem can find a suitable one.
> 
> https://wiki.debian.org/resolv.conf
> 
> .
Thank you for that link Greg.

This explains it better than I do, but if history is any indicator, it 
will be made useless by bookworm.  Thanks Greg, it may contain some clue 
as to why printers on this machine, all marked shared, cannot be used by 
other bullseye installs, Other buster installs however can use them just 
fine. My logs claim the client is not sending any authorization. Yet all 
clients claim DefaultAuthorization is Basic.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[toc] | [prev] | [next] | [standalone]

#256972

On Sun, Apr 09, 2023 at 04:53:17PM +0200, zithro wrote:
> Also, the line "search hosts, nameserver" is wrong. The place to put such
> settings is "/etc/nsswitch.conf".
> "search" is used to resolve hostnames to FQDN.
> So if you put "search example.com", and you try to connect to a machine with
> for example "ssh hostname", the DNS client will try to append example.com to
> hostname, and try to resolve "hostname.example.com".

Welcome to the Gene Heskett show, starring Gene Heskett.

We've told Gene that his configuration is wrong *so* many times, over
*so* many years.  There are very many, very long, threads dedicated to
trying to help Gene get his network configuration to a sane state.

I recommend not trying again, but it's up to you.  Maybe you'll succeed
where everyone else has failed... I doubt it, but I can't rule it out.

[toc] | [prev] | [next] | [standalone]

#256989

On 09 Apr 2023 17:20, Greg Wooledge wrote:
> Welcome to the Gene Heskett show, starring Gene Heskett.
> 
> We've told Gene that his configuration is wrong *so* many times, over
> *so* many years.  There are very many, very long, threads dedicated to
> trying to help Gene get his network configuration to a sane state.
> 
> I recommend not trying again, but it's up to you.  Maybe you'll succeed
> where everyone else has failed... I doubt it, but I can't rule it out.
> 

Ahah ^^
As confucius said : "Experience is a lantern that you carry on your back 
and that only lights up the path you have traveled", but thanks for the 
advice !

[toc] | [prev] | [next] | [standalone]

#257004

On 4/9/23 11:20, Greg Wooledge wrote:
> On Sun, Apr 09, 2023 at 04:53:17PM +0200, zithro wrote:
>> Also, the line "search hosts, nameserver" is wrong. The place to put such
>> settings is "/etc/nsswitch.conf".
>> "search" is used to resolve hostnames to FQDN.
>> So if you put "search example.com", and you try to connect to a machine with
>> for example "ssh hostname", the DNS client will try to append example.com to
>> hostname, and try to resolve "hostname.example.com".
> 
> Welcome to the Gene Heskett show, starring Gene Heskett.
> 
> We've told Gene that his configuration is wrong *so* many times, over
> *so* many years.  There are very many, very long, threads dedicated to
> trying to help Gene get his network configuration to a sane state.
> 
> I recommend not trying again, but it's up to you.  Maybe you'll succeed
> where everyone else has failed... I doubt it, but I can't rule it out.
> 
> .
Thanks for the vote of confidence Greg, but I'd like to point out that 
the help offered is only valid for systems with a working dhcpd.
You tell me I'm wrong, but you don't tell how to do it right w/o 
dragging in dhcpd.  My way doesn't need that. But you've made it your 
lifes work to not understand how my way Just Works.

Take care & stay well.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[toc] | [prev] | [next] | [standalone]

#257006

On Mon, Apr 10, 2023 at 12:05:06PM -0400, gene heskett wrote:
> Thanks for the vote of confidence Greg, but I'd like to point out that the
> help offered is only valid for systems with a working dhcpd.
> You tell me I'm wrong, but you don't tell how to do it right w/o dragging in
> dhcpd.  My way doesn't need that. But you've made it your lifes work to not
> understand how my way Just Works.

How To Set Up A Debian Computer With Static IP Addressing And Hosts File:

1) Install Debian.  Select "Standard".  Do not select a Desktop Environment.

2) Find the name of your ethernet interface, either using "ip link" or
   by reading /etc/network/interfaces.  For purposes of this document,
   let's say it's "en0".

3) Bring your ethernet interface down:  ifdown en0
   This will kill the DHCP client daemon.

4) Edit the /etc/network/interfaces file, and change
      iface en0 inet dhcp
   to
      iface en0 inet static
   and then add the "address" and "gateway" lines underneath that.
   While you're in there, make sure you have "auto en0" too.

5) Bring your interface up:  ifup en0

6) Verify that it works, by pinging your gateway, and then pinging an
   outside IP address (e.g. ping 8.8.8.8).

7) Edit your /etc/resolv.conf file correctly for your network.
   This means adding a "nameserver" line that points to your DNS resolver.
   Do not add lines that are not documented in resolv.conf(5).
   Specifically, do not add lines that mimic /etc/nsswitch.cong behavior
   in this file, because they do not work.

8) Verify that DNS works (e.g. ping www.debian.org).

9) Edit your /etc/hosts file to contain the IP addresses and names of
   other hosts on your internal network.

10) Verify that your internet network name resolution works
    (e.g. ping coyote).

There you go.  That's the whole thing.  That's what we've tried to tell
you to do, for the last 5 to 10 years.

I promise you, Gene, "search hosts, nameserver" is NOT a working line in
an /etc/resolv.conf file.  It never has been.  It never will be.

[toc] | [prev] | [next] | [standalone]

#257013

On 4/10/23 13:30, Greg Wooledge wrote:
> On Mon, Apr 10, 2023 at 12:05:06PM -0400, gene heskett wrote:
>> Thanks for the vote of confidence Greg, but I'd like to point out that the
>> help offered is only valid for systems with a working dhcpd.
>> You tell me I'm wrong, but you don't tell how to do it right w/o dragging in
>> dhcpd.  My way doesn't need that. But you've made it your lifes work to not
>> understand how my way Just Works.
> 
> How To Set Up A Debian Computer With Static IP Addressing And Hosts File:
> 
> 1) Install Debian.  Select "Standard".  Do not select a Desktop Environment.
> 
> 2) Find the name of your ethernet interface, either using "ip link" or
>     by reading /etc/network/interfaces.  For purposes of this document,
>     let's say it's "en0".
> 
> 3) Bring your ethernet interface down:  ifdown en0
>     This will kill the DHCP client daemon.
> 
> 4) Edit the /etc/network/interfaces file, and change
>        iface en0 inet dhcp
>     to
>        iface en0 inet static
>     and then add the "address" and "gateway" lines underneath that.
>     While you're in there, make sure you have "auto en0" too.
> 
> 5) Bring your interface up:  ifup en0
> 
> 6) Verify that it works, by pinging your gateway, and then pinging an
>     outside IP address (e.g. ping 8.8.8.8).
> 
> 7) Edit your /etc/resolv.conf file correctly for your network.
>     This means adding a "nameserver" line that points to your DNS resolver.
>     Do not add lines that are not documented in resolv.conf(5).
>     Specifically, do not add lines that mimic /etc/nsswitch.cong behavior
>     in this file, because they do not work.
> 
> 8) Verify that DNS works (e.g. ping www.debian.org).
> 
> 9) Edit your /etc/hosts file to contain the IP addresses and names of
>     other hosts on your internal network.
> 
> 10) Verify that your internet network name resolution works
>      (e.g. ping coyote).
> 
> There you go.  That's the whole thing.  That's what we've tried to tell
> you to do, for the last 5 to 10 years.
> 
> I promise you, Gene, "search hosts, nameserver" is NOT a working line in
> an /etc/resolv.conf file.  It never has been.  It never will be.
> 
> .
Up to the resolv.conf, that is exactly what I do. But that change to 
resolv.conf adding the search line has been required since red hat 5.0 
in 1998. until bullseye. Just last week I found it is not needed in an 
armbian bullseye install.

Now, if I could figure out why printers, shared om this bullseye machine 
work perfectly when accessed by a buster machine, but cannot be seen by 
any other bullseye machine here, debian or armbian. My logs show an auth 
failure but all are DefaultAthorization Basic. And turning on debugging 
doesn't tell me anything more useful. Like why... I've managed to get 1 
armbian machine trying to connect, but my logs are huge cuz it tries 
every 11 seconds

Take care & sty well, Greg

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[toc] | [prev] | [next] | [standalone]

#257017

> On 4/10/23 13:30, Greg Wooledge wrote:
> Up to the resolv.conf, that is exactly what I do. But that change to 
> resolv.conf adding the search line has been required since red hat 5.0 
> in 1998. until bullseye. Just last week I found it is not needed in an 
> armbian bullseye install.

What ?! Red Hat ?!
I hope it's a writing mistake, and that you know that the system config 
is not handled the same way in RedHat and Debian ?

Why can't you follow others advice, hell, if you don't trust us, even 
the perfectly correct and up-to-date manpages ?
After reading the posts of others, I'm more and more thinking your 
simply a troll (or a RedHat fanatic wasting Debian helpers time for no 
reason) ...


> Now, if I could figure out why printers, shared om this bullseye machine 
> work perfectly when accessed by a buster machine, but cannot be seen by 
> any other bullseye machine here, debian or armbian. My logs show an auth 
> failure but all are DefaultAthorization Basic. And turning on debugging 
> doesn't tell me anything more useful. Like why... I've managed to get 1 
> armbian machine trying to connect, but my logs are huge cuz it tries 
> every 11 seconds

Maybe it's a bug in CUPS or w/e soft you're using. Try to find other 
people having this, or report it as a bug.

I think you should try avahi/bonjour, also known as *zeroconf*.
Maybe it will better handle your network than yourself ...
Sorry to be so harsh, but no one can help someone who does not want to 
be helped.

[toc] | [prev] | [next] | [standalone]

#257018

On Mon, Apr 10, 2023 at 10:53:41PM +0200, zithro wrote:
> Why can't you follow others advice, hell, if you don't trust us, even the
> perfectly correct and up-to-date manpages ?
> After reading the posts of others, I'm more and more thinking your simply a
> troll (or a RedHat fanatic wasting Debian helpers time for no reason) ...

My take is that he's confused, not trolling.  I've never seen any evidence
that he's intentionally making false statements.  He seems to believe what
he's saying.

The weird and frustrating part is that nothing we do or offer seems to
break through the confusion.

[toc] | [prev] | [next] | [standalone]

#257019

On 10 Apr 2023 22:58, Greg Wooledge wrote:
> On Mon, Apr 10, 2023 at 10:53:41PM +0200, zithro wrote:
>> Why can't you follow others advice, hell, if you don't trust us, even the
>> perfectly correct and up-to-date manpages ?
>> After reading the posts of others, I'm more and more thinking your simply a
>> troll (or a RedHat fanatic wasting Debian helpers time for no reason) ...
> 
> My take is that he's confused, not trolling.  I've never seen any evidence
> that he's intentionally making false statements.  He seems to believe what
> he's saying.

Well, I don't know what's the worst ...
And honestly, when you're genuinely confused, you believe and follow the 
advice of the ones who know ...

> The weird and frustrating part is that nothing we do or offer seems to
> break through the confusion.


So, I got curious about his claim : "that change to resolv.conf adding 
the search line [search hosts, nameserver] has been required since red 
hat 5.0 in 1998".
(The bracket addition is mine)

I'm not using RHEl-based systems a lot so I may be wrong, and there's 
not a lot of material left from the 1998 web, but the resolv.conf file 
*looks* identical in RHEL-based systems, at least nowadays.
I quickly browsed a few RH help pages about resolv.conf, but couldn't 
find his claim.

I then searched for "search hosts, nameserver" on search engines (-with- 
the quotes, to only get full-match results).
Either I get no results or ... wait for it ... it *ONLY* gives me 
results where Gene posted !

So Gene, can you tell us where you read this ?

If you didn't read it somewhere, are you using it because :
- it always has been in your config files, which you created at a time 
you didn't really know what you were doing,
- or you followed advice from someone who claimed he knew,
- or it was in a wrongly pre-configured system and you blindly copied 
the stanza ?

[toc] | [prev] | [next] | [standalone]

#257020

Hello,

On Tue, Apr 11, 2023 at 12:04:24AM +0200, zithro wrote:
> So, I got curious about his claim

Well you can't say you haven't been warned. This rabbit hole goes
very deep and the bottom will not contain the answers you seek!

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

[toc] | [prev] | [next] | [standalone]

#257052

On 11 Apr 2023 00:28, Andy Smith wrote:
> Hello,
> 
> On Tue, Apr 11, 2023 at 12:04:24AM +0200, zithro wrote:
>> So, I got curious about his claim
> 
> Well you can't say you haven't been warned. This rabbit hole goes
> very deep and the bottom will not contain the answers you seek!
> 
> Cheers,
> Andy
> 

Ahah, I dunno if in this case I'd like to eat the red pill ^^

[toc] | [prev] | [next] | [standalone]

#257028

On 4/10/23 18:04, zithro wrote:
> On 10 Apr 2023 22:58, Greg Wooledge wrote:
>> On Mon, Apr 10, 2023 at 10:53:41PM +0200, zithro wrote:
>>> Why can't you follow others advice, hell, if you don't trust us, even 
>>> the
>>> perfectly correct and up-to-date manpages ?
>>> After reading the posts of others, I'm more and more thinking your 
>>> simply a
>>> troll (or a RedHat fanatic wasting Debian helpers time for no reason) 
>>> ...
>>
>> My take is that he's confused, not trolling.  I've never seen any 
>> evidence
>> that he's intentionally making false statements.  He seems to believe 
>> what
>> he's saying.
> 
> Well, I don't know what's the worst ...
> And honestly, when you're genuinely confused, you believe and follow the 
> advice of the ones who know ...
> 
>> The weird and frustrating part is that nothing we do or offer seems to
>> break through the confusion.
> 
> 
> So, I got curious about his claim : "that change to resolv.conf adding 
> the search line [search hosts, nameserver] has been required since red 
> hat 5.0 in 1998".
> (The bracket addition is mine)
> 
> I'm not using RHEl-based systems a lot so I may be wrong, and there's 
> not a lot of material left from the 1998 web, but the resolv.conf file 
> *looks* identical in RHEL-based systems, at least nowadays.
> I quickly browsed a few RH help pages about resolv.conf, but couldn't 
> find his claim.
> 
> I then searched for "search hosts, nameserver" on search engines (-with- 
> the quotes, to only get full-match results).
> Either I get no results or ... wait for it ... it *ONLY* gives me 
> results where Gene posted !
> 
> So Gene, can you tell us where you read this ?

In a man page from a good 20 years ago. I still have a copy of that 
original redhat 5.0 on a shelf above me, but not a floppy drive to read 
those disks with.
> 
> If you didn't read it somewhere, are you using it because :
> - it always has been in your config files, which you created at a time 
> you didn't really know what you were doing,
> - or you followed advice from someone who claimed he knew,
> - or it was in a wrongly pre-configured system and you blindly copied 
> the stanza ?

That I can't recall for sure, my wet ram is 88 years old, but I had to 
use it yet for a quint of buster installs when updating my machines to 
buster a month or so after it was released. 4 of them are still in daily 
use here. And I just discovered after this round re-started, that its no 
longer required for armbian's bullseye. So as an experiment, I 
re-installed avahi & cups-browsed on these bullseye machines which I had 
removed. And on reboot, I still had a local network on all bullseye's. 
Blew me away.

Take care & stay well.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[toc] | [prev] | [next] | [standalone]

#257030

On 11/04/23 15:17, gene heskett wrote:
> In a man page from a good 20 years ago. I still have a copy of that 
> original redhat 5.0 on a shelf above me, but not a floppy drive to read 
> those disks with.

Downloading an iso ... :-)

Richard

[toc] | [prev] | [next] | [standalone]

#257035

On 11/04/23 15:17, gene heskett wrote:
> On 4/10/23 18:04, zithro wrote:

>> So, I got curious about his claim : "that change to resolv.conf adding 
>> the search line [search hosts, nameserver] has been required since red 
>> hat 5.0 in 1998".
>> (The bracket addition is mine)
>>
>> I'm not using RHEl-based systems a lot so I may be wrong, and there's 
>> not a lot of material left from the 1998 web, but the resolv.conf file 
>> *looks* identical in RHEL-based systems, at least nowadays.
>> I quickly browsed a few RH help pages about resolv.conf, but couldn't 
>> find his claim.
>>
>> I then searched for "search hosts, nameserver" on search engines 
>> (-with- the quotes, to only get full-match results).
>> Either I get no results or ... wait for it ... it *ONLY* gives me 
>> results where Gene posted !
>>
>> So Gene, can you tell us where you read this ?
> 
> In a man page from a good 20 years ago. I still have a copy of that 
> original redhat 5.0 on a shelf above me, but not a floppy drive to read 
> those disks with.

Well, it's not in resolver(5) (which is for resolv.conf) on Red Hat 5.0.5.

Richard

[toc] | [prev] | [next] | [standalone]

#257042

> > > So Gene, can you tell us where you read this ?
> > 
> > In a man page from a good 20 years ago. I still have a copy of that
> > original redhat 5.0 on a shelf above me, but not a floppy drive to read
> > those disks with.
> 
> Well, it's not in resolver(5) (which is for resolv.conf) on Red Hat 5.0.5.

It wasn't in the man page from Red Hat 5.2 when I checked in 2017, either.

https://lists.debian.org/debian-user/2017/09/msg01038.html

Here's another thread from 2018:

https://lists.debian.org/debian-user/2018/08/msg01433.html

Note that this time, Gene omitted the comma, and said that the
resolv.conf file "looks something like this"; IOW he's going from
memory rather than just catting the file.

And a thread from 2019:

https://lists.debian.org/debian-arm/2019/06/msg00046.html

This time the comma is gone, and Gene may or may not have actually
catted the file -- we can't be sure, because he does not paste the actual
terminal session including the shell prompt and the command issued.

As I've said, we've been through this for literally YEARS.

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web