|
|
 |  |
Re: ListServe setupFrom: Richard Johnson Date: Friday, June 20, 1997
Time: 5:24:00 amAt 22:55 -0400 on 6/19/97, Jim Turney wrote:
> If I have a PTR record for 206.55.18.12 in my 18.55.206.in-addr.arpa. file
> on QDNSPro, shouldn't a mailhost be able to find that it is mapped to
> Fast.Look.net?
Sure, if your QuickDNS Pro server is listed at the InterNIC as autoritative
for the 18.55.206.in-addr.arpa domain, has that domain delegated to it by
the server authoritative for the 55.206.in-addr.arpa domain, and/or
provides data as a primary for a secondary server that's authoritative for
the 18.55.206.in-addr.arpa domain.
rogue:tmp {672} nslookup -type=NS 18.55.206.in-addr.arpa
Server: rogue.river.com
Address: 206.168.172.14
Non-authoritative answer:
18.55.206.in-addr.arpa nameserver = NS2.MNSINC.COM
18.55.206.in-addr.arpa nameserver = Name.Look.net
18.55.206.in-addr.arpa nameserver = ns.MNSINC.COM
18.55.206.in-addr.arpa nameserver = NS1.MNSINC.COM
Authoritative answers can be found from:
NS2.MNSINC.COM internet address = 206.55.3.11
Name.Look.net internet address = 206.55.18.14
NS1.MNSINC.COM internet address = 199.164.210.12
Looks like you're OK there if the server running QuickDNS Pro is
name.look.net, and the other servers all pull zone transfers from it.
> But maybe that's not the 'problem' I have a client that says
> he can't send email addressed to @206.55.18.12 (see quote below) This IP is
> assigned to a ListSTAR SMTP server. His mail goes through fine if he sends
> to @ListServe.com (DNS records for that domain set MX to Fast.Look.net)
> Could this be a DNS set up issue?
>
> My client says:
> >I did a lookup on 206.55.18.12 and get a no match from InterNIC
> >Our Mail system attempts to verify the DNS registry
> >before it will forward email and it could not do it.
Your client doesn't say what kind of 'lookup' he did. I suspect he's
confusing whois database lookups with DNS lookups, given that bit about the
InterNIC.
If not, his setup has a problem, as I don't have any difficulty resolving
both 206.55.18.12 <-> fast.look.net using nslookup on my openbsd systems,
or DNS Lookup on my Macs.
And of course he can't send mail addressed to @206.55.18.12. Try looking
up an A record for an IP address sometime, and you'll likely have the same
problem as he is (it's nonsense, unless your lookup software flips the
lookup to help you out of your mistake :-). To send mail directly to an IP
address, he needs use the following instead: @[206.55.18.12].
Richard
|

Return to Digital Point Solutions' Home Page |