Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Server > DNS Server > Re: stand alone windows servers not registering in DNS.

Reply
Thread Tools Display Modes

Re: stand alone windows servers not registering in DNS.

 
 
Jonathan de Boyne Pollard
Guest
Posts: n/a

 
      01-27-2010
>
>
> Recently I have noticed that some of the stand alone servers are not
> registering in DNS.
>

M. Fekay has pointed you at some things to do to investigate why the
DHCP clients are not successful in registering. An alternative, of
course, is to get your DHCP server to perform the registration.

 
Reply With Quote
 
 
 
 
Ace Fekay [MVP-DS, MCT]
Guest
Posts: n/a

 
      01-27-2010
"Jonathan de Boyne Pollard" <J.deBoynePollard-> wrote
in message
news: lard.localhost...
> >
>>
>> Recently I have noticed that some of the stand alone servers are not
>> registering in DNS.
>>

> M. Fekay has pointed you at some things to do to investigate why the DHCP
> clients are not successful in registering. An alternative, of course, is
> to get your DHCP server to perform the registration.
>



Actually to point out, I posted a general guideline for dynamic
registration, DHCP or static clients. But for non-servers, I agree, DHCP
will do the job just fine.

Ace


 
Reply With Quote
 
Ace Fekay [MVP-DS, MCT]
Guest
Posts: n/a

 
      01-27-2010
"Jonathan de Boyne Pollard" <J.deBoynePollard-> wrote
in message
news: lard.localhost...
> Recently I have noticed that some of the stand alone servers are not
> registering in DNS.
>
>
> M. Fekay has pointed you at some things to do to investigate why the
> DHCP clients are not successful in registering. An alternative, of course,
> is to get your DHCP server to perform the registration.
>
>
> Actually to point out, I posted a general guideline for dynamic
> registration, DHCP or static clients. But for non-servers, I agree, DHCP
> will do the job just fine.
>
>
> By "DHCP client" I mean the DHCP client, as in the DHCP client service,
> running on all of those machines and which is responsible for Dynamic DNS
> Update registration by a workstation even if the IP address is statically
> configured. Also, by "stand-alone servers", M. Shah is talking about
> application servers, for "our in-house applications" (whatever they are),
> which are just plain old workstations as far as Active Directory is
> concerned. So I think that the issues that you quite rightly allude to
> aren't a concern for those machines. These are non-servers, from what
> (little) we're told. Having the DHCP server do the work is thus feasible.
>
>



Ok, sorry for the misunderstanding. The DHCP Client service on all machines
is important to not disable, since that is the actual registration service.

Ace


 
Reply With Quote
 
Ace Fekay [MVP-DS, MCT]
Guest
Posts: n/a

 
      01-27-2010
> On Jan 27, 9:32*am, "Ace Fekay [MVP-DS, MCT]"
> <ace...@mvps.RemoveThisPart.org> wrote:
>> "Jonathan de Boyne Pollard" <J.deBoynePollard-newsgro...@NTLWorld.COM> wrote
>> in
>> messagenews: yne.Pollard.localhost...
>>
>>
>>
>>>> Recently I have noticed that some of the stand alone servers are not
>>>> registering in DNS.

>>
>>> M. Fekay has pointed you at some things to do to investigate why the DHCP
>>> clients are not successful in registering. *An alternative, of course, is
>>> to get your DHCP server to perform the registration.

>>
>> Actually to point out, I posted a general guideline for dynamic
>> registration, DHCP or static clients. But for non-servers, I agree, DHCP
>> will do the job just fine.
>>
>> Ace

