OT: Silly Bind question

[DAve]

Mark D. Foster wrote:
> DAve wrote:
>> Andy Dills wrote:
>>   
>>> On Sun, 3 Feb 2008, DAve wrote:
>>>     
>>>> I am stumped, what have I done wrong?
>>>>       
>>> You'll kick yourself. Here's the hint:
>>>
>>> /users/andy>dig @ns1.totallogic.com ftp.pixelhammer.com txt
>>>
>>> ; <<>> DiG 9.3.4 <<>> @ns1.totallogic.com ftp.pixelhammer.com txt
>>> ; (1 server found)
>>> ;; global options:  printcmd
>>> ;; Got answer:
>>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26833
>>> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3
>>>
>>> ;; QUESTION SECTION:
>>> ;ftp.pixelhammer.com.           IN      TXT
>>>
>>> ;; ANSWER SECTION:
>>> ftp.pixelhammer.com.    86400   IN      TXT     "v=spf1 ip4:65.196.224.82 ip4:65.196.224.83 ~all"
>>>     
>> I'm kicking but it ain't helping. Interesting that the host ftp works.
>> It is also the last host in the zone. I tried tying the txt record to
>> the origin but no change. According to the Bind book, and to the openspf
>> folks, this should work.
>>
>> pixelhammer.com.	IN	TXT	"some sorta krazy text string"
>>
>> But it don't. Now, I am even more confused. Does the location of the
>> Text record 'within' the zone file make a difference?
>>
>> Thanks,
>>
>> DAve
>>
>>   
> Andy was right, it's the line-ordering in your zone file.
> I take it you can't slave the zone from tinydns to bind?
> 

Arrrg! I tried moving the txt record but no change.  I can put the recs
in any order I want as the script that generates my Bind Zones pulls
them from SQL, so arranging the keys to write out TXT in any place
within the zone is easy enough to do. But I didn't see a difference before.

I'll relook at what I did. This should not be that difficult, online
docs show text examples with no mention of where in the zone they need
to be. I would ahve thought that it A) didn't matter, or B) an origin
line prior to the TXT line, or B) a full domain name in the text-name
field would be able to over ride the previous host name.

IOW,

host	IN	A 	xxx.xxx.xxx.xxx
domain.	IN	TXT	"something"

I would have though that a full origin name as the left value on the TXT
line would override the previous host value. But that does not seem to
be so. I still think I've done something wrong here.

DAve


-- 
Google finally, after 7 years, provided a logo for
veterans. Thank you Google. What to do with my signature now?