Re: RDNS Timeout problems

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

Michael,

Thank you for continuing to help me focus on the problem. When I use
nslookup from inside my network, I get a prompt reply. I have not had the
opportunity to use NSLOOKUP from another network, but when I use any of
several external tooks (DNSSTUFF.com or dnsadvisor@xxxxxxxxxxxx) I am
informed that my DNS does not respond - it "times-out".

Since network solutions provides forward pointers to my domain, most of the
dns checks are clean. Only the revers inquireys (that would come from IP)
seem to have timeout problems. That brings me back to thinking the problem is
wither with Port 53, or something is slowing my server down.

Where would you check next??

"Michael Dragone" wrote:

Just to be clear, when you query your DNS servers for a PTR record in a zone
you host from off your network (from your house/hotel/another
office/whatever) with nslookup, you receive the correct reply? No timeouts?
I only ask because you mentioned in your post that it works fine when
queried from a workstation on your network.

That's a good test, but you need to make sure that PTR queries are passing
from the Internet through whatever perimeter and host protection you have to
the DNS servers themselves.

"Todd" <Todd@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:96EEC68B-1584-40C7-972E-71FA1268ED02@xxxxxxxxxxxxxxxx
Interesting you should mention DNS patch. I am on the phone with AT&T DNS
support and they are finally escalating my problem. If finally registered
with me today that if the problem was with my mail server, then another of
my
outward looking servers (the DSN secondary) should at least respond. When
I
used the AOL RDNS check tool on that IP, it failed also "serverfail".
While
talking to AT&T them mentioned a masive amount of calls today. (Has the
whole
world come to an end?)

To your other questions, when quired from any workstation in network,
nslookup responds romptly with the appropriate name/ip etc. I am using
Symantec Endpoint protection, but configured without network protection
for
the servers. I did review the firewall configuration and I am told that it
will "automatically" pass DNS requests. Just make sure, I added a hole in
the
firewall for port 53 (TCP & UDP) I have created an equivalent hole in the
Routing and Remote Access WAN port. Is there anything else I should check?
What is really frustrating is that up until a week ago, things were fine.

I'm still trying to figure it out.

"Michael Dragone" wrote:

Did you test it yourself by issuing queries from off of your own network?
Do
you have any type of firewall or perimeter gateway between the Internet
and
your SBS box?

If you're sure it's a DNS and not an Exchange issue, you should probably
try
asking in microsoft.public.windows.server.dns. Perhaps it has something
to
do with the massive multivendor DNS patch that was recently released.

"Todd" <Todd@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:33AE2A26-D11F-4A1A-9C67-C41ADB248D84@xxxxxxxxxxxxxxxx
At present, I handle them my self. I could return control to AT&T, but
if
I
am slow to respond, then I probabily have other problems I should be
addressing. I would like to find the root cause and deal with that. Any
suggestions would be appreciated.

Still searching....

"Michael Dragone" wrote:

Who handles your PTR records? Your ISP or have they delegated control
of
those zones to you and you host them yourself?

"Todd" <Todd@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:780417BF-4A6B-4FFC-99A9-0418BC284A39@xxxxxxxxxxxxxxxx
Two weeks ago (shortly after some updates from MS) I started having
mail
rejected by AOL & CS domains. (This is not the first time I have had
this
problem.) But now there is a new twist.

After talking to everyone on the network from my exchange server to
AOL's
mail server (AT&T DSL / DNS support and AOL's postmaster) I have
determined
that no one claims to be blocking port 53, but my DNS server is not
responding to RDNS requests from AOL; the request "times out"; it
appears
that my server "is not responding to the request" (You may already
know
that
unless your server responds to an RDNS request from AOL, your mail
will
not
be delivered in the AOL domain.)

Is anyone else seeing this problem? Does anyone have a suggestion as
to
how
I can get my server to respond faster? I had been fine for a year
(the
last
time I had problems with AOL's postmaster). I have made no recent
changes
to
my "public" network. I have made not recent changes to my DSN
configuration.
I am running Exchange 2003 in an SBS 2003 environment with all of
the
current
service packs and updates.

Any suggestions would be appreciated.




.

Relevant Pages

  • Random Network Disconnects
    ... network and the only way I can seem to get it back up is to restart the box. ... Testing IpConfig - pinging the Secondary WINS server... ... DNS Host Name: itdspstest01.itd.edited.edited ... Provider Version:2 ...
    (microsoft.public.windows.server.dns)
  • RE: Server 2003 Network problems since IP address change
    ... Rightclick "My Computer", properties, Computer name or network identification, ... Is there any firewall running on client or server? ... Is the Primary DNS ... of zone WSW.local. ...
    (microsoft.public.windows.server.networking)
  • Re: About DNS naming convention for Active Directory
    ... Here's what I did so far, I set up a private network consists of the ... I did an in-place upgrade of the NT4 PDC to Active Directory 2003, ... I had no DNS service at all. ... Joined the 2003 Server as a member server and that went well too. ...
    (microsoft.public.windows.server.dns)
  • Re: Single NIC configuration with cable modem/router
    ... Internal or single network adapter configuration ... Verify the Domain Name System (DNS) pointers. ... Right-click Server Local Area Connection, ...
    (microsoft.public.windows.server.sbs)
  • RE: Strange Irregular DNS/Networking Problems
    ... My network is not a complicated set up and only has one domain controller. ... problems with DNS resolving after changing DNS servers. ... I was already using the server for DHCP. ...
    (microsoft.public.windows.server.dns)