Bind 9.2.4 refuses to give TXT records

[Treptow, Craig]

Please post the contents of the file containing the data for =
"wananchi.com".  It appears this is "/etc/namedb/wananchi.com"

-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
Behalf Of Odhiambo Washington
Sent: Tuesday, January 25, 2005 9:15 AM
To: bind-users at isc.org
Subject: Bind 9.2.4 refuses to give TXT records


Ladies & Gentlemen,

I have a domain. wananchi.com, running under bind-9.2.4 and I have
specified some TXT records for the purpose of SPF. However, all
queries seem to work well (tell me if they don't) EXCEPT the TXT
records!!

dig wananchi.com txt

..gives nothing! I have looked at my configuration as well:
named-checkzone wananchi.com /etc/namedb/wananchi.com

zone wananchi.com/IN: loaded serial 2005012502
OK.

When I reload this zone, or even reload bind, I see no errors at all.

I am now lost as to why the TXT records are not returned and would
appreciate any assistance in fixing this.




-Wash

http://www.netmeister.org/news/learn2quote.html

--
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+
    |\      _,,,---,,_     | Odhiambo Washington    <wash at wananchi.com>
Zzz /,`.-'`'    -.  ;-;;,_ | Wananchi Online Ltd.   www.wananchi.com
   |,4-  ) )-,_. ,\ (  `'-'| Tel: +254 20 313985-9  +254 20 313922
  '---''(_/--'  `-'\_)     | GSM: +254 722 743223   +254 733 744121
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+
Rudin's Law:
	If there is a wrong way to do something, most people will do it
every time.




-----Message=20Disclaimer-----

This=20e-mail=20message=20is=20intended=20only=20for=20the=20use=20of=20the=20individual=20or
entity=20to=20which=20it=20is=20addressed,=20and=20may=20contain=20information=20that=20is
privileged,=20confidential=20and=20exempt=20from=20disclosure=20under=20applicable=20law.
If=20you=20are=20not=20the=20intended=20recipient,=20any=20dissemination,=20distribution=20or
copying=20of=20this=20communication=20is=20strictly=20prohibited.=20If=20you=20have
received=20this=20communication=20in=20error,=20please=20notify=20us=20immediately=20by
reply=20email=20to=20Connect at principal.com=20and=20delete=20or=20destroy=20all=20copies=20of
the=20original=20message=20and=20attachments=20thereto.=20Email=20sent=20to=20or=20from=20the
Principal=20Financial=20Group=20or=20any=20of=20its=20member=20companies=20may=20be=20retained
as=20required=20by=20law=20or=20regulation.

Nothing=20in=20this=20message=20is=20intended=20to=20constitute=20an=20Electronic=20signature
for=20purposes=20of=20the=20Uniform=20Electronic=20Transactions=20Act=20(UETA)=20or=20the
Electronic=20Signatures=20in=20Global=20and=20National=20Commerce=20Act=20("E-Sign")
unless=20a=20specific=20statement=20to=20the=20contrary=20is=20included=20in=20this=20message.