6

Say I have two domains, foo.com and bar.com, and I initially have an A record for:

www.foo.com → 1.2.3.4

I then decide I want www.bar.com to resolve to this IP, so I delete www.foo.com's A record, and add an A record for bar:

www.bar.com → 1.2.3.4

This looks fine via dig. However, when I do a reverse DNS lookup on that IP, I still see www.foo.com.

Any idea how long reverse DNS takes to propagate?

slhck
  • 235,242
Joe batista
  • 63
  • 1
  • 1
  • 3

4 Answers4

4

This is nothing to do with the mythical idea of "DNS propagation". As Zoredache has quite rightly said, this is an erroneous concept (based, if it is based upon anything at all, upon the long-since-altered behaviour of some domain name registries). The DNS does not work that way. Your data were available from your content DNS servers to the world as soon as you entered them.

This is everything to do with the fact that you have name→address conflated with address→name. You've entered a name→address mapping but you've expected that to magically affect the lookup of an address→name mapping. You're spending days at a time waiting for things to "propagate" when you haven't in fact enacted any changes to the relevant data in the first place.

If you want to look up the new name→address mapping that you've just entered, look up the domain name. If you want to change what an address→name lookup returns, change the address→name mapping data in your database. Address→name mappings do not involve either A or AAAA resource record sets.

Mark C
  • 103
JdeBP
  • 27,556
  • 1
  • 77
  • 106
2

There is a propagation delay involved. When you change your "delegation" at your RIR for your reverse DNS to new servers, there is usually 24 hours for those reverse DNS name server changes to occur. However some people have waited longer......ARIN says that it usually takes 24 hours.

greggcwa
  • 21
  • 1
0

I think reverse DNS lookup is not based on A records but on PTR records, so if it doesn't change, it is maybe not because of propagation delays.

0

Propagation depends on the TTL set for the DNS hosts involved and may also be hindered by local caching on your client. Also, depending on how you're making your changes, you may have to independently enter the reverse entry.

OldWolf
  • 2,493