Diagnosing DNS problems...?

jon jon at trafficdesigns.com
Fri May 26 10:18:47 MST 2006


Howdy folks...

So, if ya haven't guess, I get to play sysadmin this week as we're 
trying to get a new project off the ground. Which is fun. However, as a 
web developer, I'm wandering into areas that I haven't really explored...

So... here's where I'm at: I'm trying to get mydns up and running on my 
ubuntu box. No problems there.... however, I'm not really clear on how 
to set up individual records and get 'em to resolve correctly.

What's the best way to diagnose dns setup problems? Is there a good 
tutorial for working through these things?

So... let's say I want blah.huggabear.com to resolve to 69.55.220.101, 
does this dig response look right?



; <<>> DiG 9.3.1 <<>> blah.huggabear.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23416
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1

;; QUESTION SECTION:
;blah.huggabear.com.            IN      A

;; ANSWER SECTION:
blah.huggabear.com.     85601   IN      A       69.55.220.101

;; AUTHORITY SECTION:
huggabear.com.          160678  IN      NS      ns2.tdnameservers.com.
huggabear.com.          160678  IN      NS      ns1.tdnameservers.com.

;; ADDITIONAL SECTION:
ns1.tdnameservers.com.  160664  IN      A       69.50.220.101

;; Query time: 164 msec
;; SERVER: 216.87.64.2#53(216.87.64.2)
;; WHEN: Fri May 26 10:08:57 2006
;; MSG SIZE  rcvd: 118



Thanks folks...

     -- jon


---------
jon roig
web developer
http://jonroig.com




More information about the PLUG-discuss mailing list