Re: A Big Mess
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Sun, 12 Feb 2006 18:25:25 -0600
"Dom" <Dom@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7F4B98B2-3BDE-45EF-B4BB-F594B3BA03D2@xxxxxxxxxxxxxxxx
I have a rather confusing situation. I'm not sure if it is a IIS issue, DNS
issue or a little of both so I am going to cross post to both discussion
forums.
That is the CORRECT way to do it IF you (reasonably) cross-posting
a single message to both groups. Do NOT post separate messages; then
the experts in each group cannot see the other responses, you have to
check multiple locations, and anyone trying to learn cannot follow the
full story and your responses easily.
This is rather long but here we go...
* I have set up a new web server behind a firewall (Server 2k3).
* Web server also acts as DNS server
Public or private? For the public it must open AT LEAST UDP
53 inbound and responses from the DNS server or the external
users cannot take advantage of it.
(And in general you external DNS is BEST placed at your REGISTRAR.)
* I have multiple websites on new web server but am only tring to go live
with one right now (for testing purposes).
Is it the default site? Or is it dependent on host headers?
If it is the "default" site you can check it BY IP ADDRESS
and prove if the DNS is the likely problem -- if it works by
address then focus on DNS.
But if it is not the default site and you are using a single IP
then DNS is mandatory for "host headers" to work.
* Each website has its own WAN side IP address that translates through
firewall to it's own LAN IP. We have on NIC with multiple IPS assigned
internally.
Well, then in effecf it is PROBABLY the default site for it's
particular IP address.
* Website in IIS is set to point toward it's assigned WAN IP
As long as that address is PHYSICALLY on the web server this
should work.
* Name Server for website has been changed to point to new DNS server on
my
new network.
What does this mean?
The web server doesn't need DNS (or care which one it uses)
for WEB serving to work. It needs the clients to be able to find
it by name/ip.
* When I ping www.nmclawnscapes.com it resolves to the WAN IP assigned to
that website, however I receive no reply.
Ping is ICMP which is commonly blocked by some fire walls or
not routed.
Use Telnet to connect directly to the web server/site by both IP
and Name:
telnet www.sitename.com 80
telnet IP.address.web.server 80
IF you get a "BLACK" screen this is a GOOD thing.
Type something like: GET / HTTP/1.0<return><return>
(Two returns.)
If you see a bit of HTTP/html you have a working web server site
even if the files are messed up.
* If I ping my new name server it resolves to the name servers internal IP
but also times out.
Your DNS is working. The question is: Is it giving the
resolution (correct address) you want it to give.
* If i try to browse to www.nmclawnscapes.com I get either a BAd Request
(invalid Hostname) or a HTTP 400 Page Cannot be Displayed error. Depends
on
the browser.
Is this a public web site? Does www.Google.com work better
or worse.
If worse, then likely your internal DNS is not resolving the
Internet (should likely FORWARD) correctly.
Too many things going on. Cannot figure out where the problem lies.
Resolution for YOUR users of the Internet (and internal)
addresses is ALMOST COMPLETELY SEPARATE from
resolution of "your resources" for the Internet.
These should be debugged separated EVEN when the
same server does both jobs (and generally different servers
should do them.)
Any help would be GREATLY appreciated.
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
.
- References:
- A Big Mess
- From: Dom
- A Big Mess
- Prev by Date: Re: Host to Outside not resolving
- Next by Date: Re: DNS Resolution not working
- Previous by thread: A Big Mess
- Next by thread: Re: Annoying/Please HELP!
- Index(es):
Relevant Pages
|
