I can't make any sense of your question. A forward lookup to ftp.tis.com
gives a CNAME record for portal.ex.tis.com which in turn give an A record of
192.94.214.101.
A reverse lookup on 192.94.214.101 immediately gives a PTR record of
portal.ex.tis.com. There's nothing double about it.
The only good use I've heard of for wildcards is in MX records. And it's not
really a good use at that.
So what EXACTLY is your problem? Can you please describe something that your
trying to do but can't? Can you provide as many examples as you think are
warrented? For example, it would be nice if you provided information like,
"when I try to telnet to that host, it drops me immediately, but when I ftp to
it, it waits one minute and then lets me in. I can't ping to that name, but I
*can* ping to that address."
> Betsy Abreu <betsy @
mail .
infocom .
etecsa .
cu> says:
>
> Hi
> I've problems configuring a double reverse lookups on a DNS server; I
> heard about a wildcard on PTR records but cannot solve them, this cause
> that ftp connections to places that make double reverse lookup (like
> ftp.tis.com) are refused.
>
> I'm using SVR3 and BIND 4.9.2
>
> Could anybody give me some information about this ?
>
> Thanks
>
> BETSY
|
|
