For reverse dns, do you or your ISP take care of reverse dns.
The book says your isp do the reverse dns.

Do you do anything on your part on the server? :cool:

It might say in the book that your ISP will do it but the truth is you really have to be the one to do it.

Actually, the ISP almost always does reverse. Usually the only upstream will delegate reverse DNS authority is if you've got a whole class C and request it.

You have to remember that I am talking about Canadian ISPs. They don't know half the stuff they should, and their knowledge is just a little beyond knowing how to turn on their PCs

Yep, usually its the ISP (or even their ISP) that sorts out the reverse DNS, whoever has authority on the IPs.

>Do you do anything on your part on the server?

Well not really it will work without any modification to the server configuration, however to be clean make sure the hostname resolves to the IP.

For example:
Panther.WebHostingTalk.com resolves to 209.249.55.203
The reverse DNS for 209.249.55.203 is Panther.WebHostingTalk.com

Just to be a perfectionist, as I presume you only want to do this for one domain per server then set the hostname of the machine the same as the hostname for the reverse DNS. Eg. panther.webhostingtalk.com or ntserver1.hostingcompany.com.

Originally posted by netsolutions
You have to remember that I am talking about Canadian ISPs. They don't know half the stuff they should, and their knowledge is just a little beyond knowing how to turn on their PCs

If they barely know how to turn on a PC, I doubt they'll know how to delegate reverse authority...

Can you guys do a traceroute on this and tell me what you think

64.71.148.130

traceroute to 64.71.148.130 (64.71.148.130), 30 hops max, 38 byte packets
1 64.124.182.main2.above.net (64.124.182.3) 1.058 ms 0.195 ms 0.649 ms
2 core1-main2colo78-oc48.sjc3.above.net (208.184.210.169) 0.715 ms 0.549 ms 0.848 ms
3 core1-sjc3-oc48.sjc2.above.net (208.185.175.157) 0.774 ms 0.409 ms 0.667 ms
4 core6-sjc2-oc48.sjc1.above.net (216.200.0.177) 0.847 ms 0.739 ms 0.392 ms
5 core2-sjc1-oc3.sjc6.above.net (207.126.96.106) 1.020 ms 1.262 ms 0.850 ms
6 100tx-f6-1.mae-west.he.net (207.126.96.98) 2.163 ms 2.037 ms 1.757 ms
7 gige-g0-0.gsr12008.fmt.he.net (216.218.130.6) 2.449 ms 2.866 ms 2.595 ms
8 64.71.148.130 (64.71.148.130) 3.313 ms 3.512 ms 4.493 ms

wow I guess

Hey, where is the "DNS Error"?

I used samspade.org, and it showed DNS Error.

:cool:

Originally posted by Asia
Hey, where is the "DNS Error"?

I used samspade.org, and it showed DNS Error.


I'm assuming it means it can't resolve the IP.

Server: ns1.planetz.net
Address: 208.237.120.200

*** No address (A) records available for 64.71.148.130

Whoever "owns" the IP address block from ARIN (in the US of A) can specify the server that should be authoritative for reverse DNS.

Then that server can of course delegate as much authority as wanted to what ever other server.

If you "own" the IP address space you should be able to do your own reverse DNS if you want. If not, then you have to convince the owner to give you the authority.

We have been unable to get the authority for the IP address space that we use, because we're borrowing it from our ISPs, and they're control freaks.

The IPs I have are from he.net.
They told me that they've completed the reverse dns.
When I tried to traceroute the IP it outputed DNS Enter.
I clicked on the DNS Error, and it showed that the IP does not have reverse dns. :rolleyes: