I started working on a DNS that is acting a bit strange. When I add a new
device to the network the DNS is not automatically creating an A record for
the device. However I can ping the device by it FQDN. Secondly when I
manally add an A record to the DNS I cannot ping by the FQDN. I ran dcdiag
testNS but it did not find any problems. any will be greatly
appreciated

You can probably ping it because of WINS or broadcasting.

What happens when you do an nslookup both forward and reverse on a problem
name?

Enabling Dynamic DNS
http://support.microsoft.com/kb/246804

--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

"Joe McHale" <JoeMcHale@discussions.microsoft.com> wrote in message
newsAA59583-1F78-421C-9222-4117FB88675E@microsoft.com...
>I started working on a DNS that is acting a bit strange. When I add a new
> device to the network the DNS is not automatically creating an A record
> for
> the device. However I can ping the device by it FQDN. Secondly when I
> manally add an A record to the DNS I cannot ping by the FQDN. I ran dcdiag
> testNS but it did not find any problems. any will be greatly
> appreciated

As Paul mentions, NSLOOKUP is really the best way to see if there is an issue
with DNS. This will give you the ability to check DNS and even to bind to
your DNS servers one at a time to see if there are any DNS servers that are
not updating correctly.

If you are using AD Integrated DNS, a missing DNS record could be indicative
of a replication problem in your domain and may be an early warning of
trouble. In a standard DNS configuration, the step that is often missed is
the configuration of notification so that downstream partners are notified of
changes rather than relying on them querying for changes.

There is also the question of how you expect these updates to get there.
If you are using older clients (Win 98/ Me) they will need to have DHCP
register in DNS rather than relying on the clients themselves. You may want
to set that to update DNS if the client doesn't do it anyway.

Cheers,
--
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
http://www.techsterity.com
Chicago, IL

Remember: Marking ful answers s everyone find the info they need
quickly.


"Joe McHale" wrote:

> I started working on a DNS that is acting a bit strange. When I add a new
> device to the network the DNS is not automatically creating an A record for
> the device. However I can ping the device by it FQDN. Secondly when I
> manually add an A record to the DNS I cannot ping by the FQDN. I ran DCDiag
> testNS but it did not find any problems. any will be greatly
> appreciated

thanks to both of you who responded. yes, I believe there is a problem with
the domain. I removed one of my two dns servers and re-installed DNS on a
third separate server. This server seems to be receiviving dynamic updates. I
compared the settings between the new server and the settings on the domain
controller running DNS. I can find no differences but the domain controller
is not accepting dynamic updates.

"Ryan Hanisco" wrote:

> As Paul mentions, NSLOOKUP is really the best way to see if there is an issue
> with DNS. This will give you the ability to check DNS and even to bind to
> your DNS servers one at a time to see if there are any DNS servers that are
> not updating correctly.
>
> If you are using AD Integrated DNS, a missing DNS record could be indicative
> of a replication problem in your domain and may be an early warning of
> trouble. In a standard DNS configuration, the step that is often missed is
> the configuration of notification so that downstream partners are notified of
> changes rather than relying on them querying for changes.
>
> There is also the question of how you expect these updates to get there.
> If you are using older clients (Win 98/ Me) they will need to have DHCP
> register in DNS rather than relying on the clients themselves. You may want
> to set that to update DNS if the client doesn't do it anyway.
>
> Cheers,
> --
> Ryan Hanisco
> MCSE, MCTS: SQL 2005, Project+
> http://www.techsterity.com
> Chicago, IL
>
> Remember: Marking ful answers s everyone find the info they need
> quickly.
>
>
> "Joe McHale" wrote:
>
> > I started working on a DNS that is acting a bit strange. When I add a new
> > device to the network the DNS is not automatically creating an A record for
> > the device. However I can ping the device by it FQDN. Secondly when I
> > manually add an A record to the DNS I cannot ping by the FQDN. I ran DCDiag
> > testNS but it did not find any problems. any will be greatly
> > appreciated

Just following up...

You mentioned that one is new. Did the results if the NSLOOKUP show that
only the one is having issues and that the others are fine?
--
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
http://www.techsterity.com
Chicago, IL

Remember: Marking ful answers s everyone find the info they need
quickly.


"Joe McHale" wrote:

