search for: aarrggh

...way to register himself. > > b) client use as DNS to register some ''random'' DNS, and seems to > keep them for some time... > > > Currently i've machine on site A that register on site C, and machine > of site B that register on site A. > > > AARRGGH! ;-) > Yes, 'AARRGGH' indeed ;-) For a computer to update its records, the records must be owned by the computer or the computer will be denied. You seem to be running a strange DNS setup, where the dhcp server is sending one dns domain, but the AD domain is in another one, not sure...

Mandi! Rowland Penny via samba In chel di` si favelave... > This is probably where you are going wrong. AD lives and dies on DNS, > your DC MUST be authoritative for the AD domain. ...but *is* authoritative! Simply DHCP server assign the ''old'' DNS, where all resolution fr the AD (sub)domain are forwarded to AD DNS... > Your AD clients should be using the DC as

...t agent so it can read out the required IP address from a temporary file and set up the network that way, although that it not very different from the patch I proposed, except using an agent instead of a hacky Powershell script. I'm also now hearing that some customers regard DHCP as insecure. Aarrggh. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests...

...by DHCP CAN not be the AD DNS, and client find a way to register himself. b) client use as DNS to register some ''random'' DNS, and seems to keep them for some time... Currently i've machine on site A that register on site C, and machine of site B that register on site A. AARRGGH! ;-) -- dott. Marco Gaiarin GNUPG Key ID: 240A3D66 Associazione ``La Nostra Famiglia'' http://www.lanostrafamiglia.it/ Polo FVG - Via della Bontà, 7 - 33078 - San Vito al Tagliamento (PN) marco.gaiarin(at)lanostrafamiglia.it t +39-0434-842711 f +39-04...

...use as DNS to register some ''random'' DNS, and seems to > > keep them for some time... > > > > > > Currently i've machine on site A that register on site C, > and machine > > of site B that register on site A. > > > > > > AARRGGH! ;-) > > > > Yes, 'AARRGGH' indeed ;-) > > For a computer to update its records, the records must be owned by the > computer or the computer will be denied. > > You seem to be running a strange DNS setup, where the dhcp server is > sending one dns domain, b...