On Monday 19 March 2007 16:54, Frank Ellermann wrote:
Stuart D. Gathman wrote:
Using "museum" as host in an http URL also works: http://museum
It doesn't work if local DNS configuration specifies a domain or
search path. E.g. for /etc/resolv.conf on unix systems:
domain example.com
Interesting, I use "domain invalid" for this purpose on OS/2 in
file d:\mptn\etc\resolv (OS/2 uses TCP/IP stacks with BSD roots.)
Do you have the same issue for the following URLs:
1: http://museum/ (that's where I arrive when using "museum")
2: http://museum.
3: http://museum./ (that's where I arrive when using "museum.")
For the nslookup "searchpath" (only used by nslookup on my box) I
finally got rid of the bogus TLD "invalid" with "set nosearch" in
.nslookuprc
For me the first two get me to a .com site (Firefox has a guessing function
that's on by default). Only the last one gets me to the museum TLD site.
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.10) Gecko/20070302
Ubuntu/dapper-security Firefox/1.5.0.10
Scott K
-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to http://v2.listbox.com/member/?list_id=735