Re: mail going out as @ns.domain, not @domain

From: Simon Waters (no email)
Date: Sun Oct 14 2001 - 18:26:38 EDT


"Greg A. Woods" wrote:
>
> > And what causes "lame"?
>
> Any delegation of a zone to a server that is not authoritative for that
> zone -- i.e. an NS record that points to a server which doesn't
> secondary the zone.

One cause could be using CNAMEs inappropriately. Which brings us
back to the mail.

A brief look suggests these may not be BIND nameservers, if
arwena is running Microsoft DNS, it could be problems with the
zone that are causing zone transfers to fail, the low expire
time would allow the data to expire. BIND typically spits an
error and carries on, Microsoft DNS is less forgiving.

If this is it, it probably shows up in your servers logs as a
lot of repeated zone transfer requests from arwena.

Arwena is definitely answering queries from cache, not from it's
zone file.

Lame is bad as a lame servers get blacklisted, reducing
redundancy. Postfix alas can't be more robust than the DNS, at
least if it can I'm sure Wietse will find out how eventually.

-- 
Are you using the Internet to best effect ? www.eighth-layer.com
Tel: +44(0)1395 232769      ICQ: 116952768
Moderated discussion of teleworking at news:uk.business.telework
-
To unsubscribe, send mail to  with content
(not subject): unsubscribe postfix-users







Hosted Email Solutions

Invaluement Anti-Spam DNSBLs



Powered By FreeBSD   Powered By FreeBSD