trafficserver-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reindl Harald <>
Subject Re: Unable to locate the server named "localhost (2)"
Date Fri, 08 Mar 2013 10:36:38 GMT

Am 08.03.2013 11:29, schrieb Luca Rea:
> OpenDNS:
> Server:
> Address:
> ** server can't find localhost: NXDOMAIN
> Server:
> Address:
> ** server can't find localhost: NXDOMAIN
> I confirm your note about MTA

surely, you can find examples enough which does
not resolve as you find much more wrong configured
nameservers ignoring TTL, mangle responses and so

for me counts what RFC's are saying and on what widely
used services rely not which wrong configured ones
someone shows me trying to prove it is common

   Note that all domains that contain hosts should have a "localhost" A
   record in them.

   People maintaining zone files with the Serial number given in dotted
   decimal notation (e.g., when SCCS is used to maintain the files)
   should beware of a bug in all BIND versions: if the serial number is
   in Release.Version (dotted decimal) notation, then it is virtually
   impossible to change to a higher release: because of the wrong way
   that notation is turned into an integer, it results in a serial
   number that is LOWER than that of the former release.

4.1 Boot file setup

   Certain zones should always be present in nameserver configurations:

           primary         localhost               localhost
           primary    127.0
           primary        255
           primary          0

   These are set up to either provide nameservice for "special"
   addresses, or to help eliminate accidental queries for broadcast or
   local address to be sent off to the root nameservers.  All of these
   files will contain NS and SOA records just like the other zone files
   you maintain, the exception being that you can probably make the SOA

View raw message