Cannot resolve DNS off public dns, but can via nameserver ip
Barry Margolin
barmar at alum.mit.edu
Sat Aug 14 02:11:04 UTC 2010
In article <mailman.334.1281737169.15649.bind-users at lists.isc.org>,
Mike Mackintosh <mike.mackintosh at angrystatic.com> wrote:
> That is correct. I made the change like that to get it working
> temporarily. The registrar is pointing to the angrystatic.com
> nameservers, which the zone file is referencing the
> dns.angryserver.net host. I then had dns.angrystatic.com point to the
> same IP address as dns.angryserver.net, so the domain could be
> resolved. What would the side effects be leaving the NS in the zone
> file to angryserver, but the registrar pointing to angrystatic?
You need glue records in the parent zone when the nameservers are in the
zone they're hosting. If you have:
angryserver.net. IN NS dns.angryserver.net.
and the A record for dns.angryserver.net expires, the nameserver can no
longer be resolved.
--
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE don't copy me on replies, I'll read them in the group ***
More information about the bind-users
mailing list