In article <AJL0b.10041$(E-Mail Removed) m>,
(E-Mail Removed) wrote:
> I'm running a web/email server on my home dsl line. Every once in awhile,
> ameritech changes the IP, and some of their blocks of IP addresses don't have
> working reverse dns, which then makes some other ISPs (like roadrunner and aol)
> reject mail from my server. So then I have to kill adsl and restart to get
> another IP. A real PITA, but I can't afford to pay for a business dsl line with
> a static IP.
If COVAD has equipment in your CO you can get 128up/608down (max) with static
IP for a bit under $70/month from Speakeasy. That may still may not be
cheap enough for you, but should be better than Amertitech's business rates.
> So, I've tried to figure out a way with dig or nslookup to see if the
> reverse dns is working with the new IP, but can't get it. My only other
> recourse is to send mail to someone at a new.rr.com address and see if it
> bounces, which is a drag, not to mention annoying to them.
> There must be some better way to do this.
Some versions of nslookup recognize an IP address when used on a command
line and will do a PTR lookup automagically. Otherwise you can rewrite
your current IP address with a script to the appropiate PTR record
and then specifically do a PTR lookup.
1.2.3.4 -> 4.3.2.1.in-addr.arpa
Similar Threads
Linear Mode
