Ladies and Gentlemen:
At the risk of double posting . . .yet again (sending this time in plain
text format), I'm reposting this question -- apparently my previous
membership was purged or otherwise not valid.
Regardless, after about eight months with no problems, AT&T U-verse has
once again quit resolving? my reverse DNS; and now I can no longer send
eMail to DNS-aware MTA's, such as sbcglobal.net, aol.com, comcast.net,
et al. I have tried tweaking my zone file as follows but nothing seems
to work. I think they (AT&T) have done something . . .yet again, to
block my DNS server (authority?). Regarding my zone file configuration
follows. Can someone tell me if the configuration is erred, and
otherwise suggest corrections, or should I expect it to work? . . .and
pressure AT&T to fix the problem.
Thanks!
(Comment lines represent variant tests.)
$ORIGIN 80/29.233.202.162.in-addr.arpa.
; $ORIGIN 233.202.162.in-addr.arpa.
$TTL 3h
@ IN SOA archaxis.net. rtwingfield.archaxis.net. (
2016061306 ; 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 archaxis.net.
81 3600 IN PTR alpha.archaxis.net.
;82 3600 IN PTR bravo.archaxis.net. /; //(an
alternate ser//ver)/
;87 3600 IN PTR broadcast.archaxis.net.
---------------------------------------------
Ron Wingfield,
CEO WaterMark Marine Industries, Inc.
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users