PHWinfo banniere

Titres
PORTAIL ANNUAIRE ARTICLES COMPARATEUR HÉBERGEURS DEVIS FORUMS RÉDUCTEUR D'URL
Précédent   PHWinfo > Forums Hébergement > Forum Noms de domaine > ms.public.win.server.dns > Made stupid change to DNS; me fix my problem.
S'inscrire FAQ Membres Recherche Messages du jour Marquer les forums comme lus
Made stupid change to DNS; me fix my problem.

Réponse
 
LinkBack Outils de la discussion
Vieux 28/01/2008, 14h49   #1
DNS_Help
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Made stupid change to DNS; me fix my problem.

Last week we were having issues with our ISP's DNS so I pushed a GP to
set our primary DNS to use OpenDNS. Obviously this broke active
directory. So I changed the GP back. But all my Xp clients that were
pushed the GP update needed to be fixed. After disjoining and
rejoining to the domain their DNS was set back to our internal DNS
servers. I am having trouble with one laptop. No matter what I do I
cannot get the laptop to forward DNS queries to our internal name
server. From the command prompt if I type nslookup it still displays
the open DNS name server. If I do an IPCONFIG /all my internal dns
servers are listed as the primary and secondary servers but if I try
to ping an internal server the client still attempts to query
openDNS. Can I force my client to use the internal DNS servers? Any
suggestions?
  Réponse avec citation
Vieux 28/01/2008, 16h14   #2
Lanwench [MVP - Exchange]
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Made stupid change to DNS; me fix my problem.

DNS_ <peter.zelonis@gmail.com> wrote:
> Last week we were having issues with our ISP's DNS so I pushed a GP to
> set our primary DNS to use OpenDNS. Obviously this broke active
> directory. So I changed the GP back. But all my Xp clients that were
> pushed the GP update needed to be fixed. After disjoining and
> rejoining to the domain their DNS was set back to our internal DNS
> servers. I am having trouble with one laptop. No matter what I do I
> cannot get the laptop to forward DNS queries to our internal name
> server. From the command prompt if I type nslookup it still displays
> the open DNS name server. If I do an IPCONFIG /all my internal dns
> servers are listed as the primary and secondary servers but if I try
> to ping an internal server the client still attempts to query
> openDNS. Can I force my client to use the internal DNS servers? Any
> suggestions?


Your workstations & servers shouldn't be using public DNS servers, ever,
since you're using AD. This will cause you no end of trouble. Instead, your
internal DNS server should be set with forwarders to the appropriate public
DNS servers, which you can easily change whenever you wish with little
disruption to your network.

Try posting an unedited ipconfig /all from a problem workstation (clearly
labeled "workstation") and from a DC (
" " )

Also curious as to why you'd be using group policy (netsh commands??)
instead of DHCP for this.


  Réponse avec citation
Vieux 28/01/2008, 19h13   #3
Kevin D. Goodknecht Sr. [MVP]
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Made stupid change to DNS; me fix my problem.

Read inline please.

In news:0cca10d2-2a66-472c-9324-2989d4746610@k2g2000hse.googlegroups.com,
DNS_ <peter.zelonis@gmail.com> typed:
> Last week we were having issues with our ISP's DNS so I pushed a GP to
> set our primary DNS to use OpenDNS. Obviously this broke active
> directory. So I changed the GP back. But all my Xp clients that were
> pushed the GP update needed to be fixed. After disjoining and
> rejoining to the domain their DNS was set back to our internal DNS
> servers. I am having trouble with one laptop. No matter what I do I
> cannot get the laptop to forward DNS queries to our internal name
> server. From the command prompt if I type nslookup it still displays
> the open DNS name server. If I do an IPCONFIG /all my internal dns
> servers are listed as the primary and secondary servers but if I try
> to ping an internal server the client still attempts to query
> openDNS. Can I force my client to use the internal DNS servers? Any
> suggestions?


By using a group policy to set DNS servers, all clients will use DNS servers
in the policy. You should not use an external DNS server on any member
client of an AD Domain.

--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This s

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oe.com/OEBackup/Default.aspx
===================================


  Réponse avec citation
Réponse


Outils de la discussion

Règles de messages
Vous ne pouvez pas créer de nouvelles discussions
Vous ne pouvez pas envoyer des réponses
Vous ne pouvez pas envoyer des pièces jointes
Vous ne pouvez pas modifier vos messages

Les balises BB sont activées : oui
Les smileys sont activés : oui
La balise [IMG] est activée : oui
Le code HTML peut être employé : non
Trackbacks are oui
Pingbacks are oui
Refbacks are oui


Fuseau horaire GMT +1. Il est actuellement 13h08.


Édité par : vBulletin® version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.2.0 RC5 Tous droits réservés.
Version française #16 par l'association vBulletin francophone
PHWinfo est un site Éducation Sans Frontières ©2000-2008
Ad Management by RedTyger
©Tous droits réservés par les parties respectives
Page generated in 0,09158 seconds with 11 queries