Re: smtp could not connect to any dns server: exchange smtp will n

From: tony adduci (tonyadduci_at_discussions.microsoft.com)
Date: 08/30/04

  • Next message: Ryan: "OWA connection problem" 
    Date: Mon, 30 Aug 2004 12:59:01 -0700

    Hello,
    I am able to reload the zone for the secondary with no problem. I am able to
    ping by name with no problem.

    I see no other errors other than the 2013, and the 2012 on the "primary"
    server in my first domain. Ironically I do not see the errors as much on the
    "secondary" server in the second domain.

    I do seem to have more problems sending mail from domain1 to domain2 and
    domain1 logs more 2013 and 2012 errors in the event viewer.

    If both servers point to themselves and they each have a secondary zone in
    their respective dns manager then why can't they resolve the
    mail.companyname.com correctly and passmail?

    >From either mail server I can telnet to the smtp port 25 and send email with
    no issue.

    I have to do a ipconfig /flushdns, ipconfig /registerdns and then start/stop
    the smtp connector and force a mail sending process in order to get the mail
    to flow... Do these troubleshooting steps help describe what error I am
    having?

    Also, in my research I have come across q-article: 330070 but it wants me to
    edit the iis metabase... Could my udp/tcp dns requests be at fault?

    Help...
    Thanks in advance.

    "Omer maydan" wrote:

    > first look at these posts as they came from eventid site:
    >
    > Adrian Grigorof
    > From newsgroup posts:
    >
    > - "It means that your server has not performed a zone transfer from whomever
    > the master DNS server is for <zone name> in the allocatted time, so the zone
    > file you have has expired and your DNS server will no longer answer queries
    > for that zone. Investigate the DNS server holding the master zone"
    >
    > - "Looks like a problem on the master. Are any of the other slaves (if any)
    > having any problems with zone transfers of the zone? On your slave, try
    > doing a non-recursive, TCP AXFR query for the domain from the master. The
    > error you get back should help you troubleshoot the problem. If you're
    > not getting any kind of error back, then there is something wrong with your
    > nameserver."
    >
    > - "You should probably be looking for a problem like the secondary being
    > unable to connect to the primary on TCP/IP port 53, or the primary being
    > configured to deny zone transfer requests from the secondaries IP address.
    > On the secondary server start by using ping to establish that it can reach
    > the primary at all. Then, also on the secondary, use NSLOOKUP. Use the
    > SERVER command to point it to the primary. Then try to manually transfer a
    > copy of the zone using the ls -d command. This should tell you if the
    > secondary cannot reach the primary on port 53 or if there is a problem in
    > the transfer."
    >
    > also, if you have windows 2003 Dns, you can use other methods to ecommplish
    > name resolution between the domains without replicating information. you can
    > setup conditional forwarding to the other server, and by that saving some
    > hassale.
    >
    > --
    >
    > Omer Maydan
    > MCSE, Security+
    >
    > "tony adduci" <tonyadduci@discussions.microsoft.com> wrote in message
    > news:080C5794-C096-49B5-BCCD-8B2C00B920D2@microsoft.com...
    > > Hello,
    > > I have two exchange servers in two windows domains on one internal subnet
    > > and they are haivng a hard time periodically delivering mail between the
    > two
    > > of them. I also get that error: SMTP could not connect to any DNS server"
    > in
    > > my event viewer on one of my domains.
    > >
    > > Until I added secondary zones I wasn't able to pass mail at all between
    > the
    > > two servers. Each server points to itself only for internal/external dns
    > > resolution. No forwarders exist or no dns servers in the smtp properties
    > of
    > > the connector.
    > > I added secondary zones to each server one for eachothers domain and that
    > > doesn't seem to help. I also see timeout errors relating to DNS in my
    > event
    > > viewer...
    > >
    > > That error is: 6527 zone companyname.com expired before it could obtain a
    > > successful zone transfer or update from a master server....
    > >
    > > Any ideas?
    >
    >
    >

  • Next message: Ryan: "OWA connection problem"

    Relevant Pages

    • Re: Replication between parent child domains
      ... install dns before i run the dcpromo on the melbourne server. ... DNS server will forward any query it can't answer, Checks zone ...
      (microsoft.public.windows.server.active_directory)
    • Re: Replication between parent child domains
      ... DNS server will forward any query it can't answer, Checks zone ... DNS Servers) all queries will go to tld DNS server (including Internet ... Stub zones: Stub zones contain a read-only copy with specific records ...
      (microsoft.public.windows.server.active_directory)
    • backup DNS on non-DC? AD Integrated DNS (Windows 2003)
      ... You can allow zone transfers of an AD zone to any DNS ... well, so when a change is made, the master server will ...
      (microsoft.public.windows.server.dns)
    • backup DNS on non-DC? AD Integrated DNS (Windows 2003)
      ... You can allow zone transfers of an AD zone to any DNS ... well, so when a change is made, the master server will ...
      (microsoft.public.windows.server.dns)
    • Re: Adding Second DNS Server to Domain
      ... DNS server was down. ... Otherwise if you manually create an identical zone on another DC/DNS ... If the second machine is not a DC, then you have to go to the first DNS ... This is what I already tried, if I enable Zone Transfers for IP ...
      (microsoft.public.windows.server.dns)