On Mon, 25 Jan 1999, Glynn Clements wrote:
>
> Scott Spence wrote:
>
> > > > Is anyone out there using the free domain name services of granitecanyon?
> > > > What experiences have people had?
> > >
> > > > At the moment our server does not seem to be registered (using nslookup
> > > > and their server as the default I get a non-existent host/domain) But I
> > > > get the same problem with netscape.com, only local granitecanyon.com
> > > > domain names seem to register, shoud this be or is there something wrong?
> > >
> > > This is correct. The nameservers for granitecanyon.com won't answer
maybe, maybe not... depends on what questions he is asking the
granitecanyon.com servers...
> > > recursive queries; they only provide information about the
> > > granitecanyon.com domain.
> > >
> > > You should use your ISP's nameserver(s) (and/or your own) for
> > > recursive queries.
> >
> > If this is the case then how do I check recursive queries for those hosts
> > on the otherside of the world? I recently had someone getting bounced mail
> > on their hotmail account due to 'non-existant domain' errors for our
> > domain (that does exist!).
Is granitecanyon.com supposed to be the DNS server for your domain? If so,
it SHOULD answer questions about your domain, otherwise, it will just
refer you to the root dns servers ... I prefer using "dig" to "nslookup"
as you actually get to see the information returned...
first... let's check the NS servers for your domain (hoping I got
the domain right):
[americium /home/hodge/tbrown]# dig noggon.co.nz ns
; <<>> DiG 8.1 <<>> noggon.co.nz ns
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
;; QUERY SECTION:
;; noggon.co.nz, type = NS, class = IN
;; ANSWER SECTION:
noggon.co.nz. 1D IN NS ns1.waikato.ac.nz.
noggon.co.nz. 1D IN NS noggon.co.nz.
OK... so granitecanyon isn't supposed to know anything special
about your domain... and:
[americium /home/hodge/tbrown]# dig noggon.co.nz @NS1.GRANITECANYON.COM
; <<>> DiG 8.1 <<>> noggon.co.nz @NS1.GRANITECANYON.COM
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0,
ADDITIONAL: 0
;; QUERY SECTION:
;; noggon.co.nz, type = A, class = IN
;; Total query time: 252 msec
Hhmm... that isn't what I expected... I'd call that an incorrect
answer... it's like they haven't loaded the root-server cache
file into that server, so it THINKS it is doing a recursive
lookup, but isn't, because it doesn't know that the rest of the
world exists...
I'd have expected something like:
[americium /home/hodge/tbrown]# dig noggon.co.nz @ITCHY.MINDSPRING.NET
; <<>> DiG 8.1 <<>> noggon.co.nz @ITCHY.MINDSPRING.NET
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 13
;; QUERY SECTION:
;; noggon.co.nz, type = A, class = IN
;; AUTHORITY SECTION:
. 2d14h53m26s IN NS F.ROOT-SERVERS.NET.
. 2d14h53m26s IN NS G.ROOT-SERVERS.NET.
. 2d14h53m26s IN NS J.ROOT-SERVERS.NET.
. 2d14h53m26s IN NS K.ROOT-SERVERS.NET.
. 2d14h53m26s IN NS L.ROOT-SERVERS.NET.
. 2d14h53m26s IN NS M.ROOT-SERVERS.NET.
. 2d14h53m26s IN NS A.ROOT-SERVERS.NET.
. 2d14h53m26s IN NS H.ROOT-SERVERS.NET.
. 2d14h53m26s IN NS B.ROOT-SERVERS.NET.
. 2d14h53m26s IN NS C.ROOT-SERVERS.NET.
. 2d14h53m26s IN NS D.ROOT-SERVERS.NET.
. 2d14h53m26s IN NS E.ROOT-SERVERS.NET.
. 2d14h53m26s IN NS I.ROOT-SERVERS.NET.
;; ADDITIONAL SECTION:
F.ROOT-SERVERS.NET. 6d1h48m23s IN A 192.5.5.241
G.ROOT-SERVERS.NET. 6d1h48m23s IN A 192.112.36.4
J.ROOT-SERVERS.NET. 3d14h53m26s IN A 198.41.0.10
K.ROOT-SERVERS.NET. 3d14h53m26s IN A 193.0.14.129
L.ROOT-SERVERS.NET. 3d14h53m26s IN A 198.32.64.12
M.ROOT-SERVERS.NET. 3d14h53m26s IN A 202.12.27.33
A.ROOT-SERVERS.NET. 6d1h48m23s IN A 198.41.0.4
H.ROOT-SERVERS.NET. 6d1h48m23s IN A 128.63.2.53
B.ROOT-SERVERS.NET. 6d1h48m23s IN A 128.9.0.107
C.ROOT-SERVERS.NET. 6d1h48m23s IN A 192.33.4.12
D.ROOT-SERVERS.NET. 6d1h48m23s IN A 128.8.10.90
E.ROOT-SERVERS.NET. 6d1h48m23s IN A 192.203.230.10
I.ROOT-SERVERS.NET. 6d1h48m23s IN A 192.36.148.17
;; Total query time: 88 msec
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
