From owner-freebsd-isp@FreeBSD.ORG Sun May 18 13:58:40 2003 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6824637B401 for ; Sun, 18 May 2003 13:58:40 -0700 (PDT) Received: from coleman.org (adsl-64-175-70-233.dsl.pltn13.pacbell.net [64.175.70.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8492E43F3F for ; Sun, 18 May 2003 13:58:39 -0700 (PDT) (envelope-from don@coleman.org) Received: from coleman.org (kestrel.coleman.org [10.0.0.11]) by eozoon.coleman.org (8.12.8p1/8.12.8) with ESMTP id h4GKCKlQ022573 for ; Fri, 16 May 2003 13:12:20 -0700 (PDT) (envelope-from don@coleman.org) Message-Id: <200305162012.h4GKCKlQ022573@eozoon.coleman.org> X-Mailer: exmh version 2.6.2 03/21/2003 with nmh-1.0.4 To: freebsd-isp@freebsd.org Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_-11980032640" Date: Fri, 16 May 2003 13:11:56 -0700 From: "Donald C. Coleman" X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: SBC dsl/PPPeE w/dynamic ip address & bad DNS records X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: don@coleman.org List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 May 2003 20:58:40 -0000 This is a multipart MIME message. --==_Exmh_-11980032640 Content-Type: text/plain; charset=us-ascii So I ran into a problem where the dynamic IP address I was handed by SBC had a DNS ptr record which referred to an A record which didn't exist (and the ptr record also had an error as it didn't follow the naming strategy obviously intended). ie: 216.71.175.64.in-addr.arpa -> adsl-64-174-71-216.dsl.pltn13.pacbell.net. ^- the problem rather then adsl-64-175-71-216.dsl.pltn13.pacbell.net. ^- the correct value and no A record exists for adsl-64-174-71-216.dsl.pltn13.pacbell.net. I won't bore you with the details of SBC's rudeness and lack of interest in fixing the problem -- basically, if you can browse, they think that is enough. The fact that some web-sites/internet services check for valid DNS records as part of their security policies, doesn't matter, let alone their violation of internet conventions/RFCs. Luckly, only a small number of their dynamic IP addresses have this problem. Below is my solution. I basically check at "link up" time that the DNS records are valid, and if not, signal ppp to drop the connection, and since my ppp is in "ddial" mode, it reestablishes the connection, and we check again, and, etc... I've never seen it have to do more then one retry. So folks won't have to re-invent the wheel, I've attached what I've done. I've also included my hooks for updating my "dynamic" domain name ip address. Delete/replace this with want you need. Put all these files in /etc/ppp. chmod a+x both the .sh files change the "sbc_yahoo:" line in the ppp.linkup file with your link name. change/delete dnsupdate.sh to fit your domain name update scheme, if you have one. --==_Exmh_-11980032640 Content-Type: text/plain ; name="ppp.linkup"; charset=us-ascii Content-Description: ppp.linkup Content-Disposition: attachment; filename="ppp.linkup" sbc_yahoo: !bg sh -c "/etc/ppp/ppp.linkup.sh MYADDR PROCESSID 2>&1 | logger -t ppp -p 'daemon.notice'" --==_Exmh_-11980032640--