Can't resolve own address

[jaypeerocks]

Hi all,

I'm mucking around with W2K server and can't get to my own web site
from the machine that's hosting it. Sounds like a DNS issue, but I'm a
bit of a DNS noob and don't know where to look to fix it.

I started with a W2K server, ran dcpromo to create a single domain.
Installed DNS Server. Didn't install DHCP server as the router is
doing it. Gave the DC a static internal IP of 192.168.1.1.

In DNS, I removed the root forward lookup zone and configured a
forwarder to my ISP's DNS.

Then I set up an ASP page in the default web site, just says "Hello!".

Did the dyndns thing and installed an IP updater on the machine.

From the machine that hosts the site, I can browse to it using the

internal IP, the external IP and the machine name, but not from the
domain name itself.

When I browse to it from another PC on the network (by internal IP,
extarnal IP, machine name and domain name) , it works fine, but not
from the machine that hosts it.

Any suggestions?

 

[Herb Martin]

Hi all,

I'm mucking around with W2K server and can't get to my own web site
from the machine that's hosting it. Sounds like a DNS issue, but I'm a
bit of a DNS noob and don't know where to look to fix it.

We all had to learn and are still learning.

I started with a W2K server, ran dcpromo to create a single domain.
Installed DNS Server. Didn't install DHCP server as the router is
doing it. Gave the DC a static internal IP of 192.168.1.1.

All irrelevant to the web server.

In DNS, I removed the root forward lookup zone and configured a
forwarder to my ISP's DNS.

So your web server is external?

Does it share the same (public) name as your private domain name?

Then I set up an ASP page in the default web site, just says "Hello!".

Then it cannot be a DNS issue since you reached (presumably the
correct) the Web server.

Did the dyndns thing and installed an IP updater on the machine.

internal IP, the external IP and the machine name, but not from the
domain name itself.

Which domain name? How does that related to your
internal Domain name?

Can you ping? Can you nslookup and get the correct DNS
resolution? What happens if you specify each of these
DNS servers (IP) on the nslookup command: internal DNS,
forwarder DNS, unrelated DNS (e.g., 4.2.2.1)

When I browse to it from another PC on the network (by internal IP,
extarnal IP, machine name and domain name) , it works fine, but not
from the machine that hosts it.

Run the nslookup command against every DNS server
specified on this "DNS client".

nslookup www.example.com IP.Address.DNS.server

Be explicit and run such commands against every DNS
server involved and on both working and non-working
DNS clients until you isolate the trouble.

Internal DNS Clients must use STRICTLY the (internal)
DNS Server (set) and must NOT try to mix internal and
external DNS servers on their client NIC->IP properties.

It is the job of their (internal) DNS server to deal with
forwarding or otherwise resolve external names.

 

[Jmnts]

Hi

I started with a W2K server, ran dcpromo to create a single domain.
Installed DNS Server. Didn't install DHCP server as the router is
doing it. Gave the DC a static internal IP of 192.168.1.1.

- You don't need to create a domain to host intra/inter webpages pages, you
only need Dns service.
- Let me rephrase this, Don't use DC to host Web pages specially if your Dc
is used as Internal Domain Controller (Security purposes), the Web servers
that are accessible to the internet shouldn't even be members of any domain.

In DNS, I removed the root forward lookup zone and configured a
forwarder to my ISP's DNS.

Is the "root forward lookup zone " the "." zone or another zone that you've
created?
The "forwarder to my ISP's DNS" is setup to the "All other Domains" or to a
especific domain (Conditional Forwarding)?
-- if it is a especific domain, is the especific domain name the same
name that the web site that you're trying to setup?
-- If yes - Then your site is being resolved by your ISP dns and not by
your internal dns, so you don't need a internal dns to resolve the Web site.
-- If No - Then this is a wrong configuration (remove the ISP ipaddress
from forwarding tab) because only your dns knows about your domain, however
if you want that internet clients reach your web site, you must register the
dns name for your web site, and make sure that your ISP (Normally) or your
public Dns provider has a record (CNAME normaly) that maps the Web site name
to your router public IP Address, then all you have to do is to open the
required ports (at least the TCP80) and map them to your IIS server Ip
Address).

Then I set up an ASP page in the default web site, just says "Hello!".

Nice page.. just kiding...

internal IP, the external IP and the machine name, but not from the
domain name itself.

Sounds like you need a CNAME to resolve the www thing... do you have it?
How do you have the IIS Hostheader configured?
How do you type the dns name of the site in the browser?
something like www.domain.com
What errors are you getting in the I.E browser?

can you ping the www.domain.com?
if you run nslookup www.domain.com what is the ipaddress that you get?

When I browse to it from another PC on the network (by internal IP,
extarnal IP, machine name and domain name) , it works fine, but not
from the machine that hosts it.

sure, because the IP Address are related with the Dc and the domain name to.
How do you type the dns name of the site in the browser?
something like www.domain.com or domain.com?

can you ping the www.domain.com?
if you run nslookup www.domain.com what is the ipaddress that you get?

Make sure that your internal clients use ONLY the internal dns server.

 

[Sam Jones]

I started with a W2K server, ran dcpromo to create a single domain.

Installed DNS Server. Didn't install DHCP server as the router is
doing it. Gave the DC a static internal IP of 192.168.1.1.

Just out of curiousity, what's the gateway address of the router?

When I browse to it from another PC on the network (by internal IP,
extarnal IP, machine name and domain name) , it works fine, but not
from the machine that hosts it.

Sounds like a CNAME (common name) problem.

Sam