Re: DNS quit working
- From: Brian <Brian@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 26 Oct 2006 11:12:02 -0700
Not before, but I did it just now. Nothing changed. FYI, here is the debug
log for a single ping of mydomain.com (where mydomain is an externally-hosted
domain, not the AD domain on the server). I got no replies to the ping.
10:53:40 1984 PACKET UDP Rcv 192.168.1.3 06ec Q [0001 D NOERROR]
(13)mydomain(3)com(0)
10:53:41 1E9C PACKET UDP Rcv 192.168.1.3 06ec Q [0001 D NOERROR]
(13)mydomain(3)com(0)
10:53:43 1984 PACKET UDP Rcv 192.168.1.3 06ec Q [0001 D NOERROR]
(13)mydomain(3)com(0)
10:53:45 17AC PACKET UDP Snd 192.168.1.3 06ec R Q [8281 DR SERVFAIL]
(13)mydomain(3)com(0)
"Cris Hanna[SBS-MVP]" wrote:
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.
- Follow-Ups:
- Re: DNS quit working
- From: Cris Hanna[SBS-MVP]
- Re: DNS quit working
- References:
- Re: DNS quit working
- From: Cris Hanna[SBS-MVP]
- Re: DNS quit working
- From: Cris Hanna[SBS-MVP]
- Re: DNS quit working
- Prev by Date: Re: One user cannot access Server Shares/connect to Exchange server
- Next by Date: Re: WSUS Sync Problem - BITS needs range protocol header - ASPNET?
- Previous by thread: Re: DNS quit working
- Next by thread: Re: DNS quit working
- Index(es):
Relevant Pages
|
Loading
