apache hostname resolution

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

Jeff <joesiege@gmail.com> wrote in news:1184072284.934837.305940
@k79g2000hse.googlegroups.com:

> 64.157.185.199:80

Obviously, as a test server you are not using a hostname that actually will
resolve. And, httpd process likely does not use the conventional path of
resolving names, i.e. hosts file first, then dns, therefore the httpd -S
does not look at your hosts file.

The result is likely a default IP address from your ISP address block.


Not sure though... I've never had the occasion to do any tests on that.



----== Posted via Newsfeeds.Com - Unlimited-Unrestricted-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

Is it possible that the results are simply cached?

Try flushing your DNS (resolved) cache & seeing if you get the same
results.

================================================== ========
How to Flush DNS in Linux:
/etc/rc.d/init.d/nscd restart

================================================== ========
How to Flush DNS in Microsoft Windows:

C:\>ipconfig /flushdns

================================================== ========
How to Flush DNS in Mac OSX:

bash-2.05a$ lookupd -flushcache

-#2pencil-
http://www.akroncdnr.com