Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


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

An unusual dns question



Thanks for reading this. I've got an unusual question about dns.

On my RH 7.3 box, if I use Netscape and enter 
http://listman.redhat.com/mailman/listinfo/redhat-list, the browser 
stalls and finally times out. I can see the dns query going out and 
being answered, and then a series of connect attempts to port 80, with 
no answers from listman.redhat.com.

On Windows 95, if I use Netscape and enter the same URL, I see the dns
query going out and being answered, and then a connect attempt AND 
ANSWER to PORT 443! The page comes up ok, albeit as https instead of http.

If I enter https instead of http on the Redhat box, it also renders the 
page correctly.

The question: how did the windows version of netscape know it should 
attempt port 443? There were NO attempts on port 80 before the port 443
traffic, so I assume that the dns query provided the information somehow.

Please tell me if that makes sense, or supply any other information 
you can. Thanks in advance.

Bill

--
Bill Horne
If you seek truth, do not look to the past or the future. Look inside.





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org