[cobalt-users] DNS Issue elsewhere or is it our RAQ

[Chae <chae@xxxxxxxxxxxx>]

Hi Yah,

Never seen this one before...

Server services seemed to stop working this morning...couldn't access 
httpd, ftp or ssh, phone the colo and they told me server was still up and 
running. So waited 30 minutes to see if the server would sort itself out 
but no joy so rebooted and checked the logs to see what went wrong and this 
is what happened prior to the reboot...

I've trimmed the log file down as it went on for 30 mins remember...

Dec 31 08:02:27 ns named[20769]: ns_forw: query(72.195.21.167.in-addr.arpa) 
NS points to CNAME (NS.OIS.STATE.DE.US:) learnt 
(CNAME=167.21.1.120:NS=192.31.80.32)
Dec 31 08:05:12 ns named[20769]: No root nameservers for class IN
Dec 31 08:05:12 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?
Dec 31 08:05:12 ns named[20769]: sysquery: findns error (2) on ns3.apnic.net?
Dec 31 08:05:17 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?
Dec 31 08:05:17 ns named[20769]: sysquery: findns error (2) on ns3.apnic.net?
Dec 31 08:05:22 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?
Dec 31 08:05:22 ns named[20769]: sysquery: findns error (2) on ns3.apnic.net?
Dec 31 08:05:27 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?
Dec 31 08:05:27 ns named[20769]: sysquery: findns error (2) on ns3.apnic.net?
Dec 31 08:05:37 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?
Dec 31 08:05:37 ns named[20769]: sysquery: findns error (2) on ns3.apnic.net?
Dec 31 08:05:47 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?
Dec 31 08:05:47 ns named[20769]: sysquery: findns error (2) on ns3.apnic.net?
Dec 31 08:06:07 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?
Dec 31 08:06:07 ns named[20769]: sysquery: findns error (2) on ns3.apnic.net?
Dec 31 08:06:27 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?
Dec 31 08:06:27 ns named[20769]: sysquery: findns error (2) on ns3.apnic.net?
Dec 31 08:06:32 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?
Dec 31 08:06:32 ns named[20769]: sysquery: findns error (2) on ns3.apnic.net?
Dec 31 08:06:37 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?
Dec 31 08:06:37 ns named[20769]: sysquery: findns error (2) on ns3.apnic.net?
Dec 31 08:06:42 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?
Dec 31 08:06:42 ns named[20769]: sysquery: findns error (2) on ns3.apnic.net?
Dec 31 08:06:47 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?
Dec 31 08:06:47 ns named[20769]: sysquery: findns error (2) on ns3.apnic.net?
Dec 31 08:06:57 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?
Dec 31 08:06:57 ns named[20769]: sysquery: findns error (2) on ns3.apnic.net?
Dec 31 08:07:07 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?
Dec 31 08:07:07 ns named[20769]: sysquery: findns error (2) on ns3.apnic.net?
Dec 31 08:07:27 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?
Dec 31 08:07:27 ns named[20769]: sysquery: findns error (2) on ns3.apnic.net?
Dec 31 08:08:27 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?
Dec 31 08:08:27 ns named[20769]: sysquery: findns error (2) on ns3.apnic.net?
Dec 31 08:08:27 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?
Dec 31 08:08:27 ns named[20769]: sysquery: findns error (2) on ns3.apnic.net?
Dec 31 08:08:27 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?
Dec 31 08:08:27 ns named[20769]: sysquery: findns error (2) on ns3.apnic.net?
Dec 31 08:08:47 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?
Dec 31 08:08:47 ns named[20769]: sysquery: findns error (2) on ns3.apnic.net?
Dec 31 08:08:47 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?
Dec 31 08:08:47 ns named[20769]: sysquery: findns error (2) on ns3.apnic.net?
Dec 31 08:08:47 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?
Dec 31 08:08:47 ns named[20769]: sysquery: findns error (2) on ns3.apnic.net?
Dec 31 08:09:07 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?
Dec 31 08:09:07 ns named[20769]: sysquery: findns error (2) on ns3.apnic.net?
Dec 31 08:09:07 ns named[20769]: sysquery: findns error (2) on NS1.APNIC.NET?
Dec 31 08:09:07 ns named[20769]: sysquery: findns error (2) on NS3.APNIC.NET?
Dec 31 08:09:07 ns named[20769]: sysquery: findns error (2) on ns1.apnic.net?

Goes on and one....

Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
macu.ma.mt.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
ohcu.oh.mt.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
wycu.wy.br.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
orcu.or.br.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
macu.ma.mt.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
ohcu.oh.mt.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
orcu.or.br.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
wycu.wy.br.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
macu.ma.mt.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
orcu.or.br.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
wycu.wy.br.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
ohcu.oh.mt.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
ohcu.oh.mt.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
orcu.or.br.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
wycu.wy.br.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
macu.ma.mt.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
ohcu.oh.mt.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
orcu.or.br.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
wycu.wy.br.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
macu.ma.mt.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
macu.ma.mt.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
orcu.or.br.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
wycu.wy.br.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
ohcu.oh.mt.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
macu.ma.mt.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
ohcu.oh.mt.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
wycu.wy.br.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
orcu.or.br.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
macu.ma.mt.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
ohcu.oh.mt.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
orcu.or.br.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
wycu.wy.br.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
DBRU.BR.NS.ELS-GMS.ATT.NET?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
macu.ma.mt.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
ohcu.oh.mt.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
wycu.wy.br.np.els-gms.att.net?
Dec 31 08:15:57 ns named[20769]: sysquery: findns error (2) on 
orcu.or.br.np.els-gms.att.net?

Goes on and one....

The servers using the latest Solarspeed Bind pkg.
Was this due to the apic DNS servers not being available?
Was it due to my server not being able to communicate with the other DNS 
servers?
Could an attack on the server cause this?
Or is it one of those Cobalt things that appear now and again ;)

Happy New Year to all when it comes

Regards

Chae