Re: Fairly new to DNS ... few Questions

From: David Taylor (mcp916removethis806_at_removethistoo@hotmail.com)
Date: 03/10/04


Date: Wed, 10 Mar 2004 14:42:23 -0600

your external, ISP hosted DNS should have an A record pointing for your
exteranal web host pointing to the address on the outside of your router.

If you are running DNS for internal use, it should contain a record for
itself using the internal address, as well as records for you clients, etc.

If you are not you will want to modify the "host" file on your workstation
to include an entry with the internal address and external host name of the
server. If you only have a few computers this is the way to go, because you
do not have to run DNS on your webserver.... a security risk if the server
is hacked.

For convience you can use the same host name internally as well as
externally...but with separate IP addresses. By doing so, you'll be able to
access the server by name from either inside or outside.

"E.Heaton" <anonymous@discussions.microsoft.com> wrote in message
news:a9f701c406cd$8ceaffd0$a101280a@phx.gbl...
Hi,
Please bare with me, as this is all new.

I'm trying to get a web server runng from my home business. I'm using
Windows 2003 Standard running IIS 6.0, behind a Netgear Router connected
to a cable modem. Port forwarding is successfully enabled on the router,
and working correctly. I also have a registered domain name, and dns
service (not hosted by myself) that's connected to my WAN IP address.

I had the server set up before so it was actually doing the routing, and had
DNS successfully configured for a forward look-up zone worked with my
.com name. It was setup and working before, but I'm not sure I completely
understood what was happening. Now that its behind the router, I'm even
more unsure how to properly set this up.

My questions are as follows:
Should my host(A) records be pointing to my internal IP address or
External
IP address?

I would like to be able to access my server from the domain.com address
from both my internal network, and externally. The way the netgear router is
setup, I can't access my server internally via the IP address... is there a
way
to work around this?

...and Finally, once setup ...how exactly is this working?



Relevant Pages

  • Re: Cannot connect to RWW from home PC
    ... eth0 172.26.0.1/16 Extra none ... That would be the address you need a DNS record for. ... One question - if I reset the Thomson Router will that clear all the ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot connect to RWW from home PC
    ... No 10.0.0.138 is the address used to log onto Thomson's router to make the ... On the DNS question I can add an MX record in the DNS area of GoDaddy's ... eth0 172.26.0.1/16 Extra none ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... NIC, you need to specify an external DNS server for DNS, instead of the ... Both NICs should point to his internal IP for DNS. ... forward ports to it reliably in the router. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot connect to RWW from home PC
    ... You say "And in the router you need to forward to your external nic IP" ... You say "You need the domain hoster to setup a DNS record that will be ... We have rerun CEICW sort of hoping it would sort out the router but no ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... Even a single-NIC configuration should have ONLY the LAN IP of the server as ... Then you can run the CEICW or use the DNS console to enter ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)

Loading