postfix and dns lookup

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
32 messages Options
12
Reply | Threaded
Open this post in threaded view
|

postfix and dns lookup

Matteo Cazzador-2
Hello , i've a question , i want do configure postfix to use external
dns like (8.8.8.8) to resolve every domain (lookup for examples)
for incoming mail and outgoing mail. I don't want to use local dns on
postfix server is it possible?
Is it possible to use :

smtp_host_lookup = ?


Thank's a lot

--
Rispetta l'ambiente: se non ti è necessario, non stampare questa mail.

Le informazioni contenute in questa e-mail e nei files eventualmente allegati sono destinate unicamente ai destinatari della stessa e sono da considerarsi strettamente riservate. E' proibito copiare, salvare, utilizzare,  inoltrare a terzi e diffondere il contenuto della presente senza il preventivo consenso, ai sensi dell'articolo 616 c.p. e della Legge n. 196/2003. Se avete ricevuto questo messaggio per errore siete pregati di comunicarlo immediatamente all'indirizzo mittente, nonché di cancellarne il contenuto senza procedere ad ulteriore o differente trattamento.


******************************************
Ing. Matteo Cazzador
NetLite snc di Cazzador Gagliardi
Corso Vittorio Emanuele II, 188 37069
Villafranca di Verona VR
Tel 0454856656
Fax 0454856655
Email: [hidden email]
Web: http://www.netlite.it
******************************************

Reply | Threaded
Open this post in threaded view
|

Re: postfix and dns lookup

Noel Jones-2
On 2/4/2011 8:39 AM, Matteo Cazzador wrote:

> Hello , i've a question , i want do configure postfix to use
> external dns like (8.8.8.8) to resolve every domain (lookup
> for examples)
> for incoming mail and outgoing mail. I don't want to use local
> dns on postfix server is it possible?
> Is it possible to use :
>
> smtp_host_lookup = ?
>
>
> Thank's a lot
>

If you don't want to use local DNS, then don't set any up.
Postfix uses whatever the system is configured to use in
/etc/resolv.conf.

There is no separate postfix config for setting a DNS resolver.



   -- Noel Jones
Reply | Threaded
Open this post in threaded view
|

Re: postfix and dns lookup

Noel Jones-2
On 2/4/2011 8:42 AM, Noel Jones wrote:

> On 2/4/2011 8:39 AM, Matteo Cazzador wrote:
>> Hello , i've a question , i want do configure postfix to use
>> external dns like (8.8.8.8) to resolve every domain (lookup
>> for examples)
>> for incoming mail and outgoing mail. I don't want to use local
>> dns on postfix server is it possible?
>> Is it possible to use :
>>
>> smtp_host_lookup = ?
>>
>>
>> Thank's a lot
>>
>
> If you don't want to use local DNS, then don't set any up.
> Postfix uses whatever the system is configured to use in
> /etc/resolv.conf.
>
> There is no separate postfix config for setting a DNS resolver.
>
>

That said, it's really a mistake to not use any resolver at
all on anything bigger than a toy server.

At least set up a local caching resolver with 8.8.8.8 as the
forwarder.



    -- Noel Jones
Reply | Threaded
Open this post in threaded view
|

Re: postfix and dns lookup

Matteo Cazzador-2
Ok thank's in alternative is it possible use of

disable_dns_lookups=yes

to increase performance?
My postfix server is a virtual mail server
With mysql backend


Il 04/02/2011 15:44, Noel Jones ha scritto:

> On 2/4/2011 8:42 AM, Noel Jones wrote:
>> On 2/4/2011 8:39 AM, Matteo Cazzador wrote:
>>> Hello , i've a question , i want do configure postfix to use
>>> external dns like (8.8.8.8) to resolve every domain (lookup
>>> for examples)
>>> for incoming mail and outgoing mail. I don't want to use local
>>> dns on postfix server is it possible?
>>> Is it possible to use :
>>>
>>> smtp_host_lookup = ?
>>>
>>>
>>> Thank's a lot
>>>
>>
>> If you don't want to use local DNS, then don't set any up.
>> Postfix uses whatever the system is configured to use in
>> /etc/resolv.conf.
>>
>> There is no separate postfix config for setting a DNS resolver.
>>
>>
>
> That said, it's really a mistake to not use any resolver at all on
> anything bigger than a toy server.
>
> At least set up a local caching resolver with 8.8.8.8 as the forwarder.
>
>
>
>    -- Noel Jones

