Re: Loopback issues

David Schwartz wrote:


You might be in the domain 'mydomain.com' and ping might be trying
'localhost.mydomain.com' first.

This is exactly the case.... it is appending domain name to the localhost.

the order in resolving is as follows
hosts
dns
infact when I attempt to ping it this is exactly the case. My problem is that the system mails a report to root@localhost which I am not receiving.
.

Relevant Pages

  • Re: no name resolution on local domain
    ... You are correct about dig (and the other DNS query tools) ignoring ... server running on localhost even if localhost is not ... You need to have a line referring to hosts, ...
    (comp.os.linux.networking)
  • Re: Gnome Ethernet Very Slow
    ... what sholud reslov.conf & hosts have for gnome to acces the router/internet properly? ... ::1 localhost localhost.my.domain ... >>Danny Browne ... > Check your DNS settings, make sure resolv.conf points to a valid DNS ...
    (freebsd-questions)
  • Re: Event ID 7063
    ... > Event Source: DNS ... query for localhost to the root servers, the weird thing about that is DNS ... is in the hosts file. ...
    (microsoft.public.win2000.dns)
  • Re: Client Discovery
    ... > which means i should only have 1249 hosts as per DNS, ... This was done to prevent dead hosts in Active directory to be ... Keep in mind that resolving the name can be done in more ways then just ... Kim Oppalfens ...
    (microsoft.public.sms.admin)
  • Re: VB6 DCOM weirdness with HOSTS file after installation of XP SP2
    ... All TCP/IP s/w should be resolving addresses the same way, e.g. HOSTS first, ... then DNS. ... > problem on a local machine and then only if I try to use the local machine ...
    (microsoft.public.windowsxp.general)