I can't get answer for my domain.

[Yoshikazu]

I can't get answer for my domain by google dns. Of course I can get
correct anwer by ISP dns server.
Why google dns think primary name server of my domain is
ns1.peer1.net ? My rental server is hosted in
peer1 related company.

== by google dns ===============================
> church.ne.jp.
Server: google-public-dns-a.google.com
Address: 8.8.8.8

------------
SendRequest(), len 30
HEADER:
opcode = QUERY, id = 39, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0,
additional = 0

QUESTIONS:
church.ne.jp, type = A, class = IN

------------
------------
Got answer (97 bytes):
HEADER:
opcode = QUERY, id = 39, rcode = NOERROR
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 1,
additional = 0

QUESTIONS:
church.ne.jp, type = A, class = IN
AUTHORITY RECORDS:
-> church.ne.jp
type = SOA, class = IN, dlen = 55
ttl = 1173 (19 mins 33 secs)
primary name server = ns1.peer1.net
responsible mail addr = hostm...@church.ne.jp
serial = 1
refresh = 16384 (4 hours 33 mins 4 secs)
retry = 2048 (34 mins 8 secs)
expire = 1048576 (12 days 3 hours 16 mins 16 secs)
default TTL = 2560 (42 mins 40 secs)

------------
------------
SendRequest(), len 30
HEADER:
opcode = QUERY, id = 40, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0,
additional = 0

QUESTIONS:
church.ne.jp, type = AAAA, class = IN

------------
------------
Got answer (97 bytes):
HEADER:
opcode = QUERY, id = 40, rcode = NOERROR
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 1,
additional = 0

QUESTIONS:
church.ne.jp, type = AAAA, class = IN
AUTHORITY RECORDS:
-> church.ne.jp
type = SOA, class = IN, dlen = 55
ttl = 2157 (35 mins 57 secs)
primary name server = ns1.peer1.net
responsible mail addr = hostm...@church.ne.jp
serial = 1
refresh = 16384 (4 hours 33 mins 4 secs)
retry = 2048 (34 mins 8 secs)
expire = 1048576 (12 days 3 hours 16 mins 16 secs)
default TTL = 2560 (42 mins 40 secs)

------------
Name: church.ne.jp

== by ISP dns ===============================
> church.ne.jp.
Server: UnKnown
Address: 218.251.89.134

------------
SendRequest(), len 30
HEADER:
opcode = QUERY, id = 4, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0,
additional = 0

QUESTIONS:
church.ne.jp, type = A, class = IN

------------
------------
Got answer (141 bytes):
HEADER:
opcode = QUERY, id = 4, rcode = NOERROR
header flags: response, want recursion, recursion avail.
questions = 1, answers = 1, authority records = 3,
additional = 2

QUESTIONS:
church.ne.jp, type = A, class = IN
ANSWERS:
-> church.ne.jp
type = A, class = IN, dlen = 4
internet address = 64.34.161.161
ttl = 1042 (17 mins 22 secs)
AUTHORITY RECORDS:
-> church.ne.jp
type = NS, class = IN, dlen = 16
nameserver = ns2.geodns.net
ttl = 1042 (17 mins 22 secs)
-> church.ne.jp
type = NS, class = IN, dlen = 5
nameserver = ns.church.ne.jp
ttl = 1042 (17 mins 22 secs)
-> church.ne.jp
type = NS, class = IN, dlen = 6
nameserver = ns1.geodns.net
ttl = 1042 (17 mins 22 secs)
ADDITIONAL RECORDS:
-> ns1.geodns.net
type = A, class = IN, dlen = 4
internet address = 69.28.203.75
ttl = 30023 (8 hours 20 mins 23 secs)
-> ns2.geodns.net
type = A, class = IN, dlen = 4
internet address = 69.90.13.105
ttl = 3506 (58 mins 26 secs)

------------
Non-authoritative answer:
------------
SendRequest(), len 30
HEADER:
opcode = QUERY, id = 5, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0,
additional = 0

QUESTIONS:
church.ne.jp, type = AAAA, class = IN

------------
------------
Got answer (74 bytes):
HEADER:
opcode = QUERY, id = 5, rcode = NOERROR
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 1,
additional = 0

QUESTIONS:
church.ne.jp, type = AAAA, class = IN
AUTHORITY RECORDS:
-> church.ne.jp
type = SOA, class = IN, dlen = 32
ttl = 3600 (1 hour)
primary name server = ns.church.ne.jp
responsible mail addr = root.church.ne.jp
serial = 2007010901
refresh = 3600 (1 hour)
retry = 900 (15 mins)
expire = 604800 (7 days)
default TTL = 3600 (1 hour)

------------
Name: church.ne.jp
Address: 64.34.161.161
=================================================

[Alex Nizhner]

We get these NODATA responses from {ns1,ns2}.geodns.net, to which .jp nameservers delegate your zone.  I.e., when we talk to .jp to resolve church.ne.jp, we get these referrals:

[finwe]% dig +norec @a.dns.jp church.ne.jp

; <<>> DiG 9.4.2-P2.1 <<>> +norec @a.dns.jp church.ne.jp
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63372
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 1

;; QUESTION SECTION:
;church.ne.jp.                  IN      A

;; AUTHORITY SECTION:
church.ne.jp.           86400   IN      NS      ns1.geodns.net.
church.ne.jp.           86400   IN      NS      ns.church.ne.jp.
church.ne.jp.           86400   IN      NS      ns2.geodns.net.

;; ADDITIONAL SECTION:
ns.church.ne.jp.        86400   IN      A       64.34.161.161

Whereas ns.church.ne.jp gives the answer you expect, both ns1.geodns.net and ns2.geodns.net give the empty (final and cacheable) response you've been seeing:

[finwe]% dig +norec @ns2.geodns.net church.ne.jp

; <<>> DiG 9.4.2-P2.1 <<>> +norec @ns2.geodns.net church.ne.jp
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12355
;; flags: qr aa; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;church.ne.jp.                  IN      A

;; AUTHORITY SECTION:
church.ne.jp.           2560    IN      SOA     ns1.peer1.net. hostmaster\@church.ne.jp. 1 16384 2048 1048576 2560

Sometimes we talk to ns.church.ne.jp to get the final answer (and when that happens, we do cache and return your IP until we refresh that record); other times we talk to the geodns nameservers.  This isn't specific to Google Public DNS.  AFAIK you need to talk to your hoster in order to fix this and get things updated on their end.

Alex

--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to
public-dns-disc...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================

[Yoshikazu]

Thanks to your advice. The problem was resolved. Changing Secondary
DNS's IP address provided by hoster caused this problem.