--
Rispetta l'ambiente: se non ti è necessario, non stampare questa mail.

Le informazioni contenute in questa e-mail e nei files eventualmente allegati sono destinate unicamente ai destinatari della stessa e sono da considerarsi strettamente riservate. E' proibito copiare, salvare, utilizzare,  inoltrare a terzi e diffondere il contenuto della presente senza il preventivo consenso, ai sensi dell'articolo 616 c.p. e della Legge n. 196/2003. Se avete ricevuto questo messaggio per errore siete pregati di comunicarlo immediatamente all'indirizzo mittente, nonché di cancellarne il contenuto senza procedere ad ulteriore o differente trattamento.


******************************************
Ing. Matteo Cazzador
NetLite snc di Cazzador Gagliardi
Corso Vittorio Emanuele II, 188 37069
Villafranca di Verona VR
Tel 0454856656
Fax 0454856655
Email: [hidden email]
Web: http://www.netlite.it
******************************************

Reply | Threaded
Open this post in threaded view
|

Re: postfix and dns lookup

Ralf Hildebrandt
* Matteo Cazzador <[hidden email]>:
> Ok thank's in alternative is it possible use of
>
> disable_dns_lookups=yes
>
> to increase performance?

Uhm, your server probably won't be able to send out mail out after
that change, but at least it will do this quickly.

> My postfix server is a virtual mail server
> With mysql backend

What exactly IS your performance problem? Sending? Receiving? Local
delivery? How are you measuring?

--
Ralf Hildebrandt
  Geschäftsbereich IT | Abteilung Netzwerk
  Charité - Universitätsmedizin Berlin
  Campus Benjamin Franklin
  Hindenburgdamm 30 | D-12203 Berlin
  Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
  [hidden email] | http://www.charite.de
           
Reply | Threaded
Open this post in threaded view
|

Re: postfix and dns lookup

Matteo Cazzador-2
Than'k a lot and excuse me if i'm not so clear:

my local dns server , that is postfix server to, is used to filter
navigation of client (by domain black list)
so my local dns is under pressure and often mail give me error resolving
dns while sending mail to external.
I need to limitate this postfix error.
An example;

  Out: 220 mydomain ESMTP Ermes
  In:  EHLO ciccio
  Out: 250-mydomain
  Out: 250-PIPELINING
  Out: 250-SIZE 18000000
  Out: 250-VRFY
  Out: 250-ETRN
  Out: 250-AUTH LOGIN PLAIN
  Out: 250-AUTH=LOGIN PLAIN
  Out: 250-ENHANCEDSTATUSCODES
  Out: 250-8BITMIME
  Out: 250 DSN
  In:  AUTH LOGIN
  Out: 334 VXNlcm5hbWU6
  In:  aW5mb0BicnVub3NybC5uZXQ=
  Out: 334 UGFzc3dvcmQ6
  In:  YXM4ZWUyNDU=
  Out: 235 2.7.0 Authentication successful
  In:  MAIL FROM:<[hidden email]>
  Out: 250 2.1.0 Ok
  In:  RCPT TO:<daniela.mair@externaldomain>
  Out: 451 4.3.0<daniela.mair@externaldomain>: Temporary lookup failure
  In:  RSET
  Out: 250 2.0.0 Ok

thank's a lot



Il 04/02/2011 15:55, Ralf Hildebrandt ha scritto:

> * Matteo Cazzador<[hidden email]>:
>> Ok thank's in alternative is it possible use of
>>
>> disable_dns_lookups=yes
>>
>> to increase performance?
> Uhm, your server probably won't be able to send out mail out after
> that change, but at least it will do this quickly.
>
>> My postfix server is a virtual mail server
>> With mysql backend
> What exactly IS your performance problem? Sending? Receiving? Local
> delivery? How are you measuring?
>

--
Rispetta l'ambiente: se non ti è necessario, non stampare questa mail.

Le informazioni contenute in questa e-mail e nei files eventualmente allegati sono destinate unicamente ai destinatari della stessa e sono da considerarsi strettamente riservate. E' proibito copiare, salvare, utilizzare,  inoltrare a terzi e diffondere il contenuto della presente senza il preventivo consenso, ai sensi dell'articolo 616 c.p. e della Legge n. 196/2003. Se avete ricevuto questo messaggio per errore siete pregati di comunicarlo immediatamente all'indirizzo mittente, nonché di cancellarne il contenuto senza procedere ad ulteriore o differente trattamento.


