rharolde at umich.edu
Fri Jan 20 16:19:39 UTC 2017
On Fri, Jan 20, 2017 at 10:57 AM, Ron Wingfield <Ron.Wingfield at archaxis.net>
> I am having difficulty configuring reverse DNS. This has been a problem
> for over a year between my server(s) and my ISP, AT&T. Specifically, I
> cannot eMail to any recipient that requires rDNS verification, e.g.,
> SBCglobal.net, Comcast.net, or AOL. Very frustrating.
> Two examples of dig:
> # dig -t mx alpha.archaxis.net
> ANSWER: 0, AUTHORITY: 1,
> Why does this first example, digging the FQDN of alpha.archaxis.net
> reports one authority but no answers?
> # dig -t mx archaxis.net
> ANSWER: 2, AUTHORITY: 0,
> . . .yet this second example. digging the FQDN of archaxis.net reports no
> authority but 2 answers?
> (The) ;; ANSWER SECTION: (of both examples) reports:
> archaxis.net. 10800 IN MX 30 bravo.archaxis.net.
> archaxis.net. 10800 IN MX 20 alpha.archaxis.net.
> In both cases, the reported server is an AT&T server ;; SERVER:
> . . .why shouldn’t this “point” to my server, 220.127.116.11 and not
Just to clear up the confusion on this point:
dig is telling you that "SERVER: 18.104.22.168#53" is the DNS resolver that
your computer used to answer the DNS question. That server is not part of
the answer to the question.
> I have coded my BIND 9 in-addr.arpa zone file as follows:
> $ORIGIN 233.202.162.in-addr.arpa.
> $TTL 3h
> @ IN SOA ns1.archaxis.net. me.archaxis.net. (
> 2017012002 <(201)%20701-2002> ; Serial
> 1h ; Refresh
> 1h ; Retry
> 1h ; Expire
> 1h ) ; Negative cashing TTL
> 3600 IN NS ns1.archaxis.net.
> 3600 IN NS ns2.archaxis.net.
> 80 3600 IN PTR network.archaxis.net.
> 81 3600 IN PTR alpha.archaxis.net.
> 82 3600 IN PTR bravo.archaxis.net.
> 87 3600 IN PTR broadcast.archaxis.net.
> What is wrong? Is this my problem, or with AT&T?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bind-users