How NOT to figure out a nameserver

So I was trying to install this piece of software that I wanted to test ..
It came with a weird installscript that kept telling me it couldn't ping tom my nameserver 

  1. .. checking network access via ping to DNS/IP: IN
  2. ...... unable to ping: IN : ping returned: 2
  3. unable to ping DNS name server: IN
  4. 192.168.1.209 : ping returned code: 2

Now why would it tro to ping IN ?

This is why .. the scripts tries to find out my nameserver using dig

  1. root@C51 ~]# dig localhost | grep SERVER  | cut -d# -f 1| awk '{print
  2. $3}'
  3. IN
  4. 192.168.1.209

It didn't expect to get this feedback from dig

  1. [root@C51 ~]# dig localhost
  2.  
  3. ; <<>> DiG 9.3.3rc2 <<>> localhost
  4. ;; global options:  printcmd
  5. ;; Got answer:
  6. ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 32043
  7. ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
  8.  
  9. ;; QUESTION SECTION:
  10. ;localhost.                     IN      A
  11.  
  12. ;; AUTHORITY SECTION:
  13. .                       10215   IN      SOA     A.ROOT-SERVERS.NET.
  14. NSTLD.VERISIGN-GRS.COM. 2008031700 1800 900 604800 86400
  15.  
  16. ;; Query time: 7 msec
  17. ;; SERVER: 192.168.1.209#53(192.168.1.209)
  18. ;; WHEN: Mon Mar 17 21:02:50 2008
  19. ;; MSG SIZE  rcvd: 102

Submitted by Kris Buytaert on Mon, 03/17/2008 - 21:17
Tags:
»