[nsp-sec] dns issues?

[Chris Morrow]

On Fri, 27 Feb 2009, Mike Lewinski wrote:
> clock.redhat.com.       115     IN      A       115.126.5.200

hknetcom

>
> ;; AUTHORITY SECTION:
> clock.redhat.com.       79612   IN      NS      nx1.redhat.com.
> clock.redhat.com.       79612   IN      NS      nx2.redhat.com.
>
> ;; Query time: 3 msec
> ;; SERVER: 63.211.239.4#53(63.211.239.4)
>
> [12:46] david: 115.126.5.200, second result, is the squid proxy
> [12:46] david: resolves to vipertheripper.com
> [12:47] david: then, after a restart of named its went away
>
> By the time I started looking into this vipertheripper.com was no longer 
> resolving for me - the glue at roots for their NS was missing.

;; QUESTION SECTION:
;vipertheripper.com.            IN      A

;; ANSWER SECTION:
vipertheripper.com.     14387   IN      A       193.138.172.5

;; AUTHORITY SECTION:
vipertheripper.com.     14381   IN      NS      ns1.beforethehost.com.
vipertheripper.com.     14381   IN      NS      ns2.beforethehost.com.

person:         Peteris Vainags
address:        Mazcenu aleja 19, Marupe, Latvia
phone:          +371 22131249
nic-hdl:        PV3578-RIPE
mnt-by:         BALTCONN-MNT
source:         RIPE # Filtered

% Information related to '193.138.172.0/22AS44245'

route:          193.138.172.0/22
descr:          Baltconn SIA
origin:         AS44245
mnt-by:         BALTCONN-MNT
source:         RIPE # Filtered