Thanks Kal. That let things be clear.
--- On Mon, 11/5/09, Kal Feher wrote:
>
> Note that the reason your queries fail is because name
> servers are supposed
> to assume that the apex of the zone contains the most
> correct data.
> Therefore if the 2 name servers to which this zone is
> delega
The zone appears to be configured incorrectly. That is why your results and
Scott's are so odd. I'll explain below, but in summary, the name servers to
which the zone is delegated have what appears to be rubbish records.
Specifically these:
gdpu.cn.3600IN NS gdpu.cn.
Hi,
Firstly the DNS serveres for that domain is not mastered by me.
I got the NS dig info as below.
You can see, if I specify another public DNS (211.66.80.161), the results can
be fetched. If I don't specify a DNS (use the default one 202.96.128.143 of my
ISP), dig gets nothing.
So I'm really
On May 11, 2009, at 2:56 AM, Tech W. wrote:
For this domain, gdpu.cn, I tried to find its ns record:
dig gdpu.cn ns
with no results.
But I can dig its www record as below.
why this happened? I can't understand entirely..
Thanks.
Actually, here is what I get back:
$dig gdpu.cn ns
; <<>> Di
Is it still happening? Can you show dig output for "dig gdpu.cn ns"
On May 11, 2009, at 2:56 AM, Tech W. wrote:
Hello,
For this domain, gdpu.cn, I tried to find its ns record:
dig gdpu.cn ns
with no results.
But I can dig its www record as below.
why this happened? I can't understand enti
Hello,
For this domain, gdpu.cn, I tried to find its ns record:
dig gdpu.cn ns
with no results.
But I can dig its www record as below.
why this happened? I can't understand entirely..
Thanks.
# dig www.gdpu.cn
; <<>> DiG 9.5.0-P2 <<>> www.gdpu.cn
;; global options: printcmd
;; Got answer:
6 matches
Mail list logo