DNS error - Someone here that can help?

[Bernie]

my company has registered domain, name server is our
server and secondary is our tech provider (not ISP). DNS
has been running for over a year - no issues at all to
this point. Our web server (sits on DMZ) is Primary DNS
with our Tech Provider as secondary (Zone change Notify is
configured pointing to their servers) 3 weeks ago we
started hosting our own website. In DNS I specified A host
record and configured the IIS. Everything came up and
running like it's supposed when configured correctly.

Here is what's going on; starting last week our website
went down (page would not be displayed), in your browser
you would get "domain not found" I did nslookup and
domain points to the correct IP. Then magically website
came back up within minutes. yesterday same thing
happened, but this time it was down for about 2 hours, I
checked IIS - ok - last night it was fine, then this
morning we are down again using domain name.

If you enter our public IP - site comes up - we have OWA
running fine using domain name (Exchange server running on
a different 2000 advanced server). nslookup again points
to the right ip, our DNS configuration has not been
changed.. I have rebooted server, restarted IIS. (I don't
think it is IIS issue) and it has not helped. When I ping
our domain it does not time out, it simply says: "Ping
request could not find host "www.ourname.com" Please check
the name and try again". Again Ping to our public IP
replys.

We have our domain registered with networksolutions..
could this be an issue on their end.. or what am I missing
here?

I have the latest SPs on our server

I hope someone here can help me head in the right
direction, hope this makes sense

BTW.. this is a 2000 server we are dealing with

Thanks in advance

Bernie

 

[Berni]

We are up and running again using domain name, domain name
responds again to ping requests.... this is getting
strange. At this point I don't think it is a configuration
issue, but that's why I came here... for pointers

 

[Kevin D. Goodknecht [MVP]]

In Berni <[email protected]> posted a question
Then Kevin replied below:
: We are up and running again using domain name, domain name
: responds again to ping requests.... this is getting
: strange. At this point I don't think it is a configuration
: issue, but that's why I came here... for pointers
:
:
:: -----Original Message-----
:: my company has registered domain, name server is our
:: server and secondary is our tech provider (not ISP). DNS
:: has been running for over a year - no issues at all to
:: this point. Our web server (sits on DMZ) is Primary DNS
:: with our Tech Provider as secondary (Zone change Notify is
:: configured pointing to their servers) 3 weeks ago we
:: started hosting our own website. In DNS I specified A host
:: record and configured the IIS. Everything came up and
:: running like it's supposed when configured correctly.
::
:: Here is what's going on; starting last week our website
:: went down (page would not be displayed), in your browser
:: you would get "domain not found" I did nslookup and
:: domain points to the correct IP. Then magically website
:: came back up within minutes. yesterday same thing
:: happened, but this time it was down for about 2 hours, I
:: checked IIS - ok - last night it was fine, then this
:: morning we are down again using domain name.
::
:: If you enter our public IP - site comes up - we have OWA
:: running fine using domain name (Exchange server running on
:: a different 2000 advanced server). nslookup again points
:: to the right ip, our DNS configuration has not been
:: changed.. I have rebooted server, restarted IIS. (I don't
:: think it is IIS issue) and it has not helped. When I ping
:: our domain it does not time out, it simply says: "Ping
:: request could not find host "www.ourname.com" Please check
:: the name and try again". Again Ping to our public IP
:: replys.
::
:: We have our domain registered with networksolutions..
:: could this be an issue on their end.. or what am I missing
:: here?
::
:: I have the latest SPs on our server
::
:: I hope someone here can help me head in the right
:: direction, hope this makes sense
::
:: BTW.. this is a 2000 server we are dealing with
::
:: Thanks in advance
::
:: Bernie
::
:: .

When you ran nslookup for www.ourdomain.com which DNS server did you specify
to look in?

For one thing in an Active Directory domain environment, you should not use
any external DNS servers in any NIC of any domain member, if that external
DNS server does not hold an exact copy of your AD Domain zone. If there are
names you need to resolve that are only on your service provider's DNS,
provided they are not in the same domain name as your internal domain, on
the forwarders tab of your DNS server, set a forwarders to that provider
only, then check "Do not use recursion" then your DNS must resolve external
names through your service provider's DNS.
That being said, if you cannot connect www.ourname.com then either no www
record exists in the ourname.com zone or the record points to an IP address
that is incorrect.
If your ourname.com external name is the same name as the internal AD Domain
name, then you will need to add the www record to your internal domain zone
since it will not forward requests for host records it does not have within
the domain zone.