I already tried that. I should have elaborated more on what I have already tried. It does not seem to have anything to do with the quotes, because if I do this...
objRR.CreateInstanceFromTextRepresentation CONST_SERVER, strZoneName, strZoneName & " IN TXT v=sp1", objOutParam I still get the line break at the end. That is with no quotes around the text string and no spaces in it. If I do the same with quotes, I get the same results. It seems to me that it doesn't have anything to do with my code and is automatically added, but I was hoping there was a way to defeat that. I may be wrong though. All other types of records (A, MX, NS) work perfectly, and TXT works except the line break. Anyone have any other ideas? -Daniel ---------- Original Message ---------------------------------- From: "William Stillwell" <[EMAIL PROTECTED]> Reply-To: [email protected] Date: Thu, 21 Apr 2005 08:45:25 -0400 >Instead of : " IN TXT ""v=spf1 mx ~all""" > >Try > >" IN TXT " & chr(34) & "v=spf1 mx ~all" & chr(34) > > >----- Original Message ----- >From: "Daniel Grotjan" <[EMAIL PROTECTED]> >To: <[email protected]> >Sent: Wednesday, April 20, 2005 11:43 PM >Subject: [Declude.JunkMail] OT: WMI scripting DNS TXT problems > > >> I'm trying to automate my dns zone creation and I am running into a >> problem with TXT records. I'm using WMI and when ever I create an SPF >> record (or any TXT record) it automatically adds a line break at the end >> of the record. Does anyone have any experience with this or have any idea >> what would cause this? The line below is the one I'm using to create the >> record. >> >> objRR.CreateInstanceFromTextRepresentation CONST_SERVER, strZoneName, >> strZoneName & " IN TXT ""v=spf1 mx ~all""", objOutParam >> >> I've tried this every different way I can and I always get the same >> result. In the zone file, it looks like this >> >> @ TXT ( "v=spf1 mx ~all" >> "" ) >> >> Also, does anyone know if having this break at the end will cause problems >> with any SPF implementations? >> >> -Daniel >> --- >> This E-mail came from the Declude.JunkMail mailing list. To >> unsubscribe, just send an E-mail to [EMAIL PROTECTED], and >> type "unsubscribe Declude.JunkMail". The archives can be found >> at http://www.mail-archive.com. >> --- >> This email has been scanned for possible viruses by Declude Antivirus. >> For more information on Declude Antivirus, Visit www.declude.com >> >> > >--- >This email has been scanned for possible viruses by Declude Antivirus. >For more information on Declude Antivirus, Visit www.declude.com > >--- >This E-mail came from the Declude.JunkMail mailing list. To >unsubscribe, just send an E-mail to [EMAIL PROTECTED], and >type "unsubscribe Declude.JunkMail". The archives can be found >at http://www.mail-archive.com. > --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
