Re: DNS quit working

This is the LAN NIC. Here is the ipconfig /all:

Windows IP Configuration
Host Name . . . . . . . . . . . . : PSTSRV
Primary Dns Suffix . . . . . . . : pst.protrucklines.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : pst.protrucklines.com
protrucklines.com

Ethernet adapter WAN:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : D-Link DFE-530TX+ PCI Adapter
Physical Address. . . . . . . . . : 00-50-BA-D9-B8-12
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 66.236.19.228
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . : 66.236.19.225
DNS Servers . . . . . . . . . . . : 192.168.1.3
NetBIOS over Tcpip. . . . . . . . : Disabled
Ethernet adapter LAN:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 XT Network Connection
Physical Address. . . . . . . . . : 00-0B-DB-93-C2-57
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.1.3
Primary WINS Server . . . . . . . : 192.168.1.3

"Cris Hanna[SBS-MVP]" wrote:

is this IP your external nic or internal?
Can you post an ipconfig /all from the server?

--
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:A59323FF-6D7B-460F-AC4F-CDC95ECABD3F@xxxxxxxxxxxxxxxx
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.





.

Relevant Pages

  • Re: Group Policy and performance during logon procces from client
    ... Note that there are some problems regarding to the use of FW in the Windows XP machine, make sure that the FW are configured correctly with GPO. ... Assuming DNS AD Integrated Zone ... Do not place the ISP DNS server or any other DNS on the client or DNS Server NIC properties, ...
    (microsoft.public.windows.server.active_directory)
  • RE: In-place upgrade to AD 2003
    ... point to itself as the primary DNS server. ... During the upgrade, name the internal DNS name different from Public DNS ... When you set up a new Windows 2003 DC and transfer the FSMO roles, ...
    (microsoft.public.windows.server.migration)
  • Re: DNS cache poisoning?
    ... Windows DNS and thanks to numerous others for reporting. ... On Windows 2000 SP3 and above, the DNS server DOES protect against DNS ... BIND4 and BIND8 forwarders will not filter the cache poisoning attack to ...
    (Incidents)
  • Re: Replication issues
    ... I wanted to say Zone Transfers not Zone Forwarding. ... AD-Integrated DNS does not do zone transfers between the ... your DNS server will bypass ...
    (microsoft.public.windows.server.active_directory)
  • Re: Servers hang on boot
    ... The last DC at that site (not a DNS server). ... EventID: 0x00000457 ... (Event String could not be retrieved) ...
    (microsoft.public.windows.server.networking)