[ List Archives Home ] [ Thread index for 2008 ] [ Date index for 2008 ] [ Author index for 2008 ]


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
It sounds like your tech guys are correct on this one: a 
*.library.prima.edu would encompass www.library.prima.edu, which is a bad 
thing.

Joe R.

At 01:46 PM 4/15/2003 -0700, you wrote:
>All,
>
>We in the library are being told by our network people that there is a 
>problem with the way our servers are named and this will prohibit us from 
>setting up the WAM that
>will eliminate the need for our patrons to configure their browsers for 
>the proxy serve.
>
>The issuse is this:
>
>The directions state that the DNS must be set up to accept wildcards.  Our 
>library (III) server is named library.pima.edu.  Our other web server is named
>www.library.pima.edu.  I'm being told that *.library.pima.edu will not 
>work.  It is the networking staff's contention that if we configure the DNS to
>*.library.pima.edu, we will no long be able to access the server named 
>www.library.pima.edu because the DNS will return the primary library 
>server address for it.
>
>That doesn't make sense to me.  Wouldn't *.library.pima.edu include 
>www.library.pima.edu?  Of course, what I know about DNS wouldn't fill a 
>thimble but this is
>counter-intuitive.
>
>Has anyone else overcome a situation like this?
>
>Thanks.
>
>--
>
>Travis Spence
>Library Specialist
>Pima Community College
>Tucson, AZ
>
>
>--
>This message was distributed through the Innovative Users Group INNOPAC list
>Public replies:  INNOPAC@xxxxxxxxxx
>Update your subscription options: 
>http://innopacusers.org/list/listinfo/innopac

Joe Reimers
Technology Support Assistant
Notre Dame Law Library
(574) 631-5994