.internal and .local with windows 2000 were the MS preferred way to set up AD. it has NOTHING to know how to seperate local and public DNS. it has everything to do with place an organizational buffere in place that cant be messed by your linux admins who think they are AD Admin (I assume you fall into that category)
"The IP address for www.tvrage.com is 80.246.178.98. Try putting that in your address bar and see what you get. The IP address for epguides.com is 216.239.136.165 but try going there and you'll get the message "Unknown virtual host".
that is due to a method called Host Header Values (the site listens for for multiple urls on that IP and serves up whichever one you type in. If you were to place the FQDN and IP in your hosts file, then your browser would append the HHV to the GET request and the porper page will come upl.
Techdirt has not posted any stories submitted by Jeremy C. Schillinger.
Re: Re: Re: Toe in the water?
.internal and .local with windows 2000 were the MS preferred way to set up AD. it has NOTHING to know how to seperate local and public DNS. it has everything to do with place an organizational buffere in place that cant be messed by your linux admins who think they are AD Admin (I assume you fall into that category)
Re: Re: Was over a torrent freak and posted these ideas
"The IP address for www.tvrage.com is 80.246.178.98. Try putting that in your address bar and see what you get. The IP address for epguides.com is 216.239.136.165 but try going there and you'll get the message "Unknown virtual host".
that is due to a method called Host Header Values (the site listens for for multiple urls on that IP and serves up whichever one you type in. If you were to place the FQDN and IP in your hosts file, then your browser would append the HHV to the GET request and the porper page will come upl.