Re: DNS reverse-lookup, and SOA change
From: Andrew Hodgson (me3_at_privacy.net)
Date: 08/24/04
- Next message: jl: "dhcp and dns"
- Previous message: William Stacey [MVP]: "Re: After delegation parent DNS cannot resolve to child DNS"
- In reply to: Chuck: "DNS reverse-lookup, and SOA change"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 24 Aug 2004 08:09:46 +0100
On Mon, 23 Aug 2004 12:01:15 -0400, "Chuck" <cholley_@hotmail.com>
wrote:
>greetings,
>
>i have two questions. the first one is, our SOA server died and had to be
>rebuilt, we did that and in the mean time the secondary picked up duties of
>SOA automatically. when i went in to look at it it said it was the
>SOA....Great!!! so i rebuilt the other server, and brought it online as a
>secondary DNS. went in through the console to change it to SOA, it seemed
>to work until i refreshed it and it kept the old settings. i did this a few
>times to make sure it would not work, and it never did work. the SOA would
>never change. what did change though was now both servers thought they were
>SOA for the domain/zone. problem!!
Careful, SOA = start of authority record, which is a record that must
be there in all DNS zones. What you are talking about is
primary/secondary DNS servers, and if your primary dies, then the
secondary will not just "take over the role of primary", as you found
out, you shouldn't be able to change anything through the secondary
zones.
>
>so, i decided to blow away the DNS server that i did not want as SOA, and
>recreate it as a secondary DNS. i did that, however, i could not delete the
>whole server from the console, so i killed the service, and blew away the
>zone. created a new zone, made it a secondary, and thought i was done.
>well, the now only SOA eventually got an error message, and said that the
>zone was deleted, and it deleted the zone as well. not good.
Remember that all secondaries should be listed as NS records on the
zone. For example:
Private zone:
hodgsonfamily.org. in NS elrond.hodgsonfamily.org.
hodgsonfamily.org. in NS gandalf.hodgsonfamily.org
elrond.hodgsonfamily.org. in a 192.168.1.4
gandalf.hodgsonfamily.org. in a 192.168.1.5 (for example sake).
The integration with AD should be doing this automatically, but it is
best to check the data in each zone to ensure that things are getting
put into the DNS, as after all this is the important thing.
>
>so i made the seconday a primary, since it still had all the records, and
>made the other server a secondary, which i did not want to do.
>
>now we cant seem to create a reverse lookup zone on the SOA, and it is
>looking to the other DNS server and says that it is the SOA for the reverse
>lookup zone. weired!!
This should be a separate issue, as the reverse lookup zone is
different (a separate zone, possibly with separate primary/secondary
servers) from your forward lookup zone.
Andrew.
-- Andrew Hodgson in Bromyard, Herefordshire, UK. My Email: use <andrew at hodgsonfamily dot org>.
- Next message: jl: "dhcp and dns"
- Previous message: William Stacey [MVP]: "Re: After delegation parent DNS cannot resolve to child DNS"
- In reply to: Chuck: "DNS reverse-lookup, and SOA change"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
