Re: Windows 2003 server, DNS forwarding to internet not working

Hi Ace and thanks for responding.

So, for the server nic, do not use the isp dns server address for
preferred dns server? I'll change that (thought Bill meant the ws to be
like that).

The firewall is a smoothwall (as I mentioned but maybe you didn't know
what that was) Smoothwal is an open source project that uses a stripped
down version of FreeBSD running on an old pc with three nics (lan,
internet, and dmz). It has a static ip of 192.168.0.1.

Separately I have a linksys router cable modem but it's actually not
connected...of course it used to be how I connected to the internet.
Maybe I need to use it as a router?

In article <#85#QDnOGHA.1032@xxxxxxxxxxxxxxxxxxxx>,
PleaseSubstituteMyActualFirstName&LastNameHere@xxxxxxxxxxx says...
In news:MPG.1e6a906072afb88d9899b3@xxxxxxxxxxxxxxxxxxxx,
network_out <none.none.none> stated, which I commented on below:
Thanks Bill. As far as I can tell I've done all of that. The ws report
the server ip as the DNS server. Forwarding for dns that the server
cannot handle is pointed to the isp dns server. I'm not sure if you
read all that I wrote, I know it's kind of long, but something in the
details of what I laid out must be wrong.

Actually I read it and you stated:
Win2003 server std, one nic.
IP 192.168.0.10 /24
default gateway 192.168.0.1 (ie firewall)
pref dns server (my isp's dns server address
this win2003 server can browse the internet fine.
dhcp service scope range 192.168.0.100 192.168.0.200

The thing that I see wrong, which you may have missed, which seems apparent
to your response to Bill, is you sated:
"> pref dns server (my isp's dns server address". That tells me that you are
mixing the DNS addresses in IP properties. What Bill stated is to ONLY use
the internal DNS, that's it. As long as the client is set to use this too,
as you stated, that's cool.

For this:
"> default gateway 192.168.0.1 (ie firewall)"
Is that your Linksys NAT router, or whatever name brand? I am assuming the
NAT/router is connected to your ISP (cable or DSL) and that performs NAT and
the internal interface is plugged into the switch all other machines are
plugged into.



.

Relevant Pages

  • RE: internet and private Dn
    ... >Subject: internet and private Dn ... I noticed that I can ping the firewall but not the isp ... Did you say that you could not ping your ISP's DNS Servers from the internal DNS Server? ... My concern is that you may simply not have communication with the ISP DNS Server. ...
    (microsoft.public.windows.server.dns)
  • Re: DNS Client Config
    ... So, if your internal client/server asks the ISP server for the Domain Controller for your internal domain, where will the ISP find the information? ... Of course the ISP DNS server can't find the record unless your ISP Server is ALSO hosting your internal domain info, or your internal domain records are published externally for all the world to see. ... >> "If this server needs to resolve names from its Internet service ...
    (microsoft.public.windows.server.dns)
  • Re: Windows 2003 server, DNS forwarding to internet not working
    ... cannot handle is pointed to the isp dns server. ... This is a direct link to the Microsoft Public ... How to Configure OEx for Internet News ...
    (microsoft.public.windows.server.networking)
  • DNS for AD in VPN/DMZ
    ... I want to configure a DNS server so users can log on to domainthrough Cisco VPN client. ... Security to me is a huge concern. ... Bill ...
    (microsoft.public.win2000.dns)
  • Re: Restrict Dynamic Updates
    ... outlined in the article "HOW TO Configure DNS for Internet Access in ... Windows Server 2003", realizing that that was not the initial intent ... internal DNS server host external public data. ... internal DNS server that hosts your internal AD infrastructure access from ...
    (microsoft.public.windows.server.dns)
Loading