Re: DNS Problem

Thanks Ace, I didn't know if you were still watching this post. Yes, all
workstations point to the DC as their primary.

Sam

"Ace Fekay [MVP]" <PleaseAskMe@xxxxxxxxxxxxxx> wrote in message
news:uOnmdWRdIHA.1164@xxxxxxxxxxxxxxxxxxxxxxx
In news:Ohns7fNdIHA.5788@xxxxxxxxxxxxxxxxxxxx,
SPG <nomail@xxxxxxxxxx> typed:
OK Ace, here it is: I installed the AV without any problems. It is
running just great. I created the delegate for www in our zone. It
asked for DNS servers & their IP's and I gave it to them. Now the
weird part: without doing anything to IIS. That same day 2 machines
could access our website and go anywhere and back, but any other
workstation would either bring up the default website (like "Under
Construction") or just crash out and said "see your admin". The next
day it would be only 1 different machine that would access the
website and all of the others would get the above errors. I then
tried redirecting with the default website in IIS but still got the
same errors with all machines and not 1 machine could access the
website. Today I put the default website in IIS back to its original
setup, deleted the delegate, and did a "A" record in the zone with
the www.domain.com and its IP address. Everyone can fly anywhere on
the net, including our website. I did nothing else to IIS and I am
going to leave it that way. By the way, this all started when I
installed a newer version of our AV. That newer version is the one I
put back in. We use Panda for our workstations and our servers, and
have for a number of years.
Thanks for all of the help

I am "outa" here,

Sam

I think with the inconsistency you saw with some machines getting the DC's
site and getting the external site is because you never know which DNS the
workstation is querying. If querying the ISP's DNS, they will get the
external site IP resolved, and if the internal, they are getting the DC's
default site, especially if you type in http://domain.com (without the
www), you will reach the DC's default website. That's the LdapIpAddress
all DCs register into DNS and can be modified with reg entries, but you
don't really want to do that. Assuming you changed all your machines to
ONLY use your internal DNS, you can overcome this with in IIS' Default Web
Site properties, do a redirect to www.domain.com. This way your users can
type in http://domain.com and get to it.

As for the A record, the site you are probably going to is a CNAME.
Delegations have problems with them. This can be tested wtih nslookup on
the domain name.

Ace





.

Relevant Pages

  • Re: DNS Problem
    ... asked for DNS servers & their IP's and I gave it to them. ... without doing anything to IIS. ... That same day 2 machines ... workstation would either bring up the default website (like "Under ...
    (microsoft.public.windows.server.dns)
  • Re: Permission Problems SBS2003 R1
    ... website on the SBS server? ... Default permissions and user rights for IIS 6.0 ... Step 3: Please check the permissions in IIS manager: ... Step 4: Re-running CEICW on SBS server: ...
    (microsoft.public.windows.server.sbs)
  • RE: HTTP Error 403.6
    ... Open Server Management and expand to Internet Information Services node. ... Check Default Web Site setting under IIS ... Under Website, right click Default Website, select Properties. ... Check ISAPI Filter of Default Web Site setting. ...
    (microsoft.public.windows.server.sbs)
  • RE: RWW
    ... Please rerun the CEICW, this helps us to configure network and IIS ... Open Server Management console, ... Under Website, right click Default Website, select Properties ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • IIS 5.0 and Netscape Authentication
    ... under IIS 5.0 in a Windows 2000 Active Directory. ... Netscape 4.x and IE 5.x running on a client or local to the server. ... Now under IIS Manager create a website that that uses the "testwebsite" ... "test" user account is a valid user account and authentication is complete. ...
    (Focus-Microsoft)