DNS ISSUES Please help!

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

I have made no changes to anything on the network as of
late. With that said here is what is going on....

Basically my users can not
access "http://eplushealthcare.com I assume because their
domain name is the same. There are DNS Fowarders that
point to their ISP DNS Servers, but this does not seem to
work. There are also host files on their DNS that point
out but that isn't doing the trick.

If they Manually type the www part they can access all of
the site.

Any and all suggestions are welcomed. I am stumped!!??

thanks in advance.

-Art

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:2c4b01c47e1c$8d153d60$a601280a@phx.gbl,
Art Murphy <art@aoics.com> wrote their comments
Then Kevin replied below:
> I have made no changes to anything on the network as of
> late. With that said here is what is going on....
>
> Basically my users can not
> access "http://eplushealthcare.com I assume because their
> domain name is the same. There are DNS Fowarders that
> point to their ISP DNS Servers, but this does not seem to
> work. There are also host files on their DNS that point
> out but that isn't doing the trick.
>
> If they Manually type the www part they can access all of
> the site.

The only way you are going to be able to access the site is with the www.
The record required for the Domain name (same as parent folder) must point
to the IPs of Domain Controllers with File Sharing. This is for the SYSVOL
DFS share.

>
> Any and all suggestions are welcomed. I am stumped!!??


The only suggestion I can offer, if you must access the site without the
www, is to install IIS on the DCs, then redirect to
http://www.eplushealthcare.com on the Home Directory Tab of the Website
properties.


--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
================================================
--
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
================================================
http://www.lonestaramerica.com/
================================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
================================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
================================================

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

"Art Murphy" <art@aoics.com> wrote in message
news:2c4b01c47e1c$8d153d60$a601280a@phx.gbl...
> I have made no changes to anything on the network as of
> late. With that said here is what is going on....
>
> Basically my users can not
> access "http://eplushealthcare.com I assume because their
> domain name is the same. There are DNS Fowarders that
> point to their ISP DNS Servers, but this does not seem to
> work. There are also host files on their DNS that point
> out but that isn't doing the trick.
>
> If they Manually type the www part they can access all of
> the site.
>
> Any and all suggestions are welcomed. I am stumped!!??
>
> thanks in advance.
>
> -Art

Missing an alias record in the DNS perhaps? (CNAME)

Just make "eplushealthcare.com" an alias for the web server's
fully-qualified name on the DNS responsible for the eplushealthcare.com
domain.

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

AM> my users can not access "http://eplushealthcare.com I assume
AM> because their domain name is the same.

<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/dns-split-horizon-common-server-names.html>

AM> If they Manually type the www part

<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/web-allowing-omission-of-www.html>

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

M> Just make "eplushealthcare.com" an alias for the web server's
M> fully-qualified name [...]

That won't work.