-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 09 February 2003 01:00 am, civileme wrote: > > It is being rejected because reverse lookup doesn't work. His ISP has the > dns misconfigured. > > Search results for: 64.72.132.17 > > > OrgName: One Call Communications > OrgID: OCCI > Address: 801 Congressional Blvd > City: Carmel > StateProv: IN > PostalCode: 46032 > Country: US > > NetRange: 64.72.128.0 - 64.72.143.255 > CIDR: 64.72.128.0/20 > NetName: OCC-2-NET > NetHandle: NET-64-72-128-0-1 > Parent: NET-64-0-0-0-0 > NetType: Direct Allocation > NameServer: NS1.ONECALL.NET > NameServer: NS2.ONECALL.NET > Comment: ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE > RegDate: 2002-01-30 > Updated: 2002-10-16 > > NOCHandle: TECHN2-ARIN > NOCName: Technical Contact > NOCPhone: +1-888-223-8633 > NOCEmail: [EMAIL PROTECTED] > > SInce they are direct allocation addresses, he may need to set up his own > reverse dns zone on his own machine to respond. > > [tester@ibm333 tester]$ host -a 64.72.132.17 > Trying "17.132.72.64.in-addr.arpa" > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19162 > ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 > > ;; QUESTION SECTION: > ;17.132.72.64.in-addr.arpa. IN PTR > > ;; ANSWER SECTION: > 17.132.72.64.in-addr.arpa. 172800 IN PTR > Hosting-132-17.PHPWebHosting.Com. > > ;; AUTHORITY SECTION: > 132.72.64.in-addr.arpa. 86400 IN NS NS1.ONECALL.NET. > 132.72.64.in-addr.arpa. 86400 IN NS NS2.ONECALL.NET. > > ;; ADDITIONAL SECTION: > NS1.ONECALL.NET. 42844 IN A 216.37.1.19 > NS2.ONECALL.NET. 42844 IN A 206.223.22.1 > > Received 193 bytes from 209.193.4.7#53 in 698 ms > [tester@ibm333 tester]$ > > But it looks OK from here so most likely someone has a badly set subnet > mask. > Thanks for jumping in here Civileme. Your detailed knowledge of Mandrake's systems always adds a level of understanding that can't be reproduced without your presence. It's good to see you back around.
Anyway, backed to the discussion at hand. I have already checked this out with the ISP and they have told me the problem relates to the fact that I am on a virtual host. Since so many domains point to the ip address, the reverse lookup is actually the machine name doing the virtual hosting, in this case Hosting-132-17.PHPWebHosting.Com. My domain, gkmweb.com, points to the numeric ip address that you looked up (64.72.132.17), which on a reverse lookup points to Hosting-132-17.PHPWebHosting.Com. Perhaps you can tell me if they are all wet and this can be fixed with changes to the DNS entries. - -- Greg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+RnEAwDpHP6GALAARAon7AJ9MeKI5qMMCqSaTX1vj4YWTaOOfNgCePeM8 5bT9BiCtYxbdf6iGN5n0dAo= =2XSh -----END PGP SIGNATURE-----
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
