Re: DNS quit working

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Have you tried re-running the CEICW??

--
CRIS HANNA [SBS-MVP]
----------------------------------------
Please only communicate in the newsgroup. Please do not contact me directly.
----------------------------------------
Sent via Windows Mail on Windows Vista, Business Edition RC 2

"Brian" <Brian@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:02B6B82A-FC58-460A-B3FE-FD5BCA7C2469@xxxxxxxxxxxxxxxx
Also, through dnsmgmt, I ran the automated query test. It works internally
but not recursively to the forwarder. However, DNS works correctly for the
workstations IF I enter the forwarder as the primary DNS.

My (very temporary) solution for the clients is to set the forwarder as the
primary DNS & the SBS server as the secondary. I know this is highly
un-recommended, but it got them up & running temporarily at least.

"Cris Hanna[SBS-MVP]" wrote:

what is the external connected to?
Another router, or directly to Internet (has a public IP assigned to nic)

--
CRIS HANNA [SBS-MVP]
----------------------------------------
Please only communicate in the newsgroup. Please do not contact me
directly.
----------------------------------------
Sent via Windows Mail on Windows Vista, Business Edition RC 2

"Brian" <Brian@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9D429CCA-6FC8-43C3-A33A-11B2B4C5699D@xxxxxxxxxxxxxxxx
> SBS 2003 server. Has been in place for two years. It is correctly set > up
> with
> two NIC's: one on the LAN, one on the WAN. Both have its LAN IP address > as
> DNS server. Forwarder is ISP's DNS server.
>
> Last week, it evidently quit forwarding requests. Not knowing this, I
> called
> the ISP and got a set of alternate DNS servers.
>
> It worked correctly for several days. Now, however, it provides only
> non-authoritative replies (presumably for those domains already in the
> cache).
>
> If I hard-code the ISP's DNS server at the clients, DNS works. If I
> hard-code the ISP's DNS servers on the server's NIC properties, I can > ping
> domains but nslookup still fails, even at the server.
>
> The only related events are 4004, 4015, 4016, and 113 with an error of
> 1168
> (The DNS server could not signal the service "NAT".
>
> I have restarted DNS client & server, rebooted the server, removed &
> re-entered the Forwarders, all to no avail.
>



.



Relevant Pages

  • Re: SBS Premium Edition Exchange Issues
    ... Cris Hanna [SBS-MVP] ... Send via Windows Mail on Vista Ultimate connected to SBS 2003 R2 ... > dns server 64.238.96.12 DNS Server should be 10.0.0.1 ...
    (microsoft.public.windows.server.sbs)
  • Re: DNS quit working
    ... I got no replies to the ping. ... Sent via Windows Mail on Windows Vista, ... workstations IF I enter the forwarder as the primary DNS. ... Forwarder is ISP's DNS server. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Premium Edition Exchange Issues
    ... tried to rerun Ceicw and system becomes non-responsive ... dns server 64.238.96.12 DNS Server should be 10.0.0.1 ... Send via Windows Mail on Vista Ultimate connected to SBS 2003 R2 ... Ip routing enabled-yes ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Premium Edition Exchange Issues
    ... default gatway 192.168.1.1 ... dns server 64.238.96.12 DNS Server should be 10.0.0.1 ... Send via Windows Mail on Vista Ultimate connected to SBS 2003 R2 ... Ip routing enabled-yes ...
    (microsoft.public.windows.server.sbs)
  • Re: DNS quit working
    ... Can you post an ipconfig /all from the server? ... Sent via Windows Mail on Windows Vista, ... > workstations IF I enter the forwarder as the primary DNS. ... Forwarder is ISP's DNS server. ...
    (microsoft.public.windows.server.sbs)