> thanks to both of you who responded. yes, I believe there is a problem with
> the domain. I removed one of my two dns servers and re-installed DNS on a
> third separate server. This server seems to be receiviving dynamic updates. I
> compared the settings between the new server and the settings on the domain
> controller running DNS. I can find no differences but the domain controller
> is not accepting dynamic updates.
>
> "Ryan Hanisco" wrote:
>
> > As Paul mentions, NSLOOKUP is really the best way to see if there is an issue
> > with DNS. This will give you the ability to check DNS and even to bind to
> > your DNS servers one at a time to see if there are any DNS servers that are
> > not updating correctly.
> >
> > If you are using AD Integrated DNS, a missing DNS record could be indicative
> > of a replication problem in your domain and may be an early warning of
> > trouble. In a standard DNS configuration, the step that is often missed is
> > the configuration of notification so that downstream partners are notified of
> > changes rather than relying on them querying for changes.
> >
> > There is also the question of how you expect these updates to get there.
> > If you are using older clients (Win 98/ Me) they will need to have DHCP
> > register in DNS rather than relying on the clients themselves. You may want
> > to set that to update DNS if the client doesn't do it anyway.
> >
> > Cheers,
> > --
> > Ryan Hanisco
> > MCSE, MCTS: SQL 2005, Project+
> > http://www.techsterity.com
> > Chicago, IL
> >
> > Remember: Marking ful answers s everyone find the info they need
> > quickly.
> >
> >
> > "Joe McHale" wrote:
> >
> > > I started working on a DNS that is acting a bit strange. When I add a new
> > > device to the network the DNS is not automatically creating an A record for
> > > the device. However I can ping the device by it FQDN. Secondly when I
> > > manually add an A record to the DNS I cannot ping by the FQDN. I ran DCDiag
> > > testNS but it did not find any problems. any will be greatly
> > > appreciated

Make sure the correct domain suffix is entered into the nic config of the
w/s. Then ensure you have selected the "Register this connection's address
in DNS" as well.
["Unless there is only one domain controller in the domain, the
infrastructure master role should not be assigned to the domain controller
that is hosting the global catalog. If the infrastructure master and global
catalog are on the same domain controller, the infrastructure master will
not function. The infrastructure master will never find data that is out of
date, so will never replicate any changes to the other domain controllers in
the domain. " -
http://www.microsoft.com/windows/win...DgcInffsmo.htm ]



"Joe McHale" <JoeMcHale@discussions.microsoft.com> wrote in message
newsAA59583-1F78-421C-9222-4117FB88675E@microsoft.com...
> I started working on a DNS that is acting a bit strange. When I add a new
> device to the network the DNS is not automatically creating an A record
> for
> the device. However I can ping the device by it FQDN. Secondly when I
> manally add an A record to the DNS I cannot ping by the FQDN. I ran dcdiag
> testNS but it did not find any problems. any will be greatly
> appreciated

NB: the Infrastructure Master/ GC conflict issue goes away if all DCs are GCs.
--
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
http://www.techsterity.com
Chicago, IL

Remember: Marking ful answers s everyone find the info they need
quickly.


"patrick@iQor.com" wrote:

> Make sure the correct domain suffix is entered into the nic config of the
> w/s. Then ensure you have selected the "Register this connection's address
> in DNS" as well.
> ["Unless there is only one domain controller in the domain, the
> infrastructure master role should not be assigned to the domain controller
> that is hosting the global catalog. If the infrastructure master and global
> catalog are on the same domain controller, the infrastructure master will
> not function. The infrastructure master will never find data that is out of
> date, so will never replicate any changes to the other domain controllers in
> the domain. " -
> http://www.microsoft.com/windows/win...DgcInffsmo.htm ]
>
>
>
> "Joe McHale" <JoeMcHale@discussions.microsoft.com> wrote in message
> newsAA59583-1F78-421C-9222-4117FB88675E@microsoft.com...
> > I started working on a DNS that is acting a bit strange. When I add a new
> > device to the network the DNS is not automatically creating an A record
> > for
> > the device. However I can ping the device by it FQDN. Secondly when I
> > manally add an A record to the DNS I cannot ping by the FQDN. I ran dcdiag
> > testNS but it did not find any problems. any will be greatly
> > appreciated
>

Not according to MS

"Ryan Hanisco" <RyanHanisco@discussions.microsoft.com> wrote in message
news:3124A9B4-D7BE-4F0C-92F0-CD5B10E2AECE@microsoft.com...
> NB: the Infrastructure Master/ GC conflict issue goes away if all DCs are
> GCs.
> --
> Ryan Hanisco
> MCSE, MCTS: SQL 2005, Project+
> http://www.techsterity.com
> Chicago, IL
>
> Remember: Marking ful answers s everyone find the info they need
> quickly.
>
>
> "patrick@iQor.com" wrote:
>
>> Make sure the correct domain suffix is entered into the nic config of the
>> w/s. Then ensure you have selected the "Register this connection's
>> address
>> in DNS" as well.
>> ["Unless there is only one domain controller in the domain, the
>> infrastructure master role should not be assigned to the domain
>> controller
>> that is hosting the global catalog. If the infrastructure master and
>> global
>> catalog are on the same domain controller, the infrastructure master will
>> not function. The infrastructure master will never find data that is out
>> of
>> date, so will never replicate any changes to the other domain controllers
>> in
>> the domain. " -
>> http://www.microsoft.com/windows/win...DgcInffsmo.htm ]
>>
>>
>>
>> "Joe McHale" <JoeMcHale@discussions.microsoft.com> wrote in message
>> newsAA59583-1F78-421C-9222-4117FB88675E@microsoft.com...
>> > I started working on a DNS that is acting a bit strange. When I add a
>> > new
>> > device to the network the DNS is not automatically creating an A record
>> > for
>> > the device. However I can ping the device by it FQDN. Secondly when I
>> > manally add an A record to the DNS I cannot ping by the FQDN. I ran
>> > dcdiag
>> > testNS but it did not find any problems. any will be greatly
>> > appreciated
>>