Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 09 Apr 2008 10:07:14 -0500
From:      Paul Schmehl <pauls@utdallas.edu>
To:        D Hill <d.hill@yournetplus.com>
Cc:        FreeBSD Questions <freebsd-questions@freebsd.org>
Subject:   Re: OT question about dns
Message-ID:  <D91870E8215B359B99419D08@utd65257.utdallas.edu>
In-Reply-To: <alpine.BSF.1.10.0804072310480.81928@duane.dbq.yournetplus.com>
References:  <4A88BCAAE6CDFDDFF91E3E30@utd65257.utdallas.edu> <alpine.BSF.1.10.0804072310480.81928@duane.dbq.yournetplus.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--On Monday, April 07, 2008 23:14:29 +0000 D Hill <d.hill@yournetplus.com> 
wrote:

> On Mon, 7 Apr 2008 at 18:05 -0500, pauls@utdallas.edu confabulated:
>
>> Does anyone know how to use dig or some other tool to query for TXT records
>> in DNS?
>>
>> I'm working on implementing spf on a small domain that I maintain, and it
>> doesn't seem to be working (according to the validators I'm using.)  I'd
>> like  to be able to query the dns server myself, but I can't seem to find
>> anything  on how to extract or view TXT records for a domain.
>>
>> I tried dig @server domain TXT and dig @server domain MX, but I don't get
>> the  TXT record.
>
> %dig @what_ever_nameserver example.com txt
>
> works for me. Let's see what AOL returns:
>
> %dig @localhost aol.com txt
> ...
> ;; QUESTION SECTION:
> ;aol.com.                       IN      TXT
>
> ;; ANSWER SECTION:
> aol.com.                300     IN      TXT     "v=spf1 ip4:152.163.225.0/24
> ip4:205.188.139.0/24 ip4:205.188.144.0/24 ip4:205.188.156.0/23
> ip4:205.188.159.0/24 ip4:64.12.136.0/23 ip4:64.12.138.0/24
> ip4:64.12.143.99/32 ip4:64.12.143.100/32 ip4:64.12.143.101/32 ptr:mx.aol.com
> ?all"
> aol.com.                300     IN      TXT     "spf2.0/pra
> ip4:152.163.225.0/24 ip4:205.188.139.0/24 ip4:205.188.144.0/24
> ip4:205.188.156.0/23 ip4:205.188.159.0/24 ip4:64.12.136.0/23
> ip4:64.12.138.0/24 ip4:64.12.143.99/32 ip4:64.12.143.100/32
> ip4:64.12.143.101/32 ptr:mx.aol.com ?all"

Ummm...this turned out to be an ID10t problem.  I'm too embarrassed to explain 
exactly what.  :-(

But thanks for the explanation.  :-)

-- 
Paul Schmehl (pauls@utdallas.edu)
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D91870E8215B359B99419D08>