Re: apache hostname resolution (strange problem)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Jeff,

did you try to restart the nscd ? maybe it's still cached.

OR make a reboot to be sure if you can.

Jeff Fulmer schrieb:
I have the oddest situation. I have a test server on the LAN. I added a
host entry for www.myserver.com (actual name changed to protect the
innocent). I can ping www.myserver.com and my resolved address matches the
host entry. Life is grand, no?

/usr/sbin/ping www.myserver.com
PING www.myserver.com: 64 byte packets
64 bytes from 10.37.74.24: icmp_seq=0. time=0. ms

I have apache configured with a virtual host for www.myserver.com. Watch
what happens when I check my virtual hosts with httpd -S. I get the PUBLIC
internet address for www.myserver.com:

$ bin/httpd -S
VirtualHost configuration:
64.157.185.199:80      www.myserver.com
(/usr/local/httpd/conf/vhosts/80_myserver.com:5)
wildcard NameVirtualHosts and _default_ servers:
*:443                  is a NameVirtualHost
         default server www.myserver.com
(/usr/local/httpd/conf/vhosts/443_myserver.com:4)
         port 443 namevhost www.myserver.com
(/usr/local/httpd/conf/vhosts/443_myserver.com:4)
*:80                   is a NameVirtualHost
         default server www.default.com
(/usr/local/httpd/conf/default.conf:4)

Okay, so I went to nsswitch.conf and TURNED DNS OFF. At this point,
resolver's only recourse is to use /etc/hosts.  No matter, the answer is
EXACTLY the same:

$ bin/httpd -S
VirtualHost configuration:
64.157.185.199:80      www.myserver.com
(/usr/local/httpd/conf/vhosts/80_myserver.com:5)
wildcard NameVirtualHosts and _default_ servers:
*:443                  is a NameVirtualHost
         default server www.myserver.com
(/usr/local/httpd/conf/vhosts/443_myserver.com:4)
         port 443 namevhost www.myserver.com
(/usr/local/httpd/conf/vhosts/443_myserver.com:4)
*:80                   is a NameVirtualHost
         default server www.default.com
(/usr/local/httpd/conf/default.conf:4)

Obvioulsy apache's getting that answer from DNS. That IP address is not
listed anywhere on the server. I don't understand where, how or why it's
resolving www.myserver.com.  Any insight?

Jeff


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
   "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx



---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx


[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux