Re: Proper rules/procedures for setting up DNS/Default Gateways

From: David Efflandt (efflandt_at_xnet.com)
Date: 11/11/04 

Date: Thu, 11 Nov 2004 02:32:05 +0000 (UTC)

On Tue, 9 Nov 2004, GordL <gord@no.spam.eagleridge-home.com.spamX> wrote:
> I run a small test network behind a hardware firewall (Sonicwall SOHO3)
> where I test various software and hardware (some of it very obscure) with
> the intention of learning what I need to know before rolling anything out in
> a mission critical production environment. I recently replaced my 'server'
> hardware (due to a motherboard failure) and my Internet proxy/mail server
> (Midpoint Gateway) because Midcore Software seems to have disappeared.
>
> Here are the details of my setup. Please understand that I am not
> soliciting opinions on my choices of software or hardware. These choices
> were made within constraints that were both political and technical and were
> highly complex.
>
> Internet connection
> Toshiba DOCSIS cable router connected to the WAN side of a Sonicwall SOHO3
> NAT firewall. The SOHO3 WAN port is a DHCP client as required by my ISP
> but
> the TCP/IP settings haven't changed for years. The LAN facing port of the
> SOHO3
> is 192.168.1.2. The subnet mask is 255.255.255.252. The default gateway is
> blank
> and DNS addresses are static but the same as the WAN side.
>
> Dual ported 'server' ( I have been given a lot of advice on this.
> Unfortunately none of it seems to have worked.)
> WinXP Pro Running Kerio WinRoute as a proxy
> WAN-facing NIC is configured as IP 192.168.1.1 - SNM 255.255.255.252 -
> DG 192.168.1.2 DNS same as above (ISP's semi-static DNS servers)
> LAN facing NIC is configured as IP 192.168.10.1 - SNM 255.255.255.0 -
> DG blank and DNS set to self (192.168.10.1)

When I do DNS on myself, I use 127.0.0.1 for nameserver. But you seem to
be using both your ISP's nameservers and yourself. Are you actually
running a nameserver listening on 192.168.10.1 for yourself and the
clients below?

> Clients
> I have been given a lot of "advice" on this as well.
> IP 192.168.10.203 SNM 266.255.255.0 DG 192.168.10.1 DNS 192.168.10.1
>
> At various times I have been told to set up the DNS server address as the
> "next hop" yet others have told me to use the ISP's real world DNS servers
> even on the clients and both interfaces on the dual ported server.

You cannot just expect any router or PC to answer DNS requests on an
interface if it is not running a nameserver (PC) or proxying DNS ("some"
broadband routers).

> I have been told to
> remove and then later told to reinstall default gateways on both the server
> and client machines.

The clients appear to have correct default gateway. Whether DNS is
correct depends whether a nameserver answers on that IP.

The server itself in this case should NOT have a default gateway on its
LAN interface, which you correctly show as blank. A default gateway
should usually lead to the internet (and not to oneself).

If you still sometimes have troubles, maybe it is from using a nameserver
IP (particularly 192.168.10.1) that has no nameserver on it.

Relevant Pages

  • RE: VPN Clients Not Registering in AD DNS
    ... via VPN, the DNS records of the VPN clients are unable to be registered. ... Windows 2003 server? ... please let me know whether the clients get the IP ...
    (microsoft.public.windows.server.sbs)
  • Re: Permissions across 2 Forrest
    ... Primary DNS server on 1.x and the 18.x network along with DHCP and WINS. ... For instance ForrestA DNS is now a secondary for Forrest B and vise versa. ... WINS clients must use the same "WINS Database"* ...
    (microsoft.public.windows.server.active_directory)
  • Re: Client installation frustration.
    ... not, apparently, any DNS lookup issues on my network. ... connection's addresses in DNS" and "Use this connection's DNS suffix in DNS ... is a file and print server that we have at one of our secondary sites. ... Is there any way to cancel all current requests to install clients? ...
    (microsoft.public.sms.admin)
  • Re: problem with xp clients and windows 2003
    ... We now have the cross cable running from the room's switch ... >> policy but logs into the server. ... >> aware that this is a DNS issue but I have TRIPLE checked the DNS ... >> If I do NSlookup from the problematic clients, ...
    (microsoft.public.windows.server.networking)
  • Re: Client Connection problems
    ... pointing to your server IP 192.168.0.2 too. ... Your external nic should not have that domain.actdsltmp dns suffix. ... > DHCP and attempted to configure a static ip on the DSL ... > the server, my clients still recieve their DHCP,DNS,WINS ...
    (microsoft.public.windows.server.sbs)