Werbung: SecurityConsole.de verwaltet Ihre Computer mit Security Essentails aus der Cloud!
30 Tage kostenfrei testen und 20% Rabatt für Ihre Bestellung mit Promocode: WBF2685582
(Promocode gültig bis 31.12.2011)

Group:  English: Windows Server » microsoft.public.windows.server.dns
Thread: Standard DNS failed integrated with ad

HTVi
TV Discussion Newsgroups

Standard DNS failed integrated with ad
"NewsReader" <carl[ at ]anywhere.com> 11/1/2008 2:20:23 AM
I have a site where they have 1 primary and 2 secondary DNS servers. They
show signs of once being AD Integrated with the subdomains
_msdcs
_sites
_tcp
_udp
DomainDnsZones
ForestDnsZones

I am told they tried over 1 year ago to convert to AD integrated and their
entire DNS 'went down' so they went back to standard. Im researching why
it would have gone down in the conversion. They currently have 3 DCs 1
primary DNS the other 2 secondary. I would like to get this converted to
ADI. Is there any caution about doing this with the older 'leftover'
subdomains? Is there a good procedure for doing this?

Thanks all

Janke
--


Re: Standard DNS failed integrated with ad
"A, Deji" <deji[ at ]akomolafe.com> 11/1/2008 3:13:31 AM
There shouldn't really be any reason for the entire DNS to "go down" from
simply converting zones. I would encourage you to safe copies of the zone
files, then do the conversion to ADI (on a weekend or when no-one is in the
office so that you could have sufficient time to troubleshoot/back out
without presure). Then if the DNS goes down after the switch, please post
back with the exact symptom and errors.

Deji

"NewsReader" <carl[ at ]anywhere.com> wrote in message
news:Ox0qnh8OJHA.3980[ at ]TK2MSFTNGP06.phx.gbl...
[Quoted Text]
>I have a site where they have 1 primary and 2 secondary DNS servers. They
>show signs of once being AD Integrated with the subdomains
> _msdcs
> _sites
> _tcp
> _udp
> DomainDnsZones
> ForestDnsZones
>
> I am told they tried over 1 year ago to convert to AD integrated and their
> entire DNS 'went down' so they went back to standard. Im researching
> why it would have gone down in the conversion. They currently have 3 DCs
> 1 primary DNS the other 2 secondary. I would like to get this converted
> to ADI. Is there any caution about doing this with the older 'leftover'
> subdomains? Is there a good procedure for doing this?
>
> Thanks all
>
> Janke
> --
>

Re: Standard DNS failed integrated with ad
Meinolf Weber <meiweb(nospam)[ at ]gmx.de> 11/1/2008 3:26:21 PM
Hello newsreader,

Save the zone files as a copy and convert on the primary DNS to AD integrated
zones. On the secondaries delete the existing zones and wait for AD replication.
If you have any erros after change please post them here.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


[Quoted Text]
> I have a site where they have 1 primary and 2 secondary DNS servers.
> They
> show signs of once being AD Integrated with the subdomains
> _msdcs
> _sites
> _tcp
> _udp
> DomainDnsZones
> ForestDnsZones
> I am told they tried over 1 year ago to convert to AD integrated and
> their entire DNS 'went down' so they went back to standard. Im
> researching why it would have gone down in the conversion. They
> currently have 3 DCs 1 primary DNS the other 2 secondary. I would
> like to get this converted to ADI. Is there any caution about doing
> this with the older 'leftover' subdomains? Is there a good procedure
> for doing this?
>
> Thanks all
>
> Janke
>

Re: Standard DNS failed integrated with ad
tenroc2o0o <tenroc2o0o.3i7o3f[ at ]DoNotSpam.com> 11/1/2008 6:40:05 PM
I had this happen before. Apparently a server can have an AD integrated DNS zone as well as a standard sitting on top of it - really confusing. DNS updates weren't working correctly and my servers weren't syncing properly. I just *deleted* the zone (since it was standard anyway), restarted DNS, and the AD-Integrated Zone just reappeared in the list - like it had been there all along. Ironically it had the latest DNS info from the other servers.