>
>
> To add to your request, the DHCP servers and DNS servers are
> 172.31.244.20, .21 and .22. The 2008 R2 machine is .22. As
> mentioned, the machine is getting all the required information from
> DHCP but not registering in DNS. The following is an ipconfig /all.
> I also reference you guideline as a checkpoint and at par.
>
> Ethernet adapter Local Area Connection 5:
>
> Connection-specific DNS Suffix . : domain.local
> Description . . . . . . . . . . . : Broadcom BCM5708S NetXtreme II
> GigE (NDI
> VBD Client) #5
> Physical Address. . . . . . . . . : 00-22-19-B5-00-CF
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IPv4 Address. . . . . . . . . . . : 172.31.244.49(Preferred)
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Lease Obtained. . . . . . . . . . : Tuesday, January 26, 2010
> 4:25:09 PM
> Lease Expires . . . . . . . . . . : Friday, January 29, 2010
> 4:25:13 PM
> Default Gateway . . . . . . . . . : 172.31.244.1
> DHCP Server . . . . . . . . . . . : 172.31.244.21
> DNS Servers . . . . . . . . . . . : 172.31.244.20
> 172.31.244.21
> NetBIOS over Tcpip. . . . . . . . : Enabled
>
> Scope Options Vendor
> Value Class
> 003 Router Standard
> 172.31.244.1 None
> 006 DNS Server Standard
> 172.31.244.20, 172.31.244.21 None
> 015 DNS Domain Name Standard
> domain.local None
>
> I check the System event viewer logs and came across the following
> during the time after the system was back up:
> 4:26:02 PM Error Event ID 7001. This is expect as I have the Base
> Engine service disabled.
> 4:26:35 PM Error Event ID 7026. stofit drivers failed to load.
>
> Let me know if you need more information.


Thanks, BlueIT for posting this. This machine apparently appears to be
fine.

I *assume* the DCs are not multihomed (a multihomed DC is defined as
having more than one NIC, IP address and/or RRAS/VPN installed), nor do
they have an outside DNS address (one that does not h ave a reference
to the domain.local zone) configured in their properties. If either is
true, it will complicate the diagnosis and may be the cause.

EventID 7001 & 7026 are generic to specific services, and from what you
mentioned, I do not believe they are related to this issue.

I assume the DHCP Client service is running on the machine. If
disabled, it will still get an IP, however it will not register.

Ace

--
Ace

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

Please reply back to the newsgroup or forum for collaboration benefit
among responding engineers, and to help others benefit from your
resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE
& MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance,
please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.


 
Reply With Quote
 
Ace Fekay [MVP-DS, MCT]
Guest
Posts: n/a

 
      01-27-2010
> On Jan 27, 11:56*am, Ace Fekay [MVP-DS, MCT]
> <ace...@mvps.RemoveThisPart.org> wrote:
>>> On Jan 27, 9:32*am, "Ace Fekay [MVP-DS, MCT]"
>>> <ace...@mvps.RemoveThisPart.org> wrote:
>>>> "Jonathan de Boyne Pollard" <J.deBoynePollard-newsgro...@NTLWorld.COM>
>>>> wrote in
>>>> messagenews: yne.Pollard.localhost...
>>>>>> Recently I have noticed that some of the stand alone servers are not
>>>>>> registering in DNS.

>>
>>>>> M. Fekay has pointed you at some things to do to investigate why the DHCP
>>>>> clients are not successful in registering. *An alternative, of course, is
>>>>> to get your DHCP server to perform the registration.
>>>> Actually to point out, I posted a general guideline for dynamic
>>>> registration, DHCP or static clients. But for non-servers, I agree, DHCP
>>>> will do the job just fine.

>>
>>>> Ace

>>
>>> To add to your request, the DHCP servers and DNS servers are
>>> 172.31.244.20, .21 and .22. *The 2008 R2 machine is .22. *As
>>> mentioned, the machine is getting all the required information from
>>> DHCP but not registering in DNS. *The following is an ipconfig /all.
>>> I also reference you guideline as a checkpoint and at par.
>>> Ethernet adapter Local Area Connection 5:
>>> * *Connection-specific DNS Suffix *. : domain.local
>>> * *Description . . . . . . . . . . . : Broadcom BCM5708S NetXtreme II
>>> GigE (NDI
>>> *VBD Client) #5
>>> * *Physical Address. . . . . . . . . : 00-22-19-B5-00-CF
>>> * *DHCP Enabled. . . . . . . . . . . : Yes
>>> * *Autoconfiguration Enabled . . . . : Yes
>>> * *IPv4 Address. . . . . . . . . . . : 172.31.244.49(Preferred)
>>> * *Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> * *Lease Obtained. . . . . . . . . . : Tuesday, January 26, 2010
>>> 4:25:09 PM
>>> * *Lease Expires . . . . . . . . . . : Friday, January 29, 2010
>>> 4:25:13 PM
>>> * *Default Gateway . . . . . . . . . : 172.31.244.1
>>> * *DHCP Server . . . . . . . . . . . : 172.31.244.21
>>> * *DNS Servers . . . . . . . . . . . : 172.31.244.20
>>> * * * * * * * * * * * * * * * * * * * *172.31.244.21
>>> * *NetBIOS over Tcpip. . . . . . . . : Enabled
>>> Scope Options * * * * * * * * * Vendor
>>> Value * * * * * * * * * * * * * * * * * * * * * * * * Class
>>> 003 Router * * * * * * * * * * * * Standard
>>> 172.31.244.1 * * * * * * * * * * * * * * * * * * * None
>>> 006 DNS Server * * * * * * * * *Standard
>>> 172.31.244.20, 172.31.244.21 * * * * * * * None
>>> 015 DNS Domain Name * * * Standard
>>> domain.local * * * * * * * * * * * * * * * * * * * None
>>> I check the System event viewer logs and came across the following
>>> during the time after the system was back up:
>>> 4:26:02 PM *Error Event ID 7001. *This is expect as I have the Base
>>> Engine service disabled.
>>> 4:26:35 PM *Error Event ID 7026. *stofit drivers failed to load.
>>> Let me know if you need more information.

