[dns-operations] about answer status

[Kevin C.]

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/8 星期一 18:16, Jim Reid wrote:
> FWIW at 08:43 UTC today:
>
> gromit% dig @dwdns1.nsbeta.info defensor.game.yy.com any | grep status
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3579
>
> gromit% dig @dwdns2.nsbeta.info defensor.game.yy.com any | grep status
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51382
>
> At 10:04 UTC today:
>
> gromit% dig @dwdns1.nsbeta.info defensor.game.yy.com any | grep status
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36559
> gromit% dig @dwdns2.nsbeta.info defensor.game.yy.com any | grep status
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64545