******************************************
Ing. Matteo Cazzador
NetLite snc di Cazzador Gagliardi
Corso Vittorio Emanuele II, 188 37069
Villafranca di Verona VR
Tel 0454856656
Fax 0454856655
Email: [hidden email]
Web: http://www.netlite.it
******************************************

Reply | Threaded
Open this post in threaded view
|

Re: postfix and dns lookup

Ralf Hildebrandt
* Matteo Cazzador <[hidden email]>:

> Than'k a lot and excuse me if i'm not so clear:
>
> my local dns server , that is postfix server to, is used to filter
> navigation of client (by domain black list)
> so my local dns is under pressure and often mail give me error
> resolving dns while sending mail to external.
> I need to limitate this postfix error.
> An example;
>
>  Out: 220 mydomain ESMTP Ermes
>  In:  EHLO ciccio
>  Out: 250-mydomain
>  Out: 250-PIPELINING
>  Out: 250-SIZE 18000000
>  Out: 250-VRFY
>  Out: 250-ETRN
>  Out: 250-AUTH LOGIN PLAIN
>  Out: 250-AUTH=LOGIN PLAIN
>  Out: 250-ENHANCEDSTATUSCODES
>  Out: 250-8BITMIME
>  Out: 250 DSN
>  In:  AUTH LOGIN
>  Out: 334 VXNlcm5hbWU6
>  In:  aW5mb0BicnVub3NybC5uZXQ=
>  Out: 334 UGFzc3dvcmQ6
>  In:  YXM4ZWUyNDU=
>  Out: 235 2.7.0 Authentication successful
>  In:  MAIL FROM:<[hidden email]>
>  Out: 250 2.1.0 Ok
>  In:  RCPT TO:<daniela.mair@externaldomain>
>  Out: 451 4.3.0<daniela.mair@externaldomain>: Temporary lookup failure
>  In:  RSET
>  Out: 250 2.0.0 Ok

Please show the logs for exactly that error. Because the logs show
WHAT failed (DNS, or mysql lookups)

--
Ralf Hildebrandt
  Geschäftsbereich IT | Abteilung Netzwerk
  Charité - Universitätsmedizin Berlin
  Campus Benjamin Franklin
  Hindenburgdamm 30 | D-12203 Berlin
  Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
  [hidden email] | http://www.charite.de
           
Reply | Threaded
Open this post in threaded view
|

Re: postfix and dns lookup

Matteo Cazzador-2
hello here's my error log
192.168.0.10 = internal client ip
now i've seen this strange mysql error maybe this is the real problem

Feb  4 00:00:58 localhost postfix/trivial-rewrite[2579]: warning: mysql
query failed: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and
(utf8_general_ci,COERCIBLE) for operation '='
Feb  4 00:00:58 localhost postfix/trivial-rewrite[2579]: warning:
transport_maps lookup failure
Feb  4 00:00:59 localhost postfix/trivial-rewrite[2579]: warning:
transport_maps lookup failure
Feb  4 00:00:59 localhost postfix/smtpd[2577]: NOQUEUE: reject: RCPT
from 189-93-193-156.3g.claro.net.br[189.93.193.156]: 451 4.3.0
<x@mydomain>: Temporary lookup failure; from=<?ngelL?[hidden email]>
to=<x@mydomain> proto=SMTP helo=<189-93-193-156.3g.claro.net.br>
Feb  4 00:01:00 localhost postfix/trivial-rewrite[2579]: warning:
transport_maps lookup failure


Feb  3 12:53:54 localhost postfix/trivial-rewrite[29555]: warning: mysql
query failed: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and
(utf8_general_ci,COERCIBLE) for operation '='
Feb  3 12:53:54 localhost postfix/trivial-rewrite[29555]: warning:
transport_maps lookup failure
Feb  3 12:53:54 localhost postfix/trivial-rewrite[29555]: warning:
transport_maps lookup failure
Feb  3 12:54:22 localhost postfix/trivial-rewrite[29555]: warning:
transport_maps lookup failure

