Re: Befuddled by DNS

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: SmartWare (SmartWare_at_discussions.microsoft.com)
Date: 02/08/05


Date: Mon, 7 Feb 2005 19:13:01 -0800

Thanks for the reply Jeff,
I found the problem. As it turns out, port 53 was not open on the firewall
therefore, external requests to resolve domain names other than the
registered name were unable to access the name server, ns1. Once I opened the
port and ran back through my forward zones, it all works great. dnsreport.com
was a great tool in resolving this issue, I highly reccommend it.

"Jeff Cochran" wrote:

> On Fri, 4 Feb 2005 20:47:01 -0800, SmartWare
> <SmartWare@discussions.microsoft.com> wrote:
>
> >Thanks for your response Jeff
> >ns1.mydomain.net is connected directly to the intenet, no router, it is
> >serving as the router using a ppoe connection to dls with a static public ip.
> >It is working well in this capacity. server.mydomain.net is a seperate
> >machine connected via a second nic in the ns1 system. server.mydomain.net is
> >the host of the website. NSLookup will return the proper public ip addy for
> >ns1, but only if it is done as nslookup ns1.mydomain.net. It fails if done as
> >nslookup mydomain.net.
>
> You need a blank host record in your external DNS for the mydomain.net
> that points to your external IP address. As well as for any other
> host names you wish to resolve. They have to resolve to your external
> IP for the outside systems to reach them, though you may need a second
> DNS answering only to your internal network to resolve the same name
> to two separate IP addresses.
>
> >Ns1 is routing port 80 to server and when
> >ns1.mydomain.net is typed in a remote browser, the page on server comes right
> >up. I have not done anything with NAT, could this be my problem? Any help is
> >greatly appreciated!
>
> If port 80 is translating correctly, you're working fine as far as NAT
> is concerned.
>
> Jeff
>
> >
> >"Jeff Cochran" wrote:
> >
> >> On Fri, 4 Feb 2005 19:41:03 -0800, SmartWare
> >> <SmartWare@discussions.microsoft.com> wrote:
> >>
> >> >I have two Server 2003 (Std Edition) systems setup in a lab situation. One is
> >> >ns1.mydomain.net and is registered as a domain server with internic. The
> >> >other is server.mydomain.net. Server has a basic site hosted and IIS running.
> >> >If I try to browse to the server site from within my network, I can reach the
> >> >site by typing in mydomain.net, www.mydomain.net, server.mydomain.net even
> >> >ns1.mydomain.net brings up the server web site. If I try from outside of my
> >> >network, I can only access the page by typing in ns1.mydomain.net. I have
> >> >tried every sort of host/alias record i can think of pointing to server to no
> >> >avail. I have opened the firewall and pointed http services to the server. I
> >> >also have successfully created a vpn to server which work flawlessly. The
> >> >only problem I am having is getting a page to come up from a remote browser.
> >> >I tried setting up the server as a backup dns server to no avail. It
> >> >presently is a backup domain controller. The ns1 system uses two nics with
> >> >one connected directly to my isp via a bridge/PPoE and is set to the public
> >> >ip address registered with internic and my isp. The ns1 system serves only as
> >> >an internet gateway, firewall and name server. I am sure the issue is within
> >> >DNS, but somehow I cannot get the thing to work properly from a remote
> >> >browser. any thoughts would be greatly appreciated!
> >>
> >> You have a lot of details, but few are relevant and many are
> >> confusing. Do I understand correctly that you have a server,
> >> ns1.mydomain.net connected to your internet router, then another
> >> server server.mydomain.net conneted to ns1 via a separate physical
> >> network on the second NIC? Does ns1 or server have the web site?
> >> Does a NSLookup from outside your network return a proper IP record
> >> for the www or server host in the mydomain.net domain? Is ns1 doing
> >> NAT and routing to server?
> >>
> >> Jeff
> >>
>
>



Relevant Pages

  • Re: Cant join a domain
    ... Attempting to resolve name to IP address... ... TCP port 42: NOT LISTENING ...
    (microsoft.public.windows.server.active_directory)
  • Re: Cant join a domain
    ... Attempting to resolve name to IP address... ... TCP port 42: NOT LISTENING ...
    (microsoft.public.windows.server.active_directory)
  • DCPromo and VPN fails
    ... Querying target system called: ... Attempting to resolve IP address to a name... ... TCP port 135: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Add a new DC to a new branch
    ... A Cisco router serves as DHCP server ... Querying target system called: ... Attempting to resolve IP address to a name... ... TCP port 135: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Add a new DC to a new branch
    ... Did you solved the problem about booting the server in Directory Services ... Querying target system called: ... Attempting to resolve IP address to a name... ... TCP port 135: ...
    (microsoft.public.windows.server.active_directory)