 |  |
The question is, why are you unable to connect by domain name? What
Re: DNS server position to firewall
From: Men & Mice Support
Date: Friday, February 22, 2002
Time: 2:20:59 pm
happens when you try to look up that domain name? Make sure you have
defined a name for the server, using an A record like this:
server.name. A 202.44.164.44
The question of whether the other services are inside or outside
shouldn't have any bearing on the issue at hand.
____________________________________________________________________
Chris Buxton Men & Mice
support@menandmice.com Making DNS Easy
At 8:57 AM +1100 2/23/02, Kim Kohen wrote:
>G'day all,
>
>My first post here - I hope it's not too OT.
>
>I'm using QuickDNS Pro and IPNetRouter and now have a (development) web
>server visible to the internet through port mapping. (202.44.164.44 ->
>192.168.100.1)
>
>I would now like to move our production servers (web, ftp, mail, QuickDNS
>Pro, Ad-delivery) inside the IPNR gateway.
>
>With the 192.168.100.1 server I'm able to connect by entering its (public)
>IP address in a browser but I'm unable to connect using its domain name.
>
>Is this because the DNS machine is outside the firewall? Will this be
>corrected by bringing the DNS server 'inside' to the private network? Will
>bringing the DNS server inside the gateway produce any undesirable
>consequences and/or is it advisable to have it 'inside'?
>
>I am asking similar questions of the IPNR folks as well as I believe it to
>be a multi-program issue.
>
>Cheers and thanks
>
>kim
Messages In This Thread:
Return to Digital Point Solutions' Home Page