Feb  3 12:54:22 localhost postfix/smtpd[29552]: NOQUEUE: reject: RCPT
from unknown[192.168.0.10]: 451 4.3.0 <[hidden email]>: Temporary
lookup failure; from=<[hidden email]> to=<[hidden email]>
proto=ESMTP helo=<ciccio>
Feb  3 12:54:55 localhost postfix/smtpd[29597]: disconnect from
unknown[192.168.0.10]
Feb  3 12:54:56 localhost postfix/smtpd[29618]: connect from
localhost[127.0.0.1]
Feb  3 12:54:56 localhost postfix/smtpd[29618]: 900EC47B3C:
client=localhost[127.0.0.1]
Feb  3 12:54:56 localhost postfix/cleanup[29561]: 900EC47B3C:
message-id=<1848812.827.1296734124609.JavaMail.SYSTEM@ciccio>
Feb  3 12:54:56 localhost postfix/smtp[29604]: 5779F47B3B:
to=<[hidden email]>, relay=127.0.0.1[127.0.0.1]:10024, delay=1.3,
delays=0.14/0/0/1.2, dsn=2.0.0, status=sent (250 2.0.0 Ok, id=28949-16,
from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as 900EC47B3C)
Feb  3 12:54:56 localhost postfix/qmgr[4415]: 5779F47B3B: removed
Feb  3 12:54:57 localhost postfix/smtp[29620]: 900EC47B3C: enabling PIX
workarounds: disable_esmtp delay_dotcrlf for
mail.external.com[external_ip]:25
Feb  3 12:55:00 localhost postfix/smtp[29620]: 900EC47B3C:
to=<[hidden email]>, relay=mail.external.com[external_ip]:25,
delay=3.6, delays=0.1/0/0.89/2.6, dsn=2.0.0, status=sent (250 2.0.0
p1NNCbuA010097 Message accepted for delivery)
Feb  3 12:55:00 localhost postfix/qmgr[4415]: 900EC47B3C: removed


Il 04/02/2011 16:08, Ralf Hildebrandt ha scritto:

> * Matteo Cazzador<[hidden email]>:
>> Than'k a lot and excuse me if i'm not so clear:
>>
>> my local dns server , that is postfix server to, is used to filter
>> navigation of client (by domain black list)
>> so my local dns is under pressure and often mail give me error
>> resolving dns while sending mail to external.
>> I need to limitate this postfix error.
>> An example;
>>
>>   Out: 220 mydomain ESMTP Ermes
>>   In:  EHLO ciccio
>>   Out: 250-mydomain
>>   Out: 250-PIPELINING
>>   Out: 250-SIZE 18000000
>>   Out: 250-VRFY
>>   Out: 250-ETRN
>>   Out: 250-AUTH LOGIN PLAIN
>>   Out: 250-AUTH=LOGIN PLAIN
>>   Out: 250-ENHANCEDSTATUSCODES
>>   Out: 250-8BITMIME
>>   Out: 250 DSN
>>   In:  AUTH LOGIN
>>   Out: 334 VXNlcm5hbWU6
>>   In:  aW5mb0BicnVub3NybC5uZXQ=
>>   Out: 334 UGFzc3dvcmQ6
>>   In:  YXM4ZWUyNDU=
>>   Out: 235 2.7.0 Authentication successful
>>   In:  MAIL FROM:<[hidden email]>
>>   Out: 250 2.1.0 Ok
>>   In:  RCPT TO:<daniela.mair@externaldomain>
>>   Out: 451 4.3.0<daniela.mair@externaldomain>: Temporary lookup failure
>>   In:  RSET
>>   Out: 250 2.0.0 Ok
> Please show the logs for exactly that error. Because the logs show
> WHAT failed (DNS, or mysql lookups)
>

--
Rispetta l'ambiente: se non ti è necessario, non stampare questa mail.

Le informazioni contenute in questa e-mail e nei files eventualmente allegati sono destinate unicamente ai destinatari della stessa e sono da considerarsi strettamente riservate. E' proibito copiare, salvare, utilizzare,  inoltrare a terzi e diffondere il contenuto della presente senza il preventivo consenso, ai sensi dell'articolo 616 c.p. e della Legge n. 196/2003. Se avete ricevuto questo messaggio per errore siete pregati di comunicarlo immediatamente all'indirizzo mittente, nonché di cancellarne il contenuto senza procedere ad ulteriore o differente trattamento.


