|
server
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
|
I have a DNS server than continues to update its own DNS record to
192.168.1.50. How can I keep this from happening? Hi Dale,
DNS server has updated its own host (A) records. In order to ensure that its DS-integrated peer DNS servers are able to replicate with this server, an attempt was made to update them with the new records through dynamic update. An error was encountered during this update, the record data is the error code. If this DNS server does not have any DS-integrated peers, then this error should be ignored. If this DNS server's Active Directory replication partners do not have the correct IP address(es) for this server, they will be unable to replicate with it. To ensure proper replication: 1) Find this server's Active Directory replication partners that run the DNS server. 2) Open DnsManager and connect in turn to each of the replication partners. 3) On each server, check the host (A record) registration for THIS server. 4) Delete any A records that do NOT correspond to IP addresses of this server. 5) If there are no A records for this server, add at least one A record corresponding to an address on this server, that the replication partner can contact. (In other words, if there multiple IP addresses for this DNS server, add at least one that is on the same network as the Active Directory DNS server you are updating.) 6) Note, that is not necessary to update EVERY replication partner. It is only necessary that the records are fixed up on enough replication partners so that every server that replicates with this server will receive (through replication) the new data. I hope that the information above helps you. Have a Nice day. Rajesh J S MCSA, MCP Show quoteHide quote "Dale Gibble" wrote: > I have a DNS server than continues to update its own DNS record to > 192.168.1.50. How can I keep this from happening? > > > Obviously this is the "party line". This same mantra is recited on every
search that I found. Now for the HARD question: how do you fix it? Dale Show quoteHide quote "Rajesh J S" <Rajes***@discussions.microsoft.com> wrote in message news:99006A4A-3FDF-4A6A-8F09-65850599B6B8@microsoft.com... > Hi Dale, > > DNS server has updated its own host (A) records. In order to ensure that > its > DS-integrated peer DNS servers are able to replicate with this server, an > attempt was made to update them with the new records through dynamic > update. > An error was encountered during this update, the record data is the error > code. > > If this DNS server does not have any DS-integrated peers, then this error > should be ignored. > > If this DNS server's Active Directory replication partners do not have the > correct IP address(es) for this server, they will be unable to replicate > with > it. > > To ensure proper replication: > 1) Find this server's Active Directory replication partners that run the > DNS > server. > 2) Open DnsManager and connect in turn to each of the replication > partners. > 3) On each server, check the host (A record) registration for THIS server. > 4) Delete any A records that do NOT correspond to IP addresses of this > server. > 5) If there are no A records for this server, add at least one A record > corresponding to an address on this server, that the replication partner > can > contact. (In other words, if there multiple IP addresses for this DNS > server, > add at least one that is on the same network as the Active Directory DNS > server you are updating.) > 6) Note, that is not necessary to update EVERY replication partner. It is > only necessary that the records are fixed up on enough replication > partners > so that every server that replicates with this server will receive > (through > replication) the new data. > > I hope that the information above helps you. > Have a Nice day. > > Rajesh J S > MCSA, MCP > > > > "Dale Gibble" wrote: > >> I have a DNS server than continues to update its own DNS record to >> 192.168.1.50. How can I keep this from happening? >> >> >> Hi Dale,
Have you fallowed the stpes from 1 to 6 as I told. I should help you slove the issue... Rajesh J S MCSA, MCP Show quoteHide quote "Dale Gibble" wrote: > Obviously this is the "party line". This same mantra is recited on every > search that I found. Now for the HARD question: how do you fix it? > > Dale > > > "Rajesh J S" <Rajes***@discussions.microsoft.com> wrote in message > news:99006A4A-3FDF-4A6A-8F09-65850599B6B8@microsoft.com... > > Hi Dale, > > > > DNS server has updated its own host (A) records. In order to ensure that > > its > > DS-integrated peer DNS servers are able to replicate with this server, an > > attempt was made to update them with the new records through dynamic > > update. > > An error was encountered during this update, the record data is the error > > code. > > > > If this DNS server does not have any DS-integrated peers, then this error > > should be ignored. > > > > If this DNS server's Active Directory replication partners do not have the > > correct IP address(es) for this server, they will be unable to replicate > > with > > it. > > > > To ensure proper replication: > > 1) Find this server's Active Directory replication partners that run the > > DNS > > server. > > 2) Open DnsManager and connect in turn to each of the replication > > partners. > > 3) On each server, check the host (A record) registration for THIS server. > > 4) Delete any A records that do NOT correspond to IP addresses of this > > server. > > 5) If there are no A records for this server, add at least one A record > > corresponding to an address on this server, that the replication partner > > can > > contact. (In other words, if there multiple IP addresses for this DNS > > server, > > add at least one that is on the same network as the Active Directory DNS > > server you are updating.) > > 6) Note, that is not necessary to update EVERY replication partner. It is > > only necessary that the records are fixed up on enough replication > > partners > > so that every server that replicates with this server will receive > > (through > > replication) the new data. > > > > I hope that the information above helps you. > > Have a Nice day. > > > > Rajesh J S > > MCSA, MCP > > > > > > > > "Dale Gibble" wrote: > > > >> I have a DNS server than continues to update its own DNS record to > >> 192.168.1.50. How can I keep this from happening? > >> > >> > >> > > > How do I : 1) Find this server's Active Directory replication partners that
run the DNS server. Dale Show quoteHide quote "Rajesh J S" <Rajes***@discussions.microsoft.com> wrote in message news:4662365F-501B-4F88-BB11-F66CA422F9D2@microsoft.com... > Hi Dale, > > Have you fallowed the stpes from 1 to 6 as I told. > I should help you slove the issue... > > Rajesh J S > MCSA, MCP > > > "Dale Gibble" wrote: > >> Obviously this is the "party line". This same mantra is recited on every >> search that I found. Now for the HARD question: how do you fix it? >> >> Dale >> >> >> "Rajesh J S" <Rajes***@discussions.microsoft.com> wrote in message >> news:99006A4A-3FDF-4A6A-8F09-65850599B6B8@microsoft.com... >> > Hi Dale, >> > >> > DNS server has updated its own host (A) records. In order to ensure >> > that >> > its >> > DS-integrated peer DNS servers are able to replicate with this server, >> > an >> > attempt was made to update them with the new records through dynamic >> > update. >> > An error was encountered during this update, the record data is the >> > error >> > code. >> > >> > If this DNS server does not have any DS-integrated peers, then this >> > error >> > should be ignored. >> > >> > If this DNS server's Active Directory replication partners do not have >> > the >> > correct IP address(es) for this server, they will be unable to >> > replicate >> > with >> > it. >> > >> > To ensure proper replication: >> > 1) Find this server's Active Directory replication partners that run >> > the >> > DNS >> > server. >> > 2) Open DnsManager and connect in turn to each of the replication >> > partners. >> > 3) On each server, check the host (A record) registration for THIS >> > server. >> > 4) Delete any A records that do NOT correspond to IP addresses of this >> > server. >> > 5) If there are no A records for this server, add at least one A record >> > corresponding to an address on this server, that the replication >> > partner >> > can >> > contact. (In other words, if there multiple IP addresses for this DNS >> > server, >> > add at least one that is on the same network as the Active Directory >> > DNS >> > server you are updating.) >> > 6) Note, that is not necessary to update EVERY replication partner. It >> > is >> > only necessary that the records are fixed up on enough replication >> > partners >> > so that every server that replicates with this server will receive >> > (through >> > replication) the new data. >> > >> > I hope that the information above helps you. >> > Have a Nice day. >> > >> > Rajesh J S >> > MCSA, MCP >> > >> > >> > >> > "Dale Gibble" wrote: >> > >> >> I have a DNS server than continues to update its own DNS record to >> >> 192.168.1.50. How can I keep this from happening? >> >> >> >> >> >> >> >> >> Does the DC have two network addresses? Where is this 192.168 address coming
from and why is it wrong? Anthony http://www.airdesk.com Show quoteHide quote "Dale Gibble" <dgib***@yahoo.com> wrote in message news:uT30VFCpJHA.1252@TK2MSFTNGP03.phx.gbl... > I have a DNS server than continues to update its own DNS record to > 192.168.1.50. How can I keep this from happening? > Hello Dale,
See here: http://technet.microsoft.com/en-us/library/cc735806.aspx http://www.eventid.net/display.asp?eventid=6702&eventno=294&source=DNS&phase=1 http://www.chicagotech.net/troubleshooting/eventid6702a.htm 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 Show quoteHide quote > I have a DNS server than continues to update its own DNS record to > 192.168.1.50. How can I keep this from happening? > Without being able to review the data myself the best suggestion I have would
be to review Troubleshooting Active Directory Replication Problems at http://www.microsoft.com/technet/pro...1/adogd12.mspx I hope that the information above helps you. Have a Nice day. Rajesh J S MCSA, MCP In news:uT30VFCpJHA.1252@TK2MSFTNGP03.phx.gbl, Dale Gibble <dgib***@yahoo.com>, posted the following:> I have a DNS server than continues to update its own DNS record to Hi Dale,> 192.168.1.50. How can I keep this from happening? Please post an unedited ipconfig /all from two sample DCs. This will give us a more specific look to diagnose this issue. Has anyone changed anything in the Root Hints tab? Does that 192.168.1.50 show up in there? If so, this can cause a 6702. You can follow the following link to fix the Roots: http://support.microsoft.com/kb/249868 Is your domain a single label name? This can cause 6702's as well. The ipconfigs will help us determine this. If any of the DCs are multihomed, this will definitely cause it. DCs are not recommended for multihoming due to the additional records that get registered into DNS and providing incorrect SRV responses to clients and DCs themselves during replication and other communications. If RRAS is installed on a DC (such as for VPN use), this makes it multihomed as well as cause havoc with the additional records in DNS and will cause the same thing. RRAS and multihoming is recommended to be left to non-DCs. I hope that helps. Looking forward to your responses. -- Ace This posting is provided "AS-IS" with no warranties or guarantees and confers no rights. Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT Microsoft Certified Trainer ace***@mvps.RemoveThisPart.org For urgent issues, you may want to contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers. 
Other interesting topics
Error while trying to upgrade a Windows 2000 Server domain
Determin the Class an Attribute Belongs To Certificate Services 2008 Cannot run .EXE after joining domain search by owner Issues Possibly From Joining a Domain Network drive mapping DNS Integrations Event ID 22 on Domain Controllers (w32time) Tapi3Directory |
|||||||||||||||||||||||
