A. Stop using nslookup. It's a really horrible DNS troubleshooting tool.
Learn to use dig.
B. Do a zone transfer (via dig) of the united-networks.ru zone from the
primary master, to verify that the correct delegation record, and
associated glue, are contained within named's in-core database of t
Dear Phil!
What did you mean saying: "Are you sure you've reloaded
the zone? " Did you mean do I "rndc reload
united-networks.ru in internal" - Yes! I don't remember,
did I change serial every time I changed zone-file. But
now I did all the things required. I changed serial, I
reloaded zone,
On 04/02/2011 11:44 AM, Яцко Эллад Геннадьевич wrote:
$ORIGIN domain.united-networks.ru.
IN NS srvmain
IN A 172.16.77.2
srvmain IN A 172.16.77.2
Huh, delegation looks ok. Are you sure you've reloaded the zone?
I tried to nslookup from 172.16.77.11:
Try a "dig" on the DNS
Please, help! What could it be?
172.16.77.1 must delegate zone domain.united-networks.ru
to srvmain.domain.united-networks.ru (W2K3 DC)
But it doesn't! How can it be done?
~~named.conf~~
// $FreeBSD: src/etc/namedb/named.conf,v 1.21.2.1
2005/09/1
4 matches
Mail list logo
