does this mean, for example, i have two nameservers,
ns1.example.pw.
ns2.example.pw.
for zone example.pw.
Now I want these two nameservers to be example.com, example.net,
example.org 's auth-nameservers. To do that we have to put these two
hostnames into com, net, org's zone space. And this c
nervous breakdown
out a few good years before you finally lose your shit and throw in the
towel.
- mark
-Original Message-
From: dns-operations [mailto:dns-operations-boun...@dns-oarc.net] On
Behalf Of bert hubert
Sent: Thursday, June 11, 2015 11:00
To: Kevin C.
Cc: dns-operati...@dns-oarc.net
Su
Hello,
Sorry this subject may have no relations to DNS technology.
But one of our customers, who is a small registrar, has about 20,000
domains in our systems, increase slowly by day.
Due to frequent DDoS we have no capability to help him, but suggest him
move to another provider.
Do you know w
No. I really did nothing, :p
On 2015/6/8 星期一 18:21, Stephane Bortzmeyer wrote:
At 10:04 UTC today:
They read the mailing list and fix in real-time
___
dns-operations mailing list
dns-operations@lists.dns-oarc.net
https://lists.dns-oarc.net/mailman/li
I am not very sure, but this is may due to split zones.
dwdns is a suite of complicated nameservers. i.e,
$ dig rise.game.yy.com @202.96.128.86 +short
58.215.138.2
$ dig rise.game.yy.com @202.106.0.20 +short
122.97.250.2
As you see, from different LDNS we can get different results.
On 2015/6
A great explaining. Thank you Stephane.
On 2015/6/8 星期一 16:54, Stephane Bortzmeyer wrote:
If you want more technical details:
dig, by default, requests a A record. defensor.game.yy.com has no A
record (ANSWER:0 in dig's answer) but it may have other types of
records (, for instance, since w
Thank you Jim.
On 2015/6/8 星期一 16:49, Jim Reid wrote:
FWIW there's an inconsistency between the two authoritative name servers for
game.yy.com. dwdns1.nsbeta.info returns NOHOST while dwdns2.nsbeta.info returns
NXDOMAIN for lookups of defensor.game.yy.com QTYPEs.
what causes the inconsisten
Hello,
Sometime I got "NOERROR" from the answer, but sometime got "NXDOMAIN".
At what case the nameserver returns "NOERROR" or "NXDOMAIN" for a
non-exist record? Thank you.
There are two digs below, please notice they are different hostnames.
$ dig defensor.game.yy.com @localhost
; <<>> DiG
Thanks for all the helps.
Now I resolved the issues.
Just add the public IP of the VPS to named.conf below, restart bind and
it works.
controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; 116.251.xx.xx; } keys { "rndc-key"; };
};
The kernel's routing may have problems, b/c
rndc.conf and named.conf are right.
Thanks.
On 2015/5/27 星期三 16:13, Kevin C. wrote:
Hello,
Can you tell me why this rndc run failed?
# rndc reload
rndc: connection to remote host closed
This may indicate that
* the remote server is using an older version of the command protocol,
* this host is not
Hello,
Can you tell me why this rndc run failed?
# rndc reload
rndc: connection to remote host closed
This may indicate that
* the remote server is using an older version of the command protocol,
* this host is not authorized to connect,
* the clocks are not synchronized, or
* the key is invalid.
Hello,
Do you know what's the special usage for resolveip command?
I saw it's not similiar to dig tool. for instance,
~$ dig www.sina.com.cn +short
jupiter.sina.com.cn.
ara.sina.com.cn.
121.14.1.190
58.63.236.248
121.14.1.189
~$ resolveip -s www.sina.com.cn
121.14.1.190
dig returns all three I
12 matches
Mail list logo
