Hi

There appears to be a number of errors with your DNS:

Information
----------------------------------------------------------------------
Serial number:           19
Primary name server:     nciserver.ncimedia.com.
Primary mail server:     nciserver.ncimedia.com.
Total # of records:      6 (1 NS, 1 MX, 4 A, 0 CNAME, 0 PTR, 0 Other)

Errors
----------------------------------------------------------------------
o The name server "nciserver.ncimedia.com." is only listed in
  delegation data
    The server "nciserver.ncimedia.com." is listed as being
    authoritative for the zone according to the delegation data, but
    there is no NS record for that server in the zone data.
    Delegation data and zone data should always match.

o The name server "ns1.stratos.net." is only listed in delegation data
    The server "ns1.stratos.net." is listed as being authoritative
    for the zone according to the delegation data, but there is no NS
    record for that server in the zone data.  Delegation data and zone
    data should always match.

o Unable to check the name server "nciserver."
   Could not check the name server "nciserver.", because
    its address could not be resolved.

o The name server "nciserver.ncimedia.com." is vulnerable to spoofing
  attacks
    The cache of the server "nciserver.ncimedia.com." can be poisoned
    with false data.  This is a threat to the security of your domain.

o There are no MX records in the zone
    The zone contains no MX records.  This will cause delivery
    problems for mail sent to a user in this zone.  Every zone should
    contain at least one MX record for successful mail delivery.

o The server "ns.digex.net." did not reply
    The server "ns.digex.net." did not reply when it was queried for
    the name "147.223.117.209.in-addr.arpa.".  This indicates that the
    server is not running, or it is currently unreachable.

o There is no PTR record for the host "secure.ncimedia.com."
    There is no PTR record available for the host
    "secure.ncimedia.com." which has the IP address 209.117.223.147.


Warnings
----------------------------------------------------------------------
o "ns1.stratos.net." refused zone transfer
    The name server "ns1.stratos.net." refused a zone transfer
    request.  This server will not be used to check information about
    the zone.

o There is just one NS record in the zone
    The zone contains just one NS record.  Every zone should contain
    two or more NS records, and the NS records in the zone should
    match the delegation data for the domain.

o There is more than one PTR record for the address 209.117.223.146
    The reverse domain contains more than one PTR record for the IP
    Address 209.117.223.146

Regards
Peter

----- Original Message -----
From: Thomas J. Blaha <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: 12 October 1999 03:43
Subject: Re: [IMail Forum] help - host not found error


> Dusty,
>
> You are reading my problem correctly.  Mail coming into our system
from other
> sources on the internet are being returned with "Host not found"
errors.
> Again .. this is a sporatic problem - we believe 99%+ of all mail
comes
> through fine and it seems to be limited to virtual domains.
>
> We have had ipswitch techs examine our DNS set-up and they verify it
is
> correct, I will however provide it here again just in case.  We are
running
> microsoft DNS with the following set-up (as described by the i-mail
manuals)
> as the primary DNS with our ISP (the server is colocalized) providing
the
> backup DNS
>
> In the TCP-IP setup we have two entries in the DNS service search
order - our
> systems IP address first, the ISP's DNS is listed second.  I have read
a tech
> note on ipswitch's website stating that having numbers in here can
cause
> problems with proper delivery.  We have tried to go without them, but
then no
> mail is delivered.  Using nslookup with these settings (no IPs
specifically
> listed in the DNS Service Search Order) we get that the DNS host
127.0.0.1
> cannot be found.  This doesnt seem normal to us, but all the
documentation we
> have on Microsoft DNS state that the proper IPs for the primary and
secondary
> DNS services need to be entered here.  Ipswitches suggestion that this
feild
> be blank seems to be out of step with normal set-up.
>
> As far as specific records are concerned, we have the following
specific
> records for each virtual domain...
>
> A for domain.com
> A for www.domain.com
> MX for domain.com with the mail exchange host being the static IP host
of the
> main system
>
> As an example we have the following records for a site we know is
having
> problems...
>
> NS Record
>      Domain: ibi-opl.com
>      name server DNS name: nciserver.ncimedia.com
>
> A Record
>      Value: com
>      Hostname: ibi-opl
>      Host IP Address:  209.117.223.146
>
> SOA Record
>      nciserver.ncimedia.com
>      refresh 8 hours
>      retry 10 minutes
>      expire time 7 days
>      minimum default ttl: 2 days
>
> MX Record
>      Domain: com
>      Hostname: ibi-opl
>      Mail exchange server DNS name:  nciserver.ncimedia.com
>      Preference: 3
>
> A Record
>      Domain: ibi-opl.com
>      Host name: www
>      host IP address:  209.117.223.146
>
> All the virtuals are set up basically the same.  Each is given a
unique
> preferance number in the MX record.  The secondary DNS records are
slightly
> different as they were set up by our ISP on they system.  They have an
MX
> record for domain.com which points to a mail host of mail.domain.com.
They
> then have another MX record for mail.domain.com which points to our
mail
> host.  I beleive they also have A records for mail.domain.com.
>
> each virtual domain in the system is named mail.domain.com in the
Imail
> administrator.  Each then as an alias for just domain.com - as the set
up
> instructions dictate.
>
> Do you see anything obviously wrong here?
>
> Thanks again for the help
>
> -Tom
>
> ## Dusty Carden wrote:
>
> > If I am understanding correctly you are saying that the host
> > not found errors are from mail that was supposedly directed
> > to your virtual domains.  Meaning the sending MTA could
> > not resolve the MX.  Is this correct?
> >
> > Can you give us an example of how you have DNS set up
> > for one of these virtuals?  One problem I dealt with this morning
> > involved something similar where a sendmail box was not
> > sending to a virtual domain which had a broken DNS record.
> > (MX pointing to IP number).
> >
> > Dusty

Please visit http://www.ipswitch.com/support/mailing-lists.html 
to be removed from this list.

Reply via email to