| New IP, reverse DNS no longer worksI had an internet outage this morning and got a new IP in the 99.224.14.0/23 net block. However, reverse DNS on the new IP no longer returns anything but SERVFAIL:
# dig -x 99.224.14.185 | grep status
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 28177
This is annoying because remote services that do reverse lookups (like SMTP, IMAP, SSH servers, etc) are slower to respond to requests.
Reverse DNS on my old IP (in a different block) worked without issue, and returned an address like *.cpe.net.cable.rogers.com.
Will anyone at Rogers know what the hell I'm talking about if I call them, or should I just release the IP lease and get a new IP with a working reverse DNS? |
 HiVoltPremium
join:2000-12-28
Toronto, ON
kudos:18
 ·TekSavvy DSL
 ·TekSavvy Cable
| You can try changing the MAC Address of your WAN port in your router (if it has that option), reboot your modem then the router and maybe you'll get another IP that resolves.
Otherwise calling Rogers to ask to get it fixed will result in nothing but frustration on your part.
Or perhaps wait a few days until they update their rDNS...
--
F**K THE NHL. Go Blue Jays 2013!!!
|