******************************************
Ing. Matteo Cazzador
NetLite snc di Cazzador Gagliardi
Corso Vittorio Emanuele II, 188 37069
Villafranca di Verona VR
Tel 0454856656
Fax 0454856655
Email: [hidden email]
Web: http://www.netlite.it
******************************************

Reply | Threaded
Open this post in threaded view
|

Re: postfix and dns lookup

Ralf Hildebrandt
* Matteo Cazzador <[hidden email]>:
> hello here's my error log
> 192.168.0.10 = internal client ip
> now i've seen this strange mysql error maybe this is the real problem

Yes!

> Feb  4 00:00:58 localhost postfix/trivial-rewrite[2579]: warning: mysql query failed: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for
> operation '='
> Feb  4 00:00:58 localhost postfix/trivial-rewrite[2579]: warning: transport_maps lookup failure
> Feb  4 00:00:59 localhost postfix/trivial-rewrite[2579]: warning: transport_maps lookup failure


--
Ralf Hildebrandt
  Geschäftsbereich IT | Abteilung Netzwerk
  Charité - Universitätsmedizin Berlin
  Campus Benjamin Franklin
  Hindenburgdamm 30 | D-12203 Berlin
  Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
  [hidden email] | http://www.charite.de
           
Reply | Threaded
Open this post in threaded view
|

Re: postfix and dns lookup

lst_hoe02
In reply to this post by Matteo Cazzador-2
Zitat von Matteo Cazzador <[hidden email]>:

> Than'k a lot and excuse me if i'm not so clear:
>
> my local dns server , that is postfix server to, is used to filter  
> navigation of client (by domain black list)
> so my local dns is under pressure and often mail give me error  
> resolving dns while sending mail to external.
> I need to limitate this postfix error.

So you have a local caching-resolver on the Postfix box?

If so it should not fail because of traffic as long as your system  
resources are not exhausted. If your system resources are exhausted  
using a different resolver does not help.

You might playing tricks with a local caching-resolver used by  
internal clients and pointing /etc/resolv.conf to some second  
(external) resolver but i doubt this is your problem at all.

Regards

Andreas



