I'm probably talking out of my hat, but when I have issues like this, I look
at WINS and also flush the resolver cache on a workstation...
These things typically shake out after a few days, except for WINS,
sometimes I need to delete the record manually.
On Fri, May 28, 2010 at 9:09 AM, David Lum <[email protected]> wrote:

>  I have an internal website we connect to by 
> http://<DNSAlias<http://%3cdnsalias/>>.
> This morning I changed the alias to point to a new server, but while the
> http://FQDN <http://fqdn/> of the alias works, using just 
> http://hostnamedoesn’t.
>
>
>
> Example: DNS alias is a CNAME of SharePointNew pointing to a host name of
> ServerA, and 
> HTTP://SharePointNew.ourcompany.local<http://sharepointnew.ourcompany.local/>works,
>  but
> http://SharePointNew <http://sharepointnew/> does not.
>
>
>
> That it would be a NetBIOS thing right? We use WINS, but I see no entry for
> COMMONS that would tell me something other than DNS is resolving that host
> name.
>
> *David Lum** **// *SYSTEMS ENGINEER
> NORTHWEST EVALUATION ASSOCIATION
> (Desk) 971.222.1025 *// *(Cell) 503.267.9764
>
>
>
>
>
>
>
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to