Heh, weird. Must be something else going on then. Thanks!
On Jan 8, 2010, at 5:16 PM, Tyler Hall wrote:
> Seems to work as configured (atleast from here)
>
> -bash-3.00$ dig _autodiscover._tcp.genesisgroup.info SRV +short
> 0 0 443 secure.genesisgroup.info.
> -bash-3.00$
>
>
>
>
> On Fri,
Seems to work as configured (atleast from here)
-bash-3.00$ dig _autodiscover._tcp.genesisgroup.info SRV +short
0 0 443 secure.genesisgroup.info.
-bash-3.00$
On Fri, Jan 8, 2010 at 6:15 PM, Ron Garret wrote:
>
> [...@vm1:~/pkg/git-1.6.6]$ dig _autodiscover._tcp.genesisgroup.info
>
> ; <<>> Di
[...@vm1:~/pkg/git-1.6.6]$ dig _autodiscover._tcp.genesisgroup.info
; <<>> DiG 9.3.4-P1.1 <<>> _autodiscover._tcp.genesisgroup.info
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25442
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITION
What happens when you dig for _autodiscover._tcp.genesisgroup.info
On Fri, Jan 8, 2010 at 6:09 PM, Ron Garret wrote:
> My name server is working properly, except that the following SRV record is
> not being served:
>
> mysql> select * from records where type='SRV';
> ++---+
My name server is working properly, except that the following SRV record is not
being served:
mysql> select * from records where type='SRV';
++---+--+--++--+--+-+
| id | domain_id | name
I think your confusing escaping. Escaping in mysql isn't stored in the
database, it's only to pass it though to the server. The mysql server
removed the escaping, before it stored it, so when you read it, it's
clean and ready to be used.
This causes issues as to what needs to be escaped, ca
Hi Rudolph
> maybe there's a misunderstanding here on my side but
> mysql_real_escape_string() still adds backslashes to some special chars
> (like ' or " and \), doesnt it? That would probably not affect the case of
> escaping a semicolon like stated below.
Yes, it does but that's a MySQL specif
Hi List,
maybe there's a misunderstanding here on my side but
mysql_real_escape_string() still adds backslashes to some special chars
(like ' or " and \), doesnt it? That would probably not affect the case of
escaping a semicolon like stated below.
But what happens if theres a TXT record contaning
