Using dig for checking domain registration

[Scott Haneda]

Comments interspersed below...

On Jun 29, 2009, at 5:42 PM, Mark Andrews wrote:

>> Hi Mark, thanks for the reply.  I do not understand your last
>> suggestion.  If the domain in question is customtruckgraphics.us, can
>> you show me an example of how to do this?
>
> % dig ns us
> ; <<>> DiG 9.3.6-P1 <<>> ns us
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38654
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 6
>
> ;; QUESTION SECTION:
> ;us.				IN	NS
>
> ;; ANSWER SECTION:
> us.			518400	IN	NS	a.gtld.biz.
> us.			518400	IN	NS	i.gtld.biz.
> us.			518400	IN	NS	c.gtld.biz.
> us.			518400	IN	NS	b.gtld.biz.
> us.			518400	IN	NS	j.gtld.biz.
> us.			518400	IN	NS	k.gtld.biz.
>
> ;; ADDITIONAL SECTION:
> a.gtld.biz.		516703	IN	A	209.173.53.162
> b.gtld.biz.		516685	IN	A	209.173.57.162
> c.gtld.biz.		516677	IN	A	209.173.60.65
> i.gtld.biz.		516687	IN	A	156.154.96.126
> k.gtld.biz.		516672	IN	A	156.154.72.65
> j.gtld.biz.		516601	IN	AAAA	2001:503:a124:ffff:ffff:ffff:ffff:ff7e
>
> ;; Query time: 438 msec
> ;; SERVER: 127.0.0.1#53(127.0.0.1)
> ;; WHEN: Tue Jun 30 10:32:37 2009
> ;; MSG SIZE  rcvd: 232
>
> % dig +norec customtruckgraphics.us ns @a.gtld.biz
> ; <<>> DiG 9.3.6-P1 <<>> +norec customtruckgraphics.us ns @a.gtld.biz
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22320
> ;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;customtruckgraphics.us.		IN	NS
>
> ;; AUTHORITY SECTION:
> customtruckgraphics.us.	7200	IN	NS	NS1.OCTANEDNS.COM.
> customtruckgraphics.us.	7200	IN	NS	NS2.OCTANEDNS.COM.
>
> ;; Query time: 242 msec
> ;; SERVER: 209.173.53.162#53(209.173.53.162)
> ;; WHEN: Tue Jun 30 10:33:22 2009
> ;; MSG SIZE  rcvd: 89

So, the idea is to `dig ns us` and fish out any? of the NS's in the  
result set, store that NS, and feed it to dig again, with `dig +norec  
customtruckgraphics.us ns @a.gtld.biz` where `a.gtld.biz` is the  
result I stored?

>> I can not
>> rebuild named entirely, as it was enough trouble getting DLZ working
>> on RHEL. I would just need to fish out dig, and build that separate.
>
> 	I suspect you will find it easier to just fully upgrade.
> 	You may need to go find test rpms.  I'm not a Linux guy but
> 	I'm sure they shouldn't be hard to find or for that matter
> 	convert a existing source on.


I wish I could, the bind that they are running is the only one I could  
find to get to work with DLZ, and it was core dumping all over the  
place.  I barely know linux, and would rather not touch it. If it is  
possible to just build dig on rhel, I could go that route.

Though I am not understanding the versions, you were using 9.3.6 and I  
am using
DiG 9.6.0-P1-RedHat-9.6.0-2.P1

Since I am more current than you, I would estimate that the one bug is  
fixed if it is in your version, of course, that is not the case:
dig customtruckgraphics.us NS +trace -4 or -6 @4.2.2.1 +short
dig: can't find IPv6 networking.

Is this bug is a regression?

I am giving it a go to build it on RHEL now, and just pull dig out.   
Thanks for any other help.

-- 
Scott * If you contact me off list replace talklists@ with scott@ *