>>
>> Thanks, BlueIT for posting this. This machine apparently appears to be
>> fine.
>>
>> I *assume* the DCs are not multihomed (a multihomed DC is defined as
>> having more than one NIC, IP address and/or RRAS/VPN installed), nor do
>> they have an outside DNS address (one that does not h ave a reference
>> to the domain.local zone) configured in their properties. If either is
>> true, it will complicate the diagnosis and may be the cause.
>>
>> EventID 7001 & 7026 are generic to specific services, and from what you
>> mentioned, I do not believe they are related to this issue.
>>
>> I assume the DHCP Client service is running on the machine. If
>> disabled, it will still get an IP, however it will not register.
>>
>> Ace
>>
>> --
>> Ace
>>
>> This posting is provided "AS-IS" with no warranties or guarantees and
>> confers no rights.
>>
>> Please reply back to the newsgroup or forum for collaboration benefit
>> among responding engineers, and to help others benefit from your
>> resolution.
>>
>> Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE
>> & MCSA 2003/2000, MCSA Messaging 2003
>> Microsoft Certified Trainer
>> Microsoft MVP - Directory Services
>>
>> If you feel this is an urgent issue and require immediate assistance,
>> please contact Microsoft PSS directly. Please
>> checkhttp://support.microsoft.comfor regional support phone numbers.- Hide
>> quoted text -
>>
>> - Show quoted text -

>
> Correct me if I am wrong, but I thought 2003 DHCP server does the the
> registration by default?


Well, kind of but not exactly. It depends.

By default, a Windows 2000 and newer statically configured machines
will register their A record (hostname) and PTR (reverse entry) into
DNS.

If set to DHCP, a Windows 2000 or newer machine will request DHCP to
allow the machine itself to register its own A record, but DHCP will
register its PTR (reverse entry) record.

However, there's more to it. Please read my blog on this process and
other options.

DHCP, Dynamic DNS Updates, Scavenging, static entries & timestamps, and
the DnsProxyUpdate Group (How to remove duplicate DNS host records):
http://msmvps.com/blogs/acefekay/arc...ate-group.aspx


You can *force* DHCP to do all the registration for you, as outlined in
my blog, but you need to address the dupe records created by either
using the DnsUpdateProxy group, or configuring credentials for DHCP to
own the records.

BUT, what *concerns* me is you stated these machines are imaged. Did
you use Sysprep, or are these machines mirror copies of a base image?

If mirrored copies, I can see what's going on - it has a duplcate SID.

--
Ace

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

Please reply back to the newsgroup or forum for collaboration benefit
among responding engineers, and to help others benefit from your
resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE
& MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance,
please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.


 
Reply With Quote
 
Phillip Windell
Guest
Posts: n/a

 
      01-27-2010
