[RFCI-Discuss] wirralnews.com

Derek J. Balling dredd at megacity.org
Wed Sep 5 06:52:55 EDT 2007


This is one of those cases where "if there were a bogusns zone, this  
would be listed"... the problem is that we can't chase down their  
authoritative NS set, because the NS's which are pointed to by the  
roots say (authoritatively) that there are no authoritative NSes...

$ dig @dpns1.dnsnameserver.org wirralnews.com. ns

; <<>> DiG 9.4.1 <<>> @dpns1.dnsnameserver.org wirralnews.com. ns
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45815
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;wirralnews.com.			IN	NS

;; AUTHORITY SECTION:
.			86400	IN	SOA	A.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.com.  
2004042200 1800 900 604800 86400

;; Query time: 21 msec
;; SERVER: 64.94.29.104#53(64.94.29.104)
;; WHEN: Wed Sep  5 06:51:32 2007
;; MSG SIZE  rcvd: 104

.... so when we go chasing down to form a list of "who should we ask  
about the MX record", the end result is a zero-length list


On Sep 4, 2007, at 4:43 PM, Simon Arlott wrote:

> The bogusmx checker doesn't handle the following:
>
> wirralnews.com.         172800  IN      NS       
> dpns1.dnsnameserver.org.
> wirralnews.com.         172800  IN      NS       
> dpns2.dnsnameserver.org.
> wirralnews.com.         172800  IN      NS       
> dpns3.dnsnameserver.org.
> wirralnews.com.         172800  IN      NS       
> dpns4.dnsnameserver.org.
> ;; Received 129 bytes from 2001:503:a83e::2:30#53(a.gtld- 
> servers.net) in 157 ms
>
> wirralnews.com.         86400   IN      MX      0 *.mx.*.
> ;; Received 265 bytes from 64.94.29.104#53(dpns1.dnsnameserver.org)  
> in 98 ms
>
>
> wirralnews.com.         1800    IN      A       72.5.175.97
> ;; Received 259 bytes from 64.94.29.104#53(dpns1.dnsnameserver.org)  
> in 98 ms
>
> -- 
> Simon Arlott
> _______________________________________________
> RFCI-Discuss mailing list
> RFCI-Discuss at lists.megacity.org
> http://lists.megacity.org/mailman/listinfo/rfci-discuss



More information about the RFCI-Discuss mailing list