In article ,
Mike Mackintosh 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
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 t
Thanks,
That was the answer i was looking for. Now it is making sense.
Thanks again,
Mike
On Aug 13, 2010, at 4:19 PM, Dave Sparro wrote:
On 8/13/2010 1:53 PM, Mike Mackintosh wrote:
How will the registrar be able to resolve the host name
dns.angryserver.net if dns is not propagating? I und
Am 13.08.2010 19:53, schrieb Mike Mackintosh:
Hi All,
I recently set up a new web server for a group of hosts, and mirrored
the setup of bind off a working system. For some reason, the DNS is
not resolving off public dns server when the nameservers for these
domains are directed to this serv
On 8/13/2010 1:53 PM, Mike Mackintosh wrote:
How will the registrar be able to resolve the host name
dns.angryserver.net if dns is not propagating? I understand that when
you register a domain, the registrar will send the nameserver
information to the root servers, which are then queried for your
Hi All,
I recently set up a new web server for a group of hosts, and mirrored
the setup of bind off a working system. For some reason, the DNS is
not resolving off public dns server when the nameservers for these
domains are directed to this server, and i cannot resolve any of the
zones o
6 matches
Mail list logo
