In article ,
Darvin Denmian wrote:
> Hi,
>
> below the information you requested:
>
> ; <<>> DiG 9.7.3-P3 <<>> @ns1.domain.com.br spf_16416.domain.com.br +tcp TXT
> ; (1 server found)
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 59810
NXDO
Hi,
below the information you requested:
; <<>> DiG 9.7.3-P3 <<>> @ns1.domain.com.br spf_16416.domain.com.br +tcp TXT
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 59810
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDI
Actually, no, there isn't enough information in your reply to help you debug.
Please issue, from a machine not your DNS server:
$ dig @your-server-address +tcp domain.name TXT
A TXT record has a maximum length of around 64k per TXT record, and each part
of the text record can be 255 bytes, if m
Hi,
Graff, thanks for you reply...
As you can see below my server is accepting DNS connections:
ACCEPT udp -- anywhere anywhereudp dpt:domain
ACCEPT tcp -- anywhere anywheretcp dpt:domain
and the service is up and running:
# netstat -
In article ,
Darvin Denmian wrote:
> I'm asking this because one of the domains configured in my Bind
> server have more than 4k TXT entries and its zone file have more than
> 400KB.
Do you mean 4K TXT entries for a single name, or across all names in the
zone?
--
Barry Margolin
Arlington,
more than 4k will exceed the default settings for EDNS0 UDP responses.
If you dig @ your server, with +tcp, do you get a reply? If not, perhaps you
are not allowing TCP connections to port 53?
What error you are getting may be of help.
--Michael
On Feb 29, 2012, at 1:20 PM, Darvin Denmian wro
6 matches
Mail list logo