Search Again: Re: reverse DNS lookup for IRC From: Michael Reid Date: Friday, August 14, 1998 Time: 12:08:00 am Hi, >When I fill in reverse entries for each of our IP# served by DHCP in our >Dialin Access Controller? As in: > > 129.226.37.203.in-addr.arpa. PTR DOT.tc. > > 130.226.37.203.in-addr.arpa. PTR DOT.tc. > > 131.226.37.203.in-addr.arpa. PTR DOT.tc. > > 132.226.37.203.in-addr.arpa. PTR DOT.tc. > > . > . > . > . > >in my 226.37.203.in-addr.arpa. record, it doesn't seem to help. > >Can someone help, please? Your reverse records are not quite legal, you should not have more than one PTR record per host (putting proper matching 'forward records' (A records) wouldn't hurt either) but, the major problem however is this: --- <nslookup:129.226.37.203.in-addr.arpa/*/203.37.226.2> Authoritative answer: 129.226.37.203.in-addr.arpa PTR 86400 DOT.tc --- ... and ... --- <nslookup:DOT.tc/A/203.37.226.2> Authoritative answer: DOT.tc A 86400 203.37.226.195 --- As you can see from above, the PTR record points to a host 'dot.tc', when you to a cross-check for the host 'dot.tc' you get a different IP (A record). For each PTR you have, the corresponding A record is mismatched. As I said above, naming the hosts properly would help. Try: 129.226.37.203.in-addr.arpa. PTR node-01.DOT.tc. 130.226.37.203.in-addr.arpa. PTR node-02. DOT.tc. 131.226.37.203.in-addr.arpa. PTR node-03. DOT.tc. 132.226.37.203.in-addr.arpa. PTR node-04. DOT.tc. . . . . I think another major problem is that the Microsoft DNS servers still have your domain records cached as non-existant. Your refresh for: <nslookup:226.37.203.in-addr.arpa/*/203.37.226.2> Authoritative answer: 226.37.203.in-addr.arpa SOA 86400 sbs.tc nquinn.acm.org SERIAL 1998081401 REFRESH 28800 RETRY 7200 EXPIRE 604800 226.37.203.in-addr.arpa NS 86400 joanna.william.org 226.37.203.in-addr.arpa NS 86400 sbs.tc 203.37.226.2 ... seems to be set at 8 hours. Give their DNS a few hours (or longer), for their old data to timeout. But wait! They'll have the wait even longer, at least until '19980814', which is a date in the future! Tomorrow in fact. Check your clocks! Hope this helps. Michael Reid

Messages In This Thread: reverse DNS lookup for IRC by Nick Quinn on Aug 13, 1998 at 11:21:00 pm Re: reverse DNS lookup for IRC by Michael Reid on Aug 14, 1998 at 12:08:00 am Re: reverse DNS lookup for IRC by Michael Reid on Aug 14, 1998 at 12:19:00 am Re: reverse DNS lookup for IRC by Nick Quinn on Aug 14, 1998 at 2:11:00 am Re: reverse DNS lookup for IRC by Nick Quinn on Aug 14, 1998 at 2:15:00 am Re: reverse DNS lookup for IRC by Michael Reid on Aug 14, 1998 at 11:05:00 pm Re: reverse DNS lookup for IRC by Nick Quinn on Aug 15, 1998 at 12:32:00 am Re: reverse DNS lookup for IRC by Nick Quinn on Aug 15, 1998 at 7:26:00 am Re: reverse DNS lookup for IRC by Michael Reid on Aug 15, 1998 at 5:58:00 pm Re: reverse DNS lookup for IRC by Sigfus Magnusson on Aug 17, 1998 at 4:09:00 pm