Re: DNS stops resolving

From: Sam (sam_at_globalwebcentral.com)
Date: 06/15/04 

Date: Tue, 15 Jun 2004 14:53:19 -0400

Hi,

Actually, I'm a little confused myself. We've always used forwarders. When I
right click the server and select properties, I see no forwarders listed
under the "Forwarders" tab. I'm not sure what happened. I'll use the old,
"the network admin who no longer works here must have done something"
excuse.

As far as DNS suffixes, here's the settings:

"append parent suffixes on the primary DNS suffix" is checked along with
"append parent suffixes of the primary DNS suffix"

The DNS suffix for this connection box is empty and "Register this
connection's address in DNS" is checked.

We have no 9x clients. My concern however was with Exchange. When the DNS
server stops resolving, for some reason Exchange box, doesn't go to the
second DNS. I guess because the first DNS is not really down. So all of a
sudden, we start having Exchange problems.

Again, I'm talking about the AD integrated internal DNS servers here.

We also have linux based external DNS servers. Is it a good idea for me to
enter the IPs of the external DNS under the forwarders tab?

There seems to be two schools of thought on this one. Some suggest, I should
use the ISP's DNS Servers-- Sprint in our case -- under forwarders. Some
argue, I should use our external DNS's. What do you sugges?

Thanks,

Sam

"Kevin D. Goodknecht [MVP]" <admin@nospam.WFTX.US> wrote in message
news:uUCWU$nUEHA.1012@TK2MSFTNGP09.phx.gbl...
> In news:egz2psjUEHA.1036@TK2MSFTNGP12.phx.gbl,
> Sam <sam@globalwebcentral.com> posted a question
> Then Kevin replied below:
> > Hi,
> >
> > I noticed that time to time our AD integrated DNS servers will stop
> > resolving domains. We just had a situation where our Exchange server
> > started having outgoing mail delivery problems. When I did an
> > NSLOOKUP on the Exchange box, I realized the DNS server wasn't
> > resolving anything. I restarted the AD/DNS server and the problem was
> > resolved.
> >
> > My question is what could be causing this? We built these AD/DNS
> > machines rather recently. They seem to be running comfortably but
> > when I check the event viewer, I see a ton of warnings (event ID
> > 5504). The description reads "The DNS server encountered an invalid
> > domain name in a packet from 193.32.4.12. The packet was rejected."
> >
> > This IP address points to one of the root servers. When I check other
> > similar events, they are the same but the IP addresses could be
> > different -- different root servers.
> >
> > Any idea what could be causing this?
>
> What are the forwarders configured on the DNS servers?
>
> What names are configured on the DNS suffix search list on your clients?
>
> Do you have any Win9x clients?
>
> --
> Best regards,
> Kevin D4 Dad Goodknecht Sr. [MVP]
> Hope This Helps
> ============================
> --
> When responding to posts, please "Reply to Group" via your
> newsreader so that others may learn and benefit from your issue.
> To respond directly to me remove the nospam. from my email.
> ==========================================
> http://www.lonestaramerica.com/
> ==========================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ==========================================
> Keep a back up of your OE settings and folders with
> OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ==========================================
>
>

Relevant Pages

  • Re: Cannot expand domain node in "my network places"
    ... Connection-specific DNS Suffix. ... list of servers for this workgroup is not currently available." ...
    (microsoft.public.windows.server.general)
  • Re: Problem with sendmail when using microsoft DNS forwarders
    ... want to disable recursion on your *public* servers, ... The issue of using forwarders is basically orthogonal to this, ... network to have many private servers forwarding to one or a few other ... Can sendmail/bsd/bind/m$ dns just not play together? ...
    (comp.mail.sendmail)
  • Re: W2k3 DNS initial design
    ... I would configure Forwarders at the root DNS servers, ... Forwarders do not respond anyway, ...
    (microsoft.public.windows.server.dns)
  • Re: dumb dns question
    ... internet access from both sites as the forwarders should normally be set to ... DNS servers. ... > I have 2 SBS Servers at different locations. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD-Integrated DNS - Root Hints, Forwarders, Confused!
    ... if you want that servers ony try to resolve all names in HQ servers make ... to the two HQ DNS servers and remove the root hints from the branch DNS ... forwarders and the best configuration for our environment. ...
    (microsoft.public.windows.server.dns)