<Ace Fekay [MVP-DS>; "MCT]" <> wrote in
message news: t.org...
> BUT, what *concerns* me is you stated these machines are imaged. Did you
> use Sysprep, or are these machines mirror copies of a base image?
>
> If mirrored copies, I can see what's going on - it has a duplcate SID.


I've have good luck with NewSid.exe It even works with with Vista without
fouling up the activation if it was activated before the image was made.
It's freeware.

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------


 
Reply With Quote
 
Ace Fekay [MVP-DS, MCT]
Guest
Posts: n/a

 
      01-28-2010
"Jonathan de Boyne Pollard" <J.deBoynePollard-> wrote
in message
news: lard.localhost...
> BUT, what concerns me is you stated these machines are imaged. Did you
> use Sysprep, or are these machines mirror copies of a base image?
>
> If mirrored copies, I can see what's going on - it has a duplicate SID.
>
>
> I've have good luck with NewSid.exe It even works with with Vista without
> fouling up the activation if it was activated before the image was made.
> It's freeware.
>
>
> ... and Mark Russinovich explains that a lot of the thinking that
> underpins people's desire to run it in the first place appears to be
> ill-founded, with duplicate SIDs not actually being the problem they are
> often thought to be. Hence the tool being retired last year.
>
>



Maybe I should have been more specific regarding duplicate SID. My concern
was if the zone is set to allow updates for Secure Only option, a duplicate
SID may cause issues during Kerberos authentication.

Yes, I realize NewSid has been retired. It does work, however, I do not use
it and rather use Sysprep.

For others out there, the following are links on duplicate SIDs, and the
myth surrounding it that one can read up on.

NewSID v4.10, By Mark Russinovich and Bryce Cogswell, Published: November 1,
2006
Note: NewSID has been retired and is no longer available for download.
http://technet.microsoft.com/en-us/s.../bb897418.aspx

Please see Mark Russinovich’s blog post: NewSID Retirement and the Machine
SID Duplication Myth
http://blogs.technet.com/markrussino...3/3291024.aspx


The Microsoft KBs regarding duplicate SIDS not being supported have not been
retired. Apparently there must be a good reason for that.

Do not disk duplicate installed versions of WindowsCloning or duplicating an
installation without taking the recommended steps could lead to duplicate
SIDs, and in the case of removable media, ...
http://support.microsoft.com/kb/162001

The Microsoft policy concerning disk duplication of Windows XP ...In the
case of removable media, a duplicate SID might give an account access to ...
Microsoft does not support the running of Sysprep after the image is ...
http://support.microsoft.com/kb/314828

Ace


 
Reply With Quote
 
Ace Fekay [MVP-DS, MCT]
Guest
Posts: n/a

 
      01-28-2010
> On Jan 27, 3:15*pm, "Phillip Windell" <philwind...@hotmail.com> wrote:
>> <Ace Fekay [MVP-DS>; "MCT]" <ace...@mvps.RemoveThisPart.org> wrote in
>> messagenews: ThisPart.org...
>>
>>> BUT, what *concerns* me is you stated these machines are imaged. Did you
>>> use Sysprep, or are these machines mirror copies of a base image?
>>> If mirrored copies, I can see what's going on - it has a duplcate SID.

>>
>> I've have good luck with NewSid.exe *It even works with with Vista without
>> fouling up the activation if it was activated before the image was made.
>> It's freeware.
>>
>> --
>> Phillip Windell
>>
>> The views expressed, are my own and not those of my employer, or Microsoft,
>> or anyone else associated with me, including my cats.
>> -----------------------------------------------------

>
> the image was used with sysprep so that is out of the question. might
> be a whole different topic, but 2008 sysprep does differ from 2003
> sysprep. this same image i used on another machine doesn't have the
> same issue. I'll check out your blog............to be continued.



Good to hear that. As for differences, as far as I know, it acts the
same regarding resetting a machine at boot creating a new SID and other
factors during image booting.

I haven't used Sysprep with Windows 2008, however I have with Vista and
Windows 7, and they are similar, and it works fine and haven't seen
this issue using it.

Curious, just to touch base when you used Sysprep, and this is out of
curiosity, when you ran it did you use the XML answer method, or did
you use the GUI? If the GUI, I assume you selected the "Generalize"
checkbox (which generates a new SID at boot)?

Also, I found the following KB regarding this issue. It may apply to
your scenario.

A Windows Server 2008-based DHCP server does not register DNS ...Fixes
an issue in which a Windows Server 2008-based DHCP server does not
register DNS records for earlier version DHCP clients that do not send
option 81 to ...
http://support.microsoft.com/kb/967363

And I agree the extended SID topic that ensued is a completely
different topic for another time.



Ace


 
Reply With Quote
 
Ace Fekay [MVP-DS, MCT]
Guest
Posts: n/a

 
      01-28-2010
>> On Jan 27, 3:15*pm, "Phillip Windell" <philwind...@hotmail.com> wrote:
>>> <Ace Fekay [MVP-DS>; "MCT]" <ace...@mvps.RemoveThisPart.org> wrote in
>>> messagenews: ThisPart.org...
>>>
>>>> BUT, what *concerns* me is you stated these machines are imaged. Did you
>>>> use Sysprep, or are these machines mirror copies of a base image?
>>>> If mirrored copies, I can see what's going on - it has a duplcate SID.
>>>
>>> I've have good luck with NewSid.exe *It even works with with Vista without
>>> fouling up the activation if it was activated before the image was made.
>>> It's freeware.
>>>
>>> --
>>> Phillip Windell
>>>
>>> The views expressed, are my own and not those of my employer, or
>>> Microsoft,
>>> or anyone else associated with me, including my cats.
>>> -----------------------------------------------------

>>
>> the image was used with sysprep so that is out of the question. might
>> be a whole different topic, but 2008 sysprep does differ from 2003
>> sysprep. this same image i used on another machine doesn't have the
>> same issue. I'll check out your blog............to be continued.

>
>
> Good to hear that. As for differences, as far as I know, it acts the same
> regarding resetting a machine at boot creating a new SID and other factors
> during image booting.
>
> I haven't used Sysprep with Windows 2008, however I have with Vista and
> Windows 7, and they are similar, and it works fine and haven't seen this
> issue using it.
>
> Curious, just to touch base when you used Sysprep, and this is out of
> curiosity, when you ran it did you use the XML answer method, or did you use
> the GUI? If the GUI, I assume you selected the "Generalize" checkbox (which
> generates a new SID at boot)?
>
> Also, I found the following KB regarding this issue. It may apply to your
> scenario.
>
> A Windows Server 2008-based DHCP server does not register DNS ...Fixes an
> issue in which a Windows Server 2008-based DHCP server does not register DNS
> records for earlier version DHCP clients that do not send option 81 to ...
> http://support.microsoft.com/kb/967363
>
> And I agree the extended SID topic that ensued is a completely different
> topic for another time.
>
>
>
> Ace


BluetIT,

I may have posted that KB too soon. I don't think it applies. However,
I've found the following articles that may be of interest.

Sysprep Networking section does not apply - Update to register with DNS
....
http://www.techtalkz.com/windows-dep...not-apply.html

Also, something else to look into. Thinking back a few weeks ago, I
believe I remember someone posting in another group a similar issue
with Windows 7 not registering. IIRC, from what I remember of the
issue, is I believe that Windows 7 either does not set "register this
connection" or it does not set "append primary DNS" suffix by default
on a fresh installation.

Ace


 
Reply With Quote
 
Ace Fekay [MVP-DS, MCT]
Guest
Posts: n/a

 
      01-28-2010
> On Jan 28, 12:04*pm, BlueIT <bijal.s...@bluecg.com> wrote:
>> On Jan 27, 8:59*pm, Ace Fekay [MVP-DS, MCT]
>>
>>
>>
>>
>>
>> <ace...@mvps.RemoveThisPart.org> wrote:
>>>>> On Jan 27, 3:15*pm, "Phillip Windell" <philwind...@hotmail.com> wrote:
>>>>>> <Ace Fekay [MVP-DS>; "MCT]" <ace...@mvps.RemoveThisPart.org> wrote in
>>>>>> messagenews: ThisPart.org...
>>>>>>> BUT, what *concerns* me is you stated these machines are imaged. Did
>>>>>>> you use Sysprep, or are these machines mirror copies of a base image?
>>>>>>> If mirrored copies, I can see what's going on - it has a duplcate SID.
>>>>>> I've have good luck with NewSid.exe *It even works with with Vista
>>>>>> without fouling up the activation if it was activated before the image
>>>>>> was made. It's freeware.

>>
>>>>>> --
>>>>>> Phillip Windell

>>
>>>>>> The views expressed, are my own and not those of my employer, or
>>>>>> Microsoft,
>>>>>> or anyone else associated with me, including my cats.
>>>>>> -----------------------------------------------------
>>>>> the image was used with sysprep so that is out of the question. *might
>>>>> be a whole different topic, but 2008 sysprep does differ from 2003
>>>>> sysprep. *this same image i used on another machine doesn't have the
>>>>> same issue. *I'll check out your blog............to be continued.
>>>> Good to hear that. As for differences, as far as I know, it acts the same
>>>> regarding resetting a machine at boot creating a new SID and other factors
>>>> during image booting.

>>
>>>> I haven't used Sysprep with Windows 2008, however I have with Vista and
>>>> Windows 7, and they are similar, and it works fine and haven't seen this
>>>> issue using it.

>>
>>>> Curious, just to touch base when you used Sysprep, and this is out of
>>>> curiosity, when you ran it did you use the XML answer method, or did you
>>>> use the GUI? If the GUI, I assume you selected the "Generalize" checkbox
>>>> (which generates a new SID at boot)?

>>
>>>> Also, I found the following KB regarding this issue. It may apply to your
>>>> scenario.

>>
>>>> A Windows Server 2008-based DHCP server does not register DNS ...Fixes an
>>>> issue in which a Windows Server 2008-based DHCP server does not register
>>>> DNS records for earlier version DHCP clients that do not send option 81 to
>>>> ... http://support.microsoft.com/kb/967363
>>>> And I agree the extended SID topic that ensued is a completely different
>>>> topic for another time.

>>
>>>> Ace

>>
>>> BluetIT,

>>
>>> I may have posted that KB too soon. I don't think it applies. However,
>>> I've found the following articles that may be of interest.
>>> Sysprep Networking section does not apply - Update to register with DNS
>>> ...http://www.techtalkz.com/windows-dep...rep-networking...
>>> Also, something else to look into. Thinking back a few weeks ago, I
>>> believe I remember someone posting in another group a similar issue
>>> with Windows 7 not registering. IIRC, from what I remember of the
>>> issue, is I believe that Windows 7 either does not set "register this
>>> connection" or it does not set "append primary DNS" suffix by default
>>> on a fresh installation.

>>
>>> Ace- Hide quoted text -

>>
>>> - Show quoted text -

>>
>> Altough newsid has saved me in the past, didn't work well for 2008 R2
>> and Win7 for me. *I believed it cause the infamous BSOD. *As for
>> sysprep, I use the GUI that is local to the machine. *There are only
>> two System Cleanup Actions:
>>
>> 1. *Enter System Out-of-Box Experience (OOBE).
>> 2. *Enter System Audit Mode.
>>
>> Don't have option for generating new SID as was the case for 2003
>> sysprep. *That is why I mention it has change is previous post. *The
>> zone is definately set up for Secure Only option, although I use
>> sysprep I should not need to worry but still have to consider that as
>> a reason.
>>
>> I went through the three DHCP servers and set each to "Always
>> dynamically update DNS A and PTR records." *I have always used the
>> default. *Will look at the links you provided.
>>
>> Thanks- Hide quoted text -
>>
>> - Show quoted text -

>
> forgot to mention, nslookup by IP works. Reverse lookup zone seems to
> be accurate, just not the forward.


Actually, with Sysprep, if you check the 'generalize' checkbox, it
creates a new SID upon boot.

If reverse works, it appears DHCP is registering that record, but the
machine may not be asking DHCP. If you set DHCP to force, I am curious
if that works.

Also, did you check those settings in the NIC's properties? ("register
this connection" and "append primary DNS" suffix.)

--
Ace


 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
I also have an error 646 in Windows update. Please help. Jose Windows Update 12 01-09-2010 01:00 PM
"Some updates could not be installed" Antnee20x Windows Update 7 12-18-2009 07:01 PM
Can I use the Windows 7 Upgrade DVD for a Clean Install ? Patrick Windows Vista General Discussion 38 11-11-2009 09:41 PM
Run Vista legally for at least one year/ Vista Activation doesn't stop Piracy Chad Harris Windows Vista Installation 56 12-25-2008 01:34 PM
How do you repair windows entirely using your Windows Vista DVD Jonathan Yaniv- Windows Live Butterfly Expert Windows Vista Performance 16 02-12-2008 06:28 PM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59