Furthermore, even if you screw up DNS, just create a zone for your domain, make it AD-integrated, and reboot. The DNS entries should recreate themselves when AD starts up. -- tenroc2o0o ------------------------------------------------------------------------ tenroc2o0o's Profile: http://forums.techarena.in/members/tenroc2o0o.htm View this thread: http://forums.techarena.in/server-dns/1064350.htm http://forums.techarena.in
Re: Standard DNS failed integrated with ad
"A, Deji" <deji[ at ]akomolafe.com> 11/2/2008 6:20:23 AM
You really don't want to just delete zones and hope that AD recreates them
automagically. What if you have static records in there? For objects that
are not able to (or actively not allowed to) register themselves in DNS?
What if the zone does allow dynamic registrations?

You want to save the flat file (to a location off the server even) before
you whack a zone. A "ooops. ok, let's roll it back" is better that "we a
phucked, what now?"

Just saying.

Deji

"tenroc2o0o" <tenroc2o0o.3i7o3f[ at ]DoNotSpam.com> wrote in message
news:tenroc2o0o.3i7o3f[ at ]DoNotSpam.com...
[Quoted Text]
>
> I had this happen before. Apparently a server can have an AD integrated
> DNS zone as well as a standard sitting on top of it - really confusing.
> DNS updates weren't working correctly and my servers weren't syncing
> properly. I just *deleted* the zone (since it was standard anyway),
> restarted DNS, and the AD-Integrated Zone just reappeared in the list -
> like it had been there all along. Ironically it had the latest DNS info
> from the other servers.
>
> Furthermore, even if you screw up DNS, just create a zone for your
> domain, make it AD-integrated, and reboot. The DNS entries should
> recreate themselves when AD starts up.
>
>
> --
> tenroc2o0o
> ------------------------------------------------------------------------
> tenroc2o0o's Profile: http://forums.techarena.in/members/tenroc2o0o.htm
> View this thread: http://forums.techarena.in/server-dns/1064350.htm
>
> http://forums.techarena.in
>

Re: Standard DNS failed integrated with ad
tenroc2o0o <tenroc2o0o.3i97nb[ at ]DoNotSpam.com> 11/2/2008 2:26:20 PM
well unless he's managing FedEx's network people usually dont have to many static dns entries aside from an occasional printer.

Obviously, make a backup.

My point was.. worst case scenario if you can't make it work, A.D. will recreate it's DNS entries. -- tenroc2o0o ------------------------------------------------------------------------ tenroc2o0o's Profile: http://forums.techarena.in/members/tenroc2o0o.htm View this thread: http://forums.techarena.in/server-dns/1064350.htm http://forums.techarena.in
Re: Standard DNS failed integrated with ad
"Ace Fekay [Microsoft Certified Trainer]" <firstnamelastname[ at ]hotmail.com> 11/3/2008 5:15:41 AM
In news:Ox0qnh8OJHA.3980[ at ]TK2MSFTNGP06.phx.gbl,
NewsReader <carl[ at ]anywhere.com> requesting assistance, typed the following:
[Quoted Text]
> I have a site where they have 1 primary and 2 secondary DNS servers. They
> show signs of once being AD Integrated with the subdomains
> _msdcs
> _sites
> _tcp
> _udp
> DomainDnsZones
> ForestDnsZones
>
> I am told they tried over 1 year ago to convert to AD integrated and
> their entire DNS 'went down' so they went back to standard. Im
> researching why it would have gone down in the conversion. They
> currently have 3 DCs 1 primary DNS the other 2 secondary. I would
> like to get this converted to ADI. Is there any caution about doing
> this with the older 'leftover' subdomains? Is there a good procedure
> for doing this?
> Thanks all
>
> Janke


I can't see DNS "going down." If you mean the zone disappeared, I'mwilling
to bet in a scenario with mixed 2000 & 2003 DCs with AD integrated zones and
not setting the zone replication scope correctly in the 2003 DNS console to
accomodate 2000's method of storing the zones in the DomainNC when someone
may selected the 'All DNS in the Domain,' then I can see that causing a HUGE
issue. It will create a duplicate zone and will mess things up. To clean it
up, or even matter of fact to check for dupe zones, you can use ADSI Edit to
find and delete the dupes. Look at the zone names in the DomainDnsZones
partition and the DomainNC partition under Microsoft Services, DNS. The
dupes show up with a prefix of "CNF... <long GUID #>" or "PRE..."


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT
Microsoft Certified Trainer

For urgent issues, you may want to contact Microsoft PSS directly.
Please check http://support.microsoft.com for regional support phone
numbers.

Home | Search | Terms | Imprint Contact
Newsgroups Reader - provided by WiredBox.Net
Suche nach Orten, Städten, Postleitzahlen, Vorwahlen, Kfz-Kennzeichen