.Info Domain Not Resolving
dbotham at edeltacom.com
dbotham at edeltacom.com
Tue May 14 16:30:05 UTC 2002
Mark, Looks like Nominimum has dropped your delegation:
[root at ns3 root]# dig
; <<>> DiG 8.3 <<>>
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4
;; flags: qr rd ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 13
;; QUERY SECTION:
;; ., type = NS, class = IN
;; ANSWER SECTION:
. 5d22h50m17s IN NS H.ROOT-SERVERS.NET.
. 5d22h50m17s IN NS C.ROOT-SERVERS.NET.
. 5d22h50m17s IN NS G.ROOT-SERVERS.NET.
. 5d22h50m17s IN NS F.ROOT-SERVERS.NET.
. 5d22h50m17s IN NS B.ROOT-SERVERS.NET.
. 5d22h50m17s IN NS J.ROOT-SERVERS.NET.
. 5d22h50m17s IN NS K.ROOT-SERVERS.NET.
. 5d22h50m17s IN NS L.ROOT-SERVERS.NET.
. 5d22h50m17s IN NS M.ROOT-SERVERS.NET.
. 5d22h50m17s IN NS I.ROOT-SERVERS.NET.
. 5d22h50m17s IN NS E.ROOT-SERVERS.NET.
. 5d22h50m17s IN NS D.ROOT-SERVERS.NET.
. 5d22h50m17s IN NS A.ROOT-SERVERS.NET.
;; ADDITIONAL SECTION:
H.ROOT-SERVERS.NET. 6d22h50m17s IN A 128.63.2.53
C.ROOT-SERVERS.NET. 6d22h50m17s IN A 192.33.4.12
G.ROOT-SERVERS.NET. 6d22h50m17s IN A 192.112.36.4
F.ROOT-SERVERS.NET. 6d22h50m17s IN A 192.5.5.241
B.ROOT-SERVERS.NET. 6d22h50m17s IN A 128.9.0.107
J.ROOT-SERVERS.NET. 6d22h50m17s IN A 198.41.0.10
K.ROOT-SERVERS.NET. 6d22h50m17s IN A 193.0.14.129
L.ROOT-SERVERS.NET. 6d22h50m17s IN A 198.32.64.12
M.ROOT-SERVERS.NET. 6d22h50m17s IN A 202.12.27.33
I.ROOT-SERVERS.NET. 6d22h50m17s IN A 192.36.148.17
E.ROOT-SERVERS.NET. 6d22h50m17s IN A 192.203.230.10
D.ROOT-SERVERS.NET. 6d22h50m17s IN A 128.8.10.90
A.ROOT-SERVERS.NET. 6d22h50m17s IN A 198.41.0.4
;; Total query time: 2 msec
;; FROM: ns3 to SERVER: default -- 216.248.176.20
;; WHEN: Tue May 14 12:20:12 2002
;; MSG SIZE sent: 17 rcvd: 436
[root at ns3 root]# dig ns opnet.info @C.ROOT-SERVERS.NET
; <<>> DiG 8.3 <<>> ns opnet.info @C.ROOT-SERVERS.NET
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2
;; QUERY SECTION:
;; opnet.info, type = NS, class = IN
;; AUTHORITY SECTION:
info. 2D IN NS TLD2.NOMINUM.COM.
info. 2D IN NS TLD1.NOMINUM.COM.
;; ADDITIONAL SECTION:
TLD1.NOMINUM.COM. 2D IN A 198.133.199.100
TLD2.NOMINUM.COM. 2D IN A 192.100.59.100
;; Total query time: 5473 msec
;; FROM: ns3 to SERVER: C.ROOT-SERVERS.NET 192.33.4.12
;; WHEN: Tue May 14 12:20:31 2002
;; MSG SIZE sent: 28 rcvd: 109
[root at ns3 root]# dig ns opnet.info @TLD1.NOMINUM.COM
; <<>> DiG 8.3 <<>> ns opnet.info @TLD1.NOMINUM.COM
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 6
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUERY SECTION:
;; opnet.info, type = NS, class = IN
;; AUTHORITY SECTION:
info. 1H IN SOA primary-update.dns.nominum.com.
hostmaster.nominum.com. (
100048495 ; serial
1H ; refresh
30M ; retry
1W ; expiry
1H ) ; minimum
;; Total query time: 50 msec
;; FROM: ns3 to SERVER: TLD1.NOMINUM.COM 198.133.199.100
;; WHEN: Tue May 14 12:20:53 2002
;; MSG SIZE sent: 28 rcvd: 105
|---------+---------------------------->
| | mbaldwin at nc.opnet|
| | .com (Mark |
| | Baldwin) |
| | Sent by: |
| | bind-users-bounce|
| | @isc.org |
| | |
| | |
| | 05/14/2002 10:51 |
| | AM |
| | |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
| |
| To: comp-protocols-dns-bind at isc.org |
| cc: |
| Subject: .Info Domain Not Resolving |
>------------------------------------------------------------------------------------------------------------------------------|
We recently setup a .info domain for our company and I while my name
servers seem to be working properly, no other name servers seem to be
able to resolve it. The domain in question is opnet.info and I have
one A record defined for www.opnet.info. Whois output for this domain
correctly lists my name servers (nsatt.opnet.com and nsba.opnet.com).
However, they do not appear to get queried whenever anyone tries to
resolve www.opnet.info. In fact, dig gives the following:
dig @uni10ns.unity.ncsu.edu www.opnet.info.
; <<>> DiG 2.0 <<>> @uni10ns.unity.ncsu.edu www.opnet.info.
;; ->>HEADER<<- opcode: QUERY , status: NXDOMAIN, id: 10
;; flags: qr rd ; Ques: 1, Ans: 0, Auth: 1, Addit: 0
;; QUESTIONS:
;; www.opnet.info, type = A, class = IN
;; AUTHORITY RECORDS:
info. 2017 SOA primary-update.dns.nominum.com.
hostmaster.nominum.com. (
100048473 ;serial
3600 ;refresh
1800 ;retry
604800 ;expire
3600 ) ;minim
;; Sent 1 pkts, answer found in time: 19 msec
;; FROM: mlclient10 to SERVER: uni10ns.unity.ncsu.edu 152.1.1.208
;; WHEN: Tue May 14 10:44:07 2002
;; MSG SIZE sent: 32 rcvd: 109
and nslookup shows:
> www.opnet.info
Server: J.ROOT-SERVERS.NET
Address: 198.41.0.10
Name: www.opnet.info
Served by:
- TLD1.NOMINUM.COM
198.133.199.100
info
- TLD2.NOMINUM.COM
192.100.59.100
info
What does nominum.com have to do with this? They obviously don't know
anything about this domain.
Thanks, Mark...
More information about the bind-users
mailing list