DNS problem?

[EnderEd]

I have one W2K Server running Active Directory, setup with Forward
Zone Lookup. The server's domain name is domainname.lan.

Our website's name is domainname.com, and is hosted outside of our
lan. To access our website/webmail, we use domainname.com:8443 for
administration login.

All of this works fine OUTSIDE of our lan. But it's hit or miss,
mostly miss, from the lan side. Sometimes our website and admin are
accessible, but sometimes they just time out.

I rechecked our Forward Zone Lookup settings, and they're pointing to
our ISPs two DNS servers and our internal firewall/router (x.x.x.1).
There is one network connection on our server (x.x.x.100/255.255.255.0/
x.x.x.1). The lone DNS entry on our server's lone network connection
is set for the server itself (x.x.x.100).

Any ideas?

Thanks,

--EnderEd

 

[Debo]

I have one W2K Server running Active Directory, setup with Forward
Zone Lookup. The server's domain name is domainname.lan.

Our website's name is domainname.com, and is hosted outside of our
lan. To access our website/webmail, we use domainname.com:8443 for
administration login.

All of this works fine OUTSIDE of our lan. But it's hit or miss,
mostly miss, from the lan side. Sometimes our website and admin are
accessible, but sometimes they just time out.

I rechecked our Forward Zone Lookup settings, and they're pointing to
our ISPs two DNS servers and our internal firewall/router (x.x.x.1).
There is one network connection on our server (x.x.x.100/255.255.255.0/
x.x.x.1). The lone DNS entry on our server's lone network connection
is set for the server itself (x.x.x.100).

Any ideas?

Thanks,

--EnderEd

Ok, just so that I am 100% clear you have both your domain name as
well as your website itself hosted via third party? Do you have any
ACL's on your firewall that prohibit anything other than, say, port 80
(http) traffic to go out? Maybe you need to open port 8443 outbound.

 

[EnderEd]

Ok, just so that I am 100% clear you have both your domain name as
well as your website itself hosted via third party? Do you have any
ACL's on your firewall that prohibit anything other than, say, port 80
(http) traffic to go out? Maybe you need to open port 8443 outbound.

Yes, and yes. The domain name is "hosted"/registered by Network
Solutions, and my website is hosted with websytz.com (DNS entries:
NS5.WEBSYTZ.COM and NS6.WEBSYTZ.COM). There are no ACL's enabled on
the firewall. Like I said, sometimes our LAN side workstations have no
problem accessing via port 8443, but many times they do. In fact, when
the workstations have a problem, so does the server-- I cannot get to
the website (80) nor administration (8443) from anywhere within my
network when it's awry. Then suddenly, for no discernable reason,
everyone plays nicely. One time I was able to force fix it by doing a
flushdns on the server, but subsequent attempts at that, including a
reboot, has no effect. But while we're having problems internally, no
one outside our network has a problem reaching either 80 or 8443,
ever.

Thanks again,

--EnderEd

 

[Debo]

Yes, and yes. The domain name is "hosted"/registered by Network
Solutions, and my website is hosted with websytz.com (DNS entries:
NS5.WEBSYTZ.COM and NS6.WEBSYTZ.COM). There are no ACL's enabled on
the firewall. Like I said, sometimes our LAN side workstations have no
problem accessing via port 8443, but many times they do. In fact, when
the workstations have a problem, so does the server-- I cannot get to
the website (80) nor administration (8443) from anywhere within my
network when it's awry. Then suddenly, for no discernable reason,
everyone plays nicely. One time I was able to force fix it by doing a
flushdns on the server, but subsequent attempts at that, including a
reboot, has no effect. But while we're having problems internally, no
one outside our network has a problem reaching either 80 or 8443,
ever.

Thanks again,

--EnderEd- Hide quoted text -

- Show quoted text -

post the error you recieve in IE when you try and get to the site from
within your network

 

[EnderEd]

post the error you recieve in IE when you try and get to the site from
within your network

Posted below. And here's another kicker. I have an acquaintance who
also uses webstyz. When my url is inaccessible, his is accessible, 80
and 8443, without issue! So I really think it has something to do with
my domain only, which is why I suspect the W2K AD server.

**********************************
http://sea.search.msn.com/dnserror.aspx?FORM=DNSAS&q=webmail.corpmktg.com

We can't find "webmail.corpmktg.com"

You can try again by typing the URL in the address bar above.
Or, search the Web:

And, firefox tells us:

Server not found



Firefox can't find the server at webmail.corpmktg.com.



* Check the address for typing errors such as

ww.example.com instead of

www.example.com



* If you are unable to load any pages, check your computer's
network

connection.



* If your computer or network is protected by a firewall or
proxy, make sure

that Firefox is permitted to access the Web.

 

[Debo]

Posted below. And here's another kicker. I have an acquaintance who
also uses webstyz. When my url is inaccessible, his is accessible, 80
and 8443, without issue! So I really think it has something to do with
my domain only, which is why I suspect the W2K AD server.

**********************************http://sea.search.msn.com/dnserror.aspx?FORM=DNSAS&q=webmail.corpmktg...

We can't find "webmail.corpmktg.com"

You can try again by typing the URL in the address bar above.
Or, search the Web:

And, firefox tells us:

Server not found

Firefox can't find the server at webmail.corpmktg.com.

* Check the address for typing errors such as

ww.example.com instead of

www.example.com

* If you are unable to load any pages, check your computer's
network

connection.

* If your computer or network is protected by a firewall or
proxy, make sure

that Firefox is permitted to access the Web.- Hide quoted text -

- Show quoted text -

Have you tried accessing it via IP Address instead of dns name?