[NCLUG] Re: reaching NCLUG.ORG...still has problems

[Matt Clauson]

If you're running linux, do the following:

dig nclug.org

it should return something like the following:

mec at epsilon:~$ dig nclug.org

; <<>> DiG 8.2 <<>> nclug.org 
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1
;; QUERY SECTION:
;;	nclug.org, type = A, class = IN

;; ANSWER SECTION:
nclug.org.		23h59m41s IN A	216.17.175.196

;; AUTHORITY SECTION:
nclug.org.		23h59m41s IN NS  ns.nclug.org.

;; ADDITIONAL SECTION:
ns.nclug.org.		23h59m41s IN A	216.17.175.196

;; Total query time: 3 msec
;; FROM: epsilon to SERVER: default -- 192.168.100.254
;; WHEN: Thu Dec  7 13:56:36 2000
;; MSG SIZE  sent: 27  rcvd: 76

See those sections where it says '23h59m41s'?  That's the TTL on the DNS server
you're using -- they've got cached records and most likely they haven't passed
yet.  (Note in the above example that the information IS correct -- tummy.com
has the TTL for those records set for 1 day it appears.)

Hopefully, your provider flushes their cache at least once a day, in case FRII
really fucked up the DNS settings.  Otherwise, I suggest you give their
customer service line a call, and have them ask their NOC to manually flush
their DNS caches.

You will most likely be back to normal shortly.

--mec