Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #186944
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: sudo slow on DNS lookup, with invalid resolv.conf entries |
| Date | 2017-09-18 14:40 +0200 |
| Message-ID | <ur3vc-6je-9@gated-at.bofh.it> (permalink) |
| References | <uqRu1-6qe-1@gated-at.bofh.it> <uqYlP-2Ut-11@gated-at.bofh.it> <ur0H2-4j6-69@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon 18 Sep 2017 at 06:32:55 -0300, x9p wrote: (Please watch your attributioms; it confuses matters. x9p did not write this). > > This is the default from the last stretch install > > > > $ cat /etc/hosts > > 127.0.0.1    localhost > > 127.0.1.1    fujitsu.mydomain   fujitsu > > > > so if mydomain or localdomain is not working it will delay. > > > > 127.0.1.1 fujitsu fujitsu.mydomain > > > > will not delay because fujitsu is the name of the machine. > > > > in my case mydomain was added at installation time, because cable was > > plugged in and the computer (fujitsu) got its IP via the dhcp server on > > the > > local network. > > > > IMO you should look deeper in your use case and see why you get invalid > > setup. The problem might be somewhere else. > > > > regards > > My chosen machine name was "localhost", problem partially lies here. The hosts manual says each host should have a line like IP_address canonical_hostname [aliases...] By implication the catonical_hostname should be for one IP_address. You have (had?) root@localhost:~# grep localhost /etc/hosts 127.0.0.1 localhost 127.0.1.1 localhost The first line is ok; the canonical_hostname localhost has the address 127.0.0.1. The second line is not ok. The file /etc/hostname has the system hostname; it should not be "localhost". If it was "stretch" then the second line should be 127.0.1.1 stretch (This becomes a little more complicated if a mail server is one of the services being run on the machine). -- Brian.
Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: sudo slow on DNS lookup, with invalid resolv.conf entries "x9p" <debian-user@x9pneu.com> - 2017-09-18 01:50 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries deloptes <deloptes@gmail.com> - 2017-09-18 09:10 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries "x9p" <debian-user@x9pneu.com> - 2017-09-18 11:40 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Curt <curty@free.fr> - 2017-09-18 13:40 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Greg Wooledge <wooledg@eeg.ccf.org> - 2017-09-18 16:00 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Curt <curty@free.fr> - 2017-09-18 16:40 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries "x9p" <debian-user@x9pneu.com> - 2017-09-18 17:30 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Brian <ad44@cityscape.co.uk> - 2017-09-18 18:10 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries "x9p" <debian-user@x9pneu.com> - 2017-09-18 20:50 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Brian <ad44@cityscape.co.uk> - 2017-09-18 21:10 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Brian <ad44@cityscape.co.uk> - 2017-09-18 14:40 +0200
csiph-web