Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 Nov 1999 11:16:11 -0500 (EST)
From:      "Mr. K." <bsd@a.servers.aozilla.com>
To:        Dag-Erling Smorgrav <des@flood.ping.uio.no>
Cc:        David G Andersen <danderse@cs.utah.edu>, freebsd-security@FreeBSD.ORG
Subject:   Re: localhost.org
Message-ID:  <Pine.BSF.3.96.991118111140.1561A-100000@inbox.org>
In-Reply-To: <xzpk8nfyea3.fsf@flood.ping.uio.no>

next in thread | previous in thread | raw e-mail | index | archive | help
> You should have an entry for localhost in the inbox.org zone file:
> 
> localhost               IN      A       127.0.0.1
> 
yep, I already had this but it was ignoring this.  in fact,
localhost.inbox.org would give me 127.0.0.1, localhost. would give me
127.0.0.1, but localhost would give me a.b.c.d.  Turns out that one part
domains automatically try the search first.

> and you should consider setting your search path explicitly in
> /etc/resolv.conf.
This solved the problem.

> Alternatively, put 'hosts' before 'bind' in /etc/host.conf and make
> sure /etc/hosts contains an entry for localhost. You can use
> /etc/hosts to override other stuff, too; e.g. make ad.doubleclick.net
> point to a dummy httpd that returns 404 no matter what URL you
> request.
> 
This seems like a good idea in any case, as it will defeat a hacker who
manages to comprimise your nameserver.  At least for those listings
included in /etc/hosts.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.991118111140.1561A-100000>