On Wed, Sep 05, 2001 at 02:20:18PM +0200, Karsten W. Rohrbach wrote:
> hmm
> seen that on one of my larger boxes around, too
>
> created an mx-in ip list:
> rohrbach@WM:datasink[~]13% dnsqr mx msn.com|cut -f6 -d' '|grep
> msn.com|xargs -n1 dnsip
> 207.46.181.24
> 207.46.181.25
> 207.46.181.27
> 207.46.181.29
> 207.46.181.32
> 207.46.181.33
> 207.46.181.35
> 207.46.181.37
> 207.46.181.38
> 207.46.181.26
> 207.46.181.45
> 207.46.181.41
Try:
$ dnsip `dnsmx msn.com|cut -f2 -d' ``
It's shorter :)
> the question is, whether to set up a local authoritative tinydns for
> serving msn.com mx records, or thinking about plan b...
> any ideas for plan b?
As pointed out, it seems to work fine when using dnscache.
Greetz, Peter
--
Monopoly http://www.dataloss.nl/monopoly.html
