Resolution of our registered domain, archaxis.net, is not resolving . . .cannot be found. This has worked for past months until 3 NOV 2017, when it started failing. Additionally, the email server, Sendmail, has stopped receiving email, and cannot send mail to a DNS-aware MTA such as sbcglobal.net, Comcast.com, AOL, et al. We run BIND version 9.10.2 on FreeBSD 10.1-RELEASE.
Again, I emphasize that this configuration has been working since modified Thr Aug 6 2015 following conversion to AT&T U-verse, and has not changed since Jan 12 2017 when added an SPF TXT RR for archaxis.net. The zone file is configured as follows: $ORIGIN archaxis.net. $TTL 3h @ IN SOA archaxis.net. rtwingfield.archaxis.net. ( 2017012501 ; Serial number 3h ; Refresh 1h ; Retry 3w ; Expire 1h ) ; Negative caching TTL @ IN A 162.202.233.81 localhost IN A 127.0.0.1 @ IN NS ns1.archaxis.net. @ IN NS ns2.archaxis.net. IN MX 20 alpha.archaxis.net. IN MX 30 bravo.archaxis.net. ; Machine Names @ IN A 162.202.233.81 ns1 IN A 162.202.233.81 ns2 IN A 162.202.233.81 alpha IN A 162.202.233.81 bravo IN A 162.202.233.81 IN TXT "v=spf1 a include:_ spf.google.com ~all" IN TXT "v=spf1 mx include:archaxis.net -all" Our ISP, AT&T U-verse, insists that apparently our registrar, eNamco/Dotster (whatever) changed or dropped something a few weeks ago and we need to request the registrar to add a "glue" record, i.e., an "A" record (I assume), in association with our two designated name servers, ns1 and ns2.archaxis.net. I assume that this would be something like "@ IN A 162.202.233.81" where the @ symbol is shorthand for "$ORIGIN archaxis.net.", i.e., substituted as "archaxis.net." AT&T’s ProvDNS experts response to my complaint is "You should contact support for your domain registrar, http://www.eNameCo.com/ and tell them [they]need to add a glue record for your two name servers with the IP address. It looks like some type of change was made at that level a few weeks ago and it messed things up (has nothing to do with us)." In other words, AT&T is blaming the fault on the registrar . . .having changed something. After several calls and a lengthy o/l chat with Dotster/eNamco, finally someone entered a Support Ticket for the addition of a “glue” record and this was reported as completed 11/18/2017 at 10:31 PM EST. Well, the problem persists . . .still failing. After reporting this continuing unsatisfactory fail to AT&T, they have yet again responded "As was stated, it shows that we are correctly delegating the records. The issue still persists that your nameservers A records are not resolving. That is wholly outside our control or access. PTR requests will continue to fail as the ns1.archaxis.net and ns2.archaxis.net are not responding to requests." I am at my wit’s end. This was working – why did it just stop? Who is to blame? Can any of you list members see any thing wrong with the previously included zone file? Thanks, Ron W.
_______________________________________________ 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