> -----Original Message----- > From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Pete Biggs > Sent: Saturday, August 25, 2018 2:30 PM > To: centos at centos.org > Subject: Re: [CentOS] Mail has quit working > > > > > > > > On 08/25/2018 03:35 AM, TE Dukes wrote: > > > > > Can't say that's what I expected. What about "getent hosts > 127.0.0.1"? > > > > > > > > 127.0.0.1 localhost > > > > > > OK. /etc/hosts isn't being used. You indicated earlier that you had > > > more hostnames in that file. They should show up there. > > > > > > Let's go back to pastebin. What are the contents of /etc/nsswitch.conf > > > and /etc/hosts, now? > > > > > > > Link to pastebin: > https://paste.fedoraproject.org/paste/97keKuhV4lMoLZ8DIrYT8w > > You are multiply defining localhost and localhost.localdomain. All > there should be is: > > 127.0.0.1 localhost.localdomain localhost > ::1 localhost6.localdomain6 localhost6 > I changed my /etc/hosts to the above. > But that's not the underlying issue, it's just a complication. What > the 'getent hosts 127.0.0.1' is showing is that the system is either > not retrieving host information from the /etc/hosts file or not > retrieving it all. That same command on my system returns > > 127.0.0.1 localhost.localdomain localhost > > i.e. the line identical to the one in /etc/hosts. Yours doesn't. What > does /etc/host.conf contain - does it have the line 'multi on' in it? Yes > > > > > > > > Are you running nscd, nslcd, or sssd? If so, you may need to stop them > > > or flush their cache. > > > > > > > None of the above are running > > Your nsswitch.conf files shows that you are retrieving information from > sssd for users. (But not for hosts, so it's not relevant here) > > > > > > What do you get if you "dig @localhost localhost +short". If that > > > doesn't return a "localhost" address, then the name server that you're > > > running has a broken configuration. > > > > ; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> @localhost localhost +short > > ; (1 server found) > > ;; global options: +cmd > > ;; connection timed out; no servers could be reached > > Are you running your own named? (I thought you said you were - this > output says you aren't.) > > P. Yes, named is running. Thanks!!