[thelist] Illegal domain name on an intranet?

[Ken Schaefer]

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
: From: thelist-bounces at lists.evolt.org [mailto:thelist-
: bounces at lists.evolt.org] On Behalf Of Dominick Cancilla
: Subject: [thelist] Illegal domain name on an intranet?
: 
: I don't run a server so I haven't a clue about this, 
: but is it possible to set up an intranet so that it 
: will serve a domain with an illegal domain
: name? For example, x.net? I assume the answer is no, 
: but I hope to find out I'm wrong.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If you run an internal DNS server(s) you can create whatever domains you
want. These can be any top-level-domain, and any host name you want (as long
as it's within the DNS specification). For example, Active Directory defaults
to naming internal domains: <domainname>.local Local isn't a valid public
TLD, but since you're controlling name resolution for the internal clients,
it'll still work just fine.



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
: From: thelist-bounces at lists.evolt.org [mailto:thelist-
: bounces at lists.evolt.org] On Behalf Of Brian Cummiskey
: Subject: Re: [thelist] Illegal domain name on an intranet?
: 
: just one more thing to add to that...
: depending on which webserver you are running (IIS or apache)
: you will need to C:\intranet\ or whatever folder you are 
: putting your local site into a network share with proper 
: permissions as well.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I wasn't aware that this was a requirement for Apache, and it's certainly not
a requirement for IIS

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
: as an aside, you can reference the "explorer" view of a servers
: files/folders/share by typing in \\foo in IE, or in the run box
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

\\servrename is a UNC sharename, not a HTTP URI, and access is via SMB
(Server Message Block) -not- HTTP. Which means that server-side processing
such as PHP (or ASP.NET, or whatever) isn't going to occur. Additionally,
it's dependant on an SMB/CIFS share being present, rather than a HTTP website
being present. The two things are, generally, completely different.

Cheers
Ken

--
www.adOpenStatic.com/cs/blogs/ken/