completing reverse DNS

[AndrewKT]

When I traceroute against my IP from the outside, I get:
C:\Documents and Settings\athompson>tracert 72.9.242.XXX

Tracing route to vps.mydomain.com [72.9.242.XXX]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.31
2 16 ms 15 ms 15 ms nc-69-68-178-129.sta.sprint-hsd.net [69.68.178.129]
3 16 ms 15 ms 15 ms crncrcmt03 [65.40.111.249]
4 16 ms 15 ms 16 ms 205.244.203.45
5 16 ms 15 ms 15 ms 205.244.112.85
6 36 ms 35 ms 35 ms sl-gw11-atl-0-3.sprintlink.net [144.232.211.217]
7 38 ms 36 ms 35 ms sl-bb24-atl-5-0.sprintlink.net [144.232.12.89]
8 35 ms 36 ms 36 ms sl-bb21-atl-4-0.sprintlink.net [144.232.12.29]
9 37 ms 37 ms 36 ms 144.232.8.182
10 * * 40 ms dcr2-so-2-2-0.Atlanta.savvis.net [208.172.67.73]
11 40 ms 41 ms 42 ms bpr2-so-0-0-0.AtlantaPaix.savvis.net [208.172.75.238]
12 39 ms 36 ms 44 ms 208.173.60.218
13 37 ms 37 ms 38 ms 209.51.131.25
14 38 ms 37 ms 40 ms 65.254.48.2
15 36 ms 35 ms 35 ms 72.9.242.254
16 39 ms 34 ms 34 ms vps.mydomain.com [72.9.242.XXX]

Trace complete.

C:\Documents and Settings\athompson>

But a nslookup using my IP gives this message(on WinXP):
C:\Documents and Settings\athompson>nslookup clientdomain.com 72.9.242.XXX
*** Can't find server name for address 72.9.242.XXX: No information
Server: UnKnown
Address: 72.9.242.XXX

Name: rhino-group.net
Address: 209.123.241.250

Do I need to configure something in my bind/named to have reverse DNS work completely?

[tiffman]

Your command tries to look up "clientdomain.com" on nameserver "72.9.242.XXX".

Presuming you're trying to test reverse DNS, you probably want to just run "nslookup 72.9.242.XXX" to see if it will resolve from your default server, or run "nslookup 72.9.242.XXX clientdomain.com" if you're actually trying to use the clientdomain.com nameserver.

[AndrewKT]

I used nslookup rhino-group.net 72.9.242.XXX because that looks up rhino-group.net using the nameserver specified. Which is what I wanted to do.
The reason I posted is, if I just specify the domain name, I get:
C:\Documents and Settings\athompson>nslookup rhino-group.net
Server: itdc01.ournetwork.com
Address: 192.168.0.2

Non-authoritative answer:
Name: rhino-group.net
Address: 209.123.241.250

See how the nameserver was identified by name, unlike my IP here:
C:\Documents and Settings\athompson>nslookup rhino-group.net 72.9.242.XXX
*** Can't find server name for address 72.9.242.XXX: No information
Server: UnKnown
Address: 72.9.242.XXX

Name: rhino-group.net
Address: 209.123.241.250

[tiffman]

Sorry, misunderstood the problem.

Do you have recursion turned off on your server? If so, the reverse lookup will fail because you're not authoritative for your reverse domain. I don't believe it's really a problem, because a reverse lookup of your ip address will go to the authoritative server (probably ns1.tektonic.net).

If you want to make sure reverse dns is working, you should be able to just "nslookup 72.9.242.XXX" and make sure it resolves through normal recursive methods.

[mroch]

Your reverse DNS is not set up properly:

bash-2.05b$ dig rhino-group.net

; <<>> DiG 9.2.3 <<>> rhino-group.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59902
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;rhino-group.net. IN A

;; ANSWER SECTION:
rhino-group.net. 86400 IN A 209.123.241.250

;; AUTHORITY SECTION:
rhino-group.net. 86400 IN NS dns19.register.com.
rhino-group.net. 86400 IN NS dns20.register.com.

;; Query time: 61 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Tue Apr 12 21:40:34 2005
;; MSG SIZE rcvd: 101

bash-2.05b$ dig -x 209.123.241.250

; <<>> DiG 9.2.3 <<>> -x 209.123.241.250
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 38233
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;250.241.123.209.in-addr.arpa. IN PTR

;; AUTHORITY SECTION:
241.123.209.in-addr.arpa. 86400 IN SOA ns.effectdns.com. root.ns.effectdns.com. 1997023703 28800 14400 3600000 86400

;; Query time: 47 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Tue Apr 12 21:40:47 2005
;; MSG SIZE rcvd: 103

bash-2.05b$

The important part:

;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 38233
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;250.241.123.209.in-addr.arpa. IN PTR

If this was working properly, you would see "IN PTR rhino-group.net"

Since TekTonic/Unixshell controls the IPs, you'll have to have them set up the PTR pointing from your IP back to your domain. Reverse DNS hasn't been officially set up on unixshell yet (search this forum), but it's been said that TekTonic will set it up for you if you email support@tektonic.net.

HTH,

Marshall Roch

[tiffman]

I could just be confused (again), but it looks as though 209.123.241.250 is a nac.net ip (though rwhois.nac.net isn't responding to give me further information). I think he really wants reverse dns on 72.9.242.XXX, which is definitely a tektonic address, and is just using rhino-group.net as a test. Not knowing what the XXX is, I can't say for sure if reverse dns for that IP is working, but you're right that if he hasn't requsted it be set up, it won't be working yet.

Again, I could be confused; if so, my apologies.

[AndrewKT]

[QUOTE=tiffman]I could just be confused (again), but it looks as though 209.123.241.250 is a nac.net ip (though rwhois.nac.net isn't responding to give me further information). I think he really wants reverse dns on 72.9.242.XXX, which is definitely a tektonic address, and is just using rhino-group.net as a test.[/quote]
Nope, you're exactly right. The 209... IP is the current primary nameserver for that domain. When I'm happy with the configuration of this box, I'll change the domains.

[QUOTE=tiffman]Not knowing what the XXX is, I can't say for sure if reverse dns for that IP is working, but you're right that if he hasn't requsted it be set up, it won't be working yet.[/QUOTE]
I have requested the reverse DNS be set up on both my IPs, and like I posted originally, traceroute(and dnsstuff.com) show that it is configured.

[AndrewKT]

sorry... seem to be having some network connectivity issues... (The page was not returning.)