Try again... using "dig"

greg@maxime:~ [1] $ dig blog.cooklikeyourgrandmother.com @yns1.yahoo.com ; <<>> DiG 9.6.1-P1 <<>> blog.cooklikeyourgrandmother.com @yns1.yahoo.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 18670 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;blog.cooklikeyourgrandmother.com. IN A ;; Query time: 311 msec ;; SERVER: 98.136.43.32#53(98.136.43.32) ;; WHEN: Tue Sep 22 16:28:16 2009 ;; MSG SIZE rcvd: 50 greg@maxime:~ [0] $ dig blog.cooklikeyourgrandmother.com @uno.gregfolkert.net ; <<>> DiG 9.6.1-P1 <<>> blog.cooklikeyourgrandmother.com @uno.gregfolkert.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19891 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 6, ADDITIONAL: 0 ;; QUESTION SECTION: ;blog.cooklikeyourgrandmother.com. IN A ;; ANSWER SECTION: blog.cooklikeyourgrandmother.com. 38400 IN CNAME ghs.google.com. ghs.google.com. 580300 IN CNAME ghs.l.google.com. ghs.l.google.com. 33 IN A 74.125.93.121 ;; AUTHORITY SECTION: l.google.com. 61886 IN NS g.l.google.com. l.google.com. 61886 IN NS d.l.google.com. l.google.com. 61886 IN NS f.l.google.com. l.google.com. 61886 IN NS e.l.google.com. l.google.com. 61886 IN NS b.l.google.com. l.google.com. 61886 IN NS a.l.google.com. ;; Query time: 53 msec ;; SERVER: 208.64.37.170#53(208.64.37.170) ;; WHEN: Tue Sep 22 16:29:11 2009 ;; MSG SIZE rcvd: 207 greg@maxime:~ [0] $ dig blog.cooklikeyourgrandmother.com @nrcns.westlandrdc.mi.michigan.comcast.net ; <<>> DiG 9.6.1-P1 <<>> blog.cooklikeyourgrandmother.com @nrcns.westlandrdc.mi.michigan.comcast.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9695 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;blog.cooklikeyourgrandmother.com. IN A ;; ANSWER SECTION: blog.cooklikeyourgrandmother.com. 2185 IN CNAME ghs.google.com. ghs.google.com. 602766 IN CNAME ghs.l.google.com. ghs.l.google.com. 246 IN A 74.125.113.121 ;; Query time: 16 msec ;; SERVER: 68.87.77.130#53(68.87.77.130) ;; WHEN: Tue Sep 22 16:40:02 2009 ;; MSG SIZE rcvd: 111

Post #314,438 by folkert 9/22/09 4:40:55 PM Reply	Try again... using "dig" greg@maxime:~ [1] $ dig blog.cooklikeyourgrandmother.com @yns1.yahoo.com ; <<>> DiG 9.6.1-P1 <<>> blog.cooklikeyourgrandmother.com @yns1.yahoo.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 18670 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;blog.cooklikeyourgrandmother.com. IN A ;; Query time: 311 msec ;; SERVER: 98.136.43.32#53(98.136.43.32) ;; WHEN: Tue Sep 22 16:28:16 2009 ;; MSG SIZE rcvd: 50 greg@maxime:~ [0] $ dig blog.cooklikeyourgrandmother.com @uno.gregfolkert.net ; <<>> DiG 9.6.1-P1 <<>> blog.cooklikeyourgrandmother.com @uno.gregfolkert.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19891 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 6, ADDITIONAL: 0 ;; QUESTION SECTION: ;blog.cooklikeyourgrandmother.com. IN A ;; ANSWER SECTION: blog.cooklikeyourgrandmother.com. 38400 IN CNAME ghs.google.com. ghs.google.com. 580300 IN CNAME ghs.l.google.com. ghs.l.google.com. 33 IN A 74.125.93.121 ;; AUTHORITY SECTION: l.google.com. 61886 IN NS g.l.google.com. l.google.com. 61886 IN NS d.l.google.com. l.google.com. 61886 IN NS f.l.google.com. l.google.com. 61886 IN NS e.l.google.com. l.google.com. 61886 IN NS b.l.google.com. l.google.com. 61886 IN NS a.l.google.com. ;; Query time: 53 msec ;; SERVER: 208.64.37.170#53(208.64.37.170) ;; WHEN: Tue Sep 22 16:29:11 2009 ;; MSG SIZE rcvd: 207 greg@maxime:~ [0] $ dig blog.cooklikeyourgrandmother.com @nrcns.westlandrdc.mi.michigan.comcast.net ; <<>> DiG 9.6.1-P1 <<>> blog.cooklikeyourgrandmother.com @nrcns.westlandrdc.mi.michigan.comcast.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9695 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;blog.cooklikeyourgrandmother.com. IN A ;; ANSWER SECTION: blog.cooklikeyourgrandmother.com. 2185 IN CNAME ghs.google.com. ghs.google.com. 602766 IN CNAME ghs.l.google.com. ghs.l.google.com. 246 IN A 74.125.113.121 ;; Query time: 16 msec ;; SERVER: 68.87.77.130#53(68.87.77.130) ;; WHEN: Tue Sep 22 16:40:02 2009 ;; MSG SIZE rcvd: 111
Post #314,439 by drook 9/22/09 4:45:09 PM Reply	If I'm reading that right, Yahoo doesn't have me in DNS Am I reading that right? And should I be seeing it in there? -- Drew
Post #314,441 by folkert 9/22/09 5:08:25 PM Reply	DING DING DING! Give that man a Cupie Doll!
Post #314,443 by drook 9/22/09 5:21:37 PM Reply	No, looks like that's only the address for ones they host Tried looking up google.com on their servers and got nothing. That's not the DNS that their ISP clients use, they're the nameservers for domains they host. -- Drew
Post #314,442 by folkert 9/22/09 5:18:31 PM Reply	NO RECORDS what so ever in Yahoo yns1/2 has NO DNS records: blog, forum, wildcard, mx, www... nothing. DNS from yahoo provides support for ALL AT&T operations, including iPhone, Broadband (uVerse), Dialup, 3G/CDMA/4G wireless Internet and other things.
Post #314,440 by folkert 9/22/09 5:08:00 PM Reply	Re: Try again... using "dig" And even both yns1 and yns2 do not see it yet.

Welcome to IWETHEY!