smime.p7s (8K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: postfix and dns lookup

Reindl Harald-2

Am 04.02.2011 16:32, schrieb [hidden email]:
> So you have a local caching-resolver on the Postfix box?
>
> If so it should not fail because of traffic as long as your system resources are not exhausted.
> If your system resources are exhausted using a different resolver does not help.
>
> You might playing tricks with a local caching-resolver used by internal clients and
> pointing /etc/resolv.conf to
> some second (external) resolver but i doubt this is your problem at all

Even if dns-load would be the problem (which is not, it is mysql seen some posts before)
the real problem should be searched because nohting is better for a dns.cache as
a mailserver to get the cache filled

But i never seen any machine where dns-lookups where a load problem




signature.asc (269 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: postfix and dns lookup

Matteo Cazzador-2
Sure, thank's a lot everybody, i think the problem is related to:

warning: mysql query failed: Illegal mix of collations
(latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE)  operation '='
that cause

warning: transport_maps lookup failure


Someone suggest to forse use latin 1  in sql

like  =CONVERT('%s' USING latin1) for mysql transport table

but  is it correct?

In reality i don't use mysql-transport table can elide it.


Il 04/02/2011 16:39, Reindl Harald ha scritto:

> Am 04.02.2011 16:32, schrieb [hidden email]:
>> So you have a local caching-resolver on the Postfix box?
>>
>> If so it should not fail because of traffic as long as your system resources are not exhausted.
>> If your system resources are exhausted using a different resolver does not help.
>>
>> You might playing tricks with a local caching-resolver used by internal clients and
>> pointing /etc/resolv.conf to
>> some second (external) resolver but i doubt this is your problem at all
> Even if dns-load would be the problem (which is not, it is mysql seen some posts before)
> the real problem should be searched because nohting is better for a dns.cache as
> a mailserver to get the cache filled
>
> But i never seen any machine where dns-lookups where a load problem
>
>
>

--
Rispetta l'ambiente: se non ti è necessario, non stampare questa mail.

Le informazioni contenute in questa e-mail e nei files eventualmente allegati sono destinate unicamente ai destinatari della stessa e sono da considerarsi strettamente riservate. E' proibito copiare, salvare, utilizzare,  inoltrare a terzi e diffondere il contenuto della presente senza il preventivo consenso, ai sensi dell'articolo 616 c.p. e della Legge n. 196/2003. Se avete ricevuto questo messaggio per errore siete pregati di comunicarlo immediatamente all'indirizzo mittente, nonché di cancellarne il contenuto senza procedere ad ulteriore o differente trattamento.


******************************************
Ing. Matteo Cazzador
NetLite snc di Cazzador Gagliardi
Corso Vittorio Emanuele II, 188 37069
Villafranca di Verona VR
Tel 0454856656
Fax 0454856655
Email: [hidden email]
Web: http://www.netlite.it
******************************************

Reply | Threaded
Open this post in threaded view
|

Re: postfix and dns lookup

Brian Evans - Postfix List
On 2/4/2011 10:50 AM, Matteo Cazzador wrote:

> Sure, thank's a lot everybody, i think the problem is related to:
>
> warning: mysql query failed: Illegal mix of collations
> (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE)
> operation '='
> that cause
>
> warning: transport_maps lookup failure
>
>
> Someone suggest to forse use latin 1  in sql
>
> like  =CONVERT('%s' USING latin1) for mysql transport table
>
> but  is it correct?
>
> In reality i don't use mysql-transport table can elide it.

http://dev.mysql.com/doc/refman/5.1/en/charset-literal.html

Postfix allows sql/ldap queries in transport_maps, but it is discouraged
for this very reason.
If you have a small list of transports, use a static hash/dbm/cdb lookup.
You can update these using a script if they are dynamic.
Don't postmap a hash transport table if it is quite long as overwrites
the old one in-line. Postmap to a temporary name or use cdb instead.

>
>
> Il 04/02/2011 16:39, Reindl Harald ha scritto:
>> Am 04.02.2011 16:32, schrieb [hidden email]:
>>> So you have a local caching-resolver on the Postfix box?
>>>
>>> If so it should not fail because of traffic as long as your system
>>> resources are not exhausted.
>>> If your system resources are exhausted using a different resolver
>>> does not help.
>>>
>>> You might playing tricks with a local caching-resolver used by
>>> internal clients and
>>> pointing /etc/resolv.conf to
>>> some second (external) resolver but i doubt this is your problem at all
>> Even if dns-load would be the problem (which is not, it is mysql seen
>> some posts before)
>> the real problem should be searched because nohting is better for a
>> dns.cache as
>> a mailserver to get the cache filled
>>
>> But i never seen any machine where dns-lookups where a load problem
>>
>>
>>
>

Reply | Threaded
Open this post in threaded view
|

Re: postfix and dns lookup

Benny Pedersen
In reply to this post by Noel Jones-2
On Fri, 04 Feb 2011 08:44:39 -0600, Noel Jones <[hidden email]>
wrote:

> At least set up a local caching resolver with 8.8.8.8 as the
> forwarder.

in case of bind this is bad to use any forwarder since it disables hint
zone, forwarders is more usefull pr zone, so keeep forwards out of options
containter in named.conf
Reply | Threaded
Open this post in threaded view
|

Re: postfix and dns lookup

Reindl Harald-2

Am 05.02.2011 12:37, schrieb Benny Pedersen:
> On Fri, 04 Feb 2011 08:44:39 -0600, Noel Jones <[hidden email]>
> wrote:
>
>> At least set up a local caching resolver with 8.8.8.8 as the
>> forwarder.
>
> in case of bind this is bad to use any forwarder since it disables hint
> zone, forwarders is more usefull pr zone, so keeep forwards out of options
> containter in named.conf

And where is the problem?
Nobody needs the "hint zone" in his LAN because some reasons:

* A big external forwarder has many requests in his cache
* This cached requests are much faster and fewer as full recursion
* It reduces the load of the root-Servers



signature.asc (269 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: postfix and dns lookup

Matteo Cazzador-2
hello, the nature of the problem that causes temporary lookup failure is
not dns
like i thinking of, the problem is caused by mysql backend. Some
spam has strange charset that caused mysql error, see previous mail
about it.
Thank's a lot.

Il 05/02/2011 13:55, Reindl Harald ha scritto:

> Am 05.02.2011 12:37, schrieb Benny Pedersen:
>> On Fri, 04 Feb 2011 08:44:39 -0600, Noel Jones<[hidden email]>
>> wrote:
>>
>>> At least set up a local caching resolver with 8.8.8.8 as the
>>> forwarder.
>> in case of bind this is bad to use any forwarder since it disables hint
>> zone, forwarders is more usefull pr zone, so keeep forwards out of options
>> containter in named.conf
> And where is the problem?
> Nobody needs the "hint zone" in his LAN because some reasons:
>
> * A big external forwarder has many requests in his cache
> * This cached requests are much faster and fewer as full recursion
> * It reduces the load of the root-Servers
>
>

--
Rispetta l'ambiente: se non ti è necessario, non stampare questa mail.
******************************************
Ing. Matteo Cazzador
NetLite Snc
di Gagliardi A. Cazzador M.
C.so Vittorio Emanuele II, 188
37069 Villafranca di Verona (VR)
Tel 045 4856656
Fax 045 4856655
C.F. E P.IVA 03782800233
Email: [hidden email]
Web: http://www.netlite.it
******************************************

Reply | Threaded
Open this post in threaded view
|

Re: postfix and dns lookup

Charles Marcus
In reply to this post by Reindl Harald-2
On 2/5/2011 7:55 AM, Reindl Harald wrote:
> Am 05.02.2011 12:37, schrieb Benny Pedersen:
>> On Fri, 04 Feb 2011 08:44:39 -0600, Noel Jones<[hidden email]>
>> wrote:
>>> At least set up a local caching resolver with 8.8.8.8 as the
>>> forwarder.

>> in case of bind this is bad to use any forwarder since it disables hint
>> zone, forwarders is more usefull pr zone, so keeep forwards out of options
>> containter in named.conf

> And where is the problem?
> Nobody needs the "hint zone" in his LAN because some reasons:
>
> * A big external forwarder has many requests in his cache
> * This cached requests are much faster and fewer as full recursion
> * It reduces the load of the root-Servers

But you can't use one of the big public DNS resolvers if you are using
spamhaus or any of the other BLs...
Reply | Threaded
Open this post in threaded view
|

Re: postfix and dns lookup

Reindl Harald-2
Am 05.02.2011 18:49, schrieb Charles Marcus:

>>> in case of bind this is bad to use any forwarder since it disables hint
>>> zone, forwarders is more usefull pr zone, so keeep forwards out of options
>>> containter in named.conf
>
>> And where is the problem?
>> Nobody needs the "hint zone" in his LAN because some reasons:
>>
>> * A big external forwarder has many requests in his cache
>> * This cached requests are much faster and fewer as full recursion
>> * It reduces the load of the root-Servers
>
> But you can't use one of the big public DNS resolvers if you are using
> spamhaus or any of the other BLs...
bullshit!

there is no difference if your stoopid nameserver makes recursion for
the request of your dns-client or the frowarder do this for him, think
about how works (google: recursion, ttl) and after that about your post

it is bad if every noob install his nameserver and configure it
for recursion because there are MANY requests, if you have some
clients in your lan this does not matter, but a amilserver
makes a lot of dns-requests

* your dns requests the root server
* root server gives him the address of the registry-server
* registry server tells you server the domain-dns
* finally your nameserver requests the authoritative one

if you are using a forwarder you leave the root-servers
fuck in peace and since most clients are using their isp
forwarder there is no single-point of load



signature.asc (269 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: postfix and dns lookup

Jeroen Geilman
On 2/5/11 6:58 PM, Reindl Harald wrote:
> bullshit!
<snipped paragraphs of invective>


Way to make your case.


--
J.

Reply | Threaded
Open this post in threaded view
|

Re: postfix and dns lookup

Reindl Harald-2


Am 05.02.2011 19:05, schrieb Jeroen Geilman:
> On 2/5/11 6:58 PM, Reindl Harald wrote:
>> bullshit!
> <snipped paragraphs of invective>
>
>
> Way to make your case.

sorry, but this was the only right answer for you can not
use dns-forwarder and blacklists"

http://www.postfix.org/TUNING_README.html
> Run a local name server to reduce slow-down due to DNS lookups.
> If you run multiple Postfix systems, point each local name server
> to a shared forwarding server to reduce the number of lookups
> across the upstream network link.

where does it interest your named if his forwarder is in
your lan or outside? there is no magic in dns


signature.asc (269 bytes) Download Attachment
12