Host resolution

[mrlynx79]

Hi!

I have a Server 2003 with IIS and a coupe of websites running on my network.
I can reach them from internet by friendly name but on my lan only by IP.
What do i need to do to be able to reach the websites by friendly name on my
lan?

// JJL

 

[Michael Johnston [MSFT]]

First you'll need name resolution. Who are your clients pointing at for DNS? If the domain name used to reach these sites is a
Internet registered name, any internet DNS server should get you there. If it's a private DNS domain, then the clients can only
point to the internal DNS server hosting this zone. What is the IP address of the site you are trying to reach? If this IP is bound to
the external Interface of your Firewall or router and this is the IP address the clients are attempting at connect to, this may not
work. Many firewalls will report this as a spoof attack. For instance, if the external interface of the firewall recieves a packet that
is sourced from an internal IP, the firewall may assume this is a spoofed packet and dropp it. If that is the case, you'll need to
make sure the internal clients access the web site via an internal IP address.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.

 

[mrlynx79]

Hi!

The DNS and the Web server are in the same Windows 2003 server. My
firewall/router has port 80 forwarded to the server. I have a dyndns adress
pointing at my routers internet ip.

I can get to the website from outside my network by typing my dyndns adress.

My clients are pointing at my dns server for name resolution. In DNS i have
(dont know english term, i have swedish language on my server) forward set
to my isp's dns.

Hope this is enough information for you. Im not so good at english but im
trying to explain as good as i can.

// JJL

First you'll need name resolution. Who are your clients pointing at for

DNS? If the domain name used to reach these sites is a

Internet registered name, any internet DNS server should get you there.

If it's a private DNS domain, then the clients can only

point to the internal DNS server hosting this zone. What is the IP

address of the site you are trying to reach? If this IP is bound to

the external Interface of your Firewall or router and this is the IP

address the clients are attempting at connect to, this may not

work. Many firewalls will report this as a spoof attack. For instance,

if the external interface of the firewall recieves a packet that

is sourced from an internal IP, the firewall may assume this is a spoofed

packet and dropp it. If that is the case, you'll need to

make sure the internal clients access the web site via an internal IP address.

Thank you,
Mike Johnston
Microsoft Network Support

rights. Use of included script samples are subject to the

terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this

message are best directed to the newsgroup/thread from

 

[Kevin D. Goodknecht [MVP]]

In

Hi!

The DNS and the Web server are in the same Windows 2003 server. My
firewall/router has port 80 forwarded to the server. I have a dyndns
adress pointing at my routers internet ip.

I can get to the website from outside my network by typing my dyndns
adress.

My clients are pointing at my dns server for name resolution. In DNS
i have (dont know english term, i have swedish language on my server)
forward set to my isp's dns.

Hope this is enough information for you. Im not so good at english
but im trying to explain as good as i can.

In your local DNS server create a forward lookup zone with the full name of
your dydns address, i.e. myhost.dydns.org then in that zone, create a new
host leaving the name field blank and give it the IP of your webserver. You
will get a warning that (same as parent folder) is not a valid host name,
click OK create the record anyway.
run ipconfig /flushdns and try it again, it should work, and won't interfere
with other dydns.org names.

 

[mrlynx79]

In
In your local DNS server create a forward lookup zone with the full name of
your dydns address, i.e. myhost.dydns.org then in that zone, create a new
host leaving the name field blank and give it the IP of your webserver. You
will get a warning that (same as parent folder) is not a valid host name,
click OK create the record anyway.
run ipconfig /flushdns and try it again, it should work, and won't interfere
with other dydns.org names.

Thanx a lot. That did it.

// JJL