Last day I tried new bind, and the crash when reloading comes.
The reload command: 'rndc -c etc/rndc.conf reload' or 'killall -HUP
named', the used rndc.conf was generated by 'rndc-confgen -r
/dev/urandom -t /chroot/'. And messages below comes from offline
debug.
[snipped]
21-Mar-2012 16:46:12.56
In message <040b89c8b1e1d945ae2700c511a039e915f...@atmexdb04.dsw.net>, "Lightne
r, Jeff" writes:
> I donât think the target is blocking as I get the following:
Jeff, the servers *are* dropping packets sourced from port 53. By
default dig uses a ephemeral port assigned by the system. It doesn'
On 21/03/2012 09:41, Matus UHLAR - fantomas wrote:
> maybe the admin set that up to force local servers using random ports,
> instead of 53, for outgoing requests. Nobody should use port 53 for
> _ougtoing_ requests.
You're wrong. A name server can use any source port from 1 up to 65535
for an ou
I don’t think the target is blocking as I get the following:
dig www.dubaiairport.com
; <<>> DiG 9.8.1 <<>> www.dubaiairport.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36668
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
;
Dear All,
When i executed #dig www.dubaiairport.com, i am getting bleow response
;<<>> DiG 9.3.4-P1 <<>> www.dubaiairport.com
;; global options: printcmd
;; connection timed out; no servers could be reached
When i checked the firewall logs, as you all confirmed, traffic is leaving
from bot
On 21.03.12 09:23, Mark Andrews wrote:
Stupid firewall rules in front of the nameservers. They block
traffic sent from port 53 which is the port lots of nameservers
used to send query traffic. When will firewall administrators learn
that the source ports can be anything, that they are not signi
I have read your blog and do not agree with you about one of your conclusions
to non-existence of ns rrs of www.qq.com in the ns-tel1.qq.com server. One
recursor must request ns rr(s) of www.qq.com to the ns[1-4].qq.com server
before requesting to ns-tel[1-2].qq.com. When it receives the ns rrs
You might want to read my this blog；
http://www.nsbeta.info/archives/115
HTH
于 2012-3-21 15:07, Felix New 写道:
when i dumpdb from the cache dns, some domain's ns records are glue
DNS, and others are authauthority.
The TTL are different. which type is used in Cache DNS?
___
8 matches
Mail list logo
