DNS problem?

[Me]

I have 3 systems behind a linksys router.
One of them is a Windows 2000 server. I have DNS service installed on it.
The systems name is scrappy and the IP is 192.168.1.2 In the DNS paramaters
I include a forwarded to 192.168.1.1, the address of my router.

It appears to work, all my clients (2000 workstation and 98) that use a DNS
of 192.168.1.2 can get to the Internet

Here's the problem. When the other 2 nodes attempt to connect to
http://scrappy or the FQDN, I get a prompt from my router for authentication
credentials. I want it to go the web page I have set up on http://scrappy

My DNS is registered on the Internet through dnydns.org.


Any ideas?

 

[Kevin D. Goodknecht Sr. [MVP]]

In Me <[email protected]>
posted their concerrns,
Then Kevin D4Dad added his reply at the bottom.

I have 3 systems behind a linksys router.
One of them is a Windows 2000 server. I have DNS service installed on
it. The systems name is scrappy and the IP is 192.168.1.2 In the DNS
paramaters I include a forwarded to 192.168.1.1, the address of my
router.

It appears to work, all my clients (2000 workstation and 98) that use
a DNS of 192.168.1.2 can get to the Internet

Here's the problem. When the other 2 nodes attempt to connect to
http://scrappy or the FQDN, I get a prompt from my router for
authentication credentials. I want it to go the web page I have set
up on http://scrappy

My DNS is registered on the Internet through dnydns.org.


Any ideas?

Internally behind your router you will have to access your web site by its
private address.
If you use host headers create a forward lookup zone with the FQDN of your
dnydns.org name for it to work and not interfere with any other dyndns.org
names the zone must be something like "scrappy.dyndns.org" (with out the
quotes, if that is the correct name) in that zone create a blank host
pointing to the web servers private address. It will bark at you and say
(same as parent folder) is not a valid host name, click OK create the record
anyway.

Enternally, it will be accessed by the public IP then you router will must
forward incoming connections on port 80 to the private IP of your web
server.