Reverse DNS question

[Bob Smith]

192... was meant to be a place holder for the real values, such as
the phony "domain.com" domain name.

I'll try the dig +trace.  Thanks,

-Bob


> 192.100.1 is owned by the following. Have they delegated DNS to you for
> reverse lookups?
>
> inetnum:      192.100.1.0 - 192.100.1.255
> netname:      CCWR
> descr:        Computing Centre for Water Research
> descr:        Private Bag X01
> descr:        Scottsville, 3209
> country:      ZA
> admin-c:      AK115-AFRINIC
> tech-c:       AK115-AFRINIC
> status:       ASSIGNED PI
> mnt-by:       TF-192-100-1-MNT
> mnt-lower:    TF-192-100-1-MNT
> changed:      hostmaster at arin.net 19910308
> changed:      hostmaster at arin.net 19980803
> changed:      hostmaster at afrinic.net 20050221
> source:       AFRINIC
>
> person:       Arne F. Kure
> address:      Computing Centre for Water Research
> address:      Private Bag X01
> address:      Scottsville
> address:      3201
> address:      ZA
> phone:        +27 331 260 5175
> e-mail:       kure at aqua.ccwr.ac.za
> nic-hdl:      AK115-AFRINIC
> changed:      hostmaster at arin.net 19960131
> changed:      hostmaster at afrinic.net 20050221
> source:       AFRINIC
>
> If you just put 192.100.1 as a placeholder below, then I would still look
> at
> whether the DNS for your IPs has been delegated to the right name server.
>
> Try something like:
>
> dig +trace 2.1.100.192.in-addr.arpa
>
> and see where it stops or fails.
>
> Good luck,
> -Allen
>
> On Wednesday 08 February 2006 12:41, Bob Smith wrote:
>> Hey Gurus,
>>
>> I'm running RH9, and have not had much problem with setting up DNS, with
>> one exception:  getting the reverse DNS lookup to work properly from
>> outside of the box.  I have forward and reverse dns zone files, but
>> I think I'm missing something.  Both are listed in the named.conf file,
>> but when I use some of the web tools, or do a reverse lookup, it can't
>> find
>> the domain.  Also, some mail servers are now looking for a domain tag
>> in place of the in-addra.arpa basic declaration.
>>
>> Any help would be appreciated.
>>
>> Thanks,
>>
>> -Bob
>>
>> Entry in named.conf:
>> zone "domain.com" {
>>         type master;
>>         file "domain.com.zone";
>> };
>>
>> zone "1.100.192.in-addr.arpa" {
>>         type master;
>>         file "1.100.192.in-addr.arpa.zone";
>> };
>>
>> Here's a sample of the forward zone file (domain.com.zone)
>> ------------------
>> $TTL 86400
>> domain.com.     IN      SOA     machine.domain.com.
>> webmaster.machine.domain.com (
>>                         2006010902 ; serial number
>>                         28800 ; refresh interval
>>                         7200 ; retry interval
>>                         604800 ; expire
>>                         86400 ; time to live
>>                         )
>>
>> ;
>> ; Name servers
>> ;
>> domain.com.		IN	NS	machine.domain.com.
>> domain.com.		IN	A	192.100.1.2
>> machine.domain.com.	IN	A	192.100.1.2
>> ns1.domain.com.		IN	CNAME	machine.domain.com.
>> domain.com.		IN	MX	10	machine.domain.com.
>> ; EOF
>>
>> And here's the 1.100.192.in-addr.arpa.zone file
>> $TTL 86400
>> @       IN      SOA     ns1.domain.com. webmaster.machine.domain.com (
>>                         2006012102 ; serial number
>>                         28800 ; refresh interval
>>                         7200 ; retry interval
>>                         604800 ; expire
>>                         86400 ; time to live
>>                         )
>>
>> @       IN      NS      ns1.domain.com
>> 2       IN      PTR     domain.com.
>> ; EOF
>