North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Need help explaining in-addr.arpa to Limelight

  • From: Tuc at T-B-O-H.NET
  • Date: Tue Oct 24 09:44:51 2006

Hi all,

	(And especially to those emailing privately, Joe Abley
and Adam Rothschild... I never disappeared... ;) )

	Yes, I've misspoke. Bad on me #1. You can subdomain
IN-ADDR.ARPA. I understand that if you do more than just simply
put NS records in, it can be done. 

	The issue still stands though, that according to my
latest dig +trace of it, I see :

185.28.69.in-addr.arpa. 86400   IN      NS      dns.iad.llns.net.
185.28.69.in-addr.arpa. 86400   IN      NS      dns.lax.llns.net.
185.28.69.in-addr.arpa. 86400   IN      NS      dns.lga.llns.net.
185.28.69.in-addr.arpa. 86400   IN      NS      dns.sjc.llns.net.
;; Received 138 bytes from 192.35.51.32#53(dill.ARIN.NET) in 2880 ms

185.28.69.in-addr.arpa. 7200    IN      SOA     ns8.zoneedit.com. soacontact.zoneedit.com. 1115928761 14400 7200 950400 7200
;; Received 105 bytes from 69.28.156.99#53(dns.iad.llns.net) in 970 ms

	Which still is wrong I believe. If nothing else, it
should point to the ns13 and ns8 servers at zoneedit.com .

	Jeroen said he saw :

;; ANSWER SECTION:
185.28.69.in-addr.arpa. 7200    IN      NS      ns13.zoneedit.com.
185.28.69.in-addr.arpa. 7200    IN      NS      ns8.zoneedit.com.

	from a dig, but I'm not sure how. And yes, I'm using zoneedit
for diversity for this reverse.

	As for my bad #2, I incorrectly used SWIP. I guess I should
have said that if you do :

whois -h rwhois.llnw.net -p 4321 69.28.185.1

	It shows up as that I am the contact for that.

	Howerver, it still remains that after telling them twice
EXACTLY what to do, it seems like they are still wrong. I
would think I'd need to see something like what WCG did for
me for another subnet :

164.193.64.in-addr.arpa. 86400  IN      NS      ns8.zoneedit.com.
164.193.64.in-addr.arpa. 86400  IN      NS      ns13.zoneedit.com.
;; Received 126 bytes from 64.200.255.12#53(tuldns1.wcg.net) in 1030 ms


	Am I still wrong, or are they?

			Thanks, Tuc