DNS not dynamically updating clients

[Guest]

Thanks for all you r help in this matter.

Current Configuration:
Primary DNS, DHCP, WINS - 2K3 server - member server on NT40 domain
Secondary DNS, WINS - 2K3 server - member server on NT40 domain
Workstation clients - All Windows XP Pro

I have all the neccessary configurations set in DHCP to dynamically update
the DNS servers but it is not working. The Primary DNS server is working
without any errors. We did however, change the name of the SOA to NS1
instead of using the name of the server. Could this be the problem? We are
not using the DNS registration credentials in the DHCP Advanced options.

The Primary and Secondary DNS servers are pointing repectively to themselves
in IP Config for thier preferred DNS with no alternate DNS.

The errors in in the DHCP log I am getting is as follows:
31,04/28/06,00:20:25,DNS Update Failed,10.100.101.91,IT-10058.,-1,
31,04/28/06,00:20:25,DNS Update Failed,10.100.101.92,it-10131.,-1,
31,04/28/06,00:20:25,DNS Update Failed,10.100.101.93,IT-10127.,-1,

It looks like DHCP is trying to update DNS but fails. Any ideas? Thanks.

 

[Herb Martin]

Thanks for all you r help in this matter.

Current Configuration:
Primary DNS, DHCP, WINS - 2K3 server - member server on NT40 domain
Secondary DNS, WINS - 2K3 server - member server on NT40 domain
Workstation clients - All Windows XP Pro

Is your primary Zone set to allow updates?

I have all the neccessary configurations set in DHCP to dynamically update
the DNS servers but it is not working.

When you say "all the necessary..." we cannot really help
you. Unless you list those we have to presume you know
and have everything correct.

The Primary DNS server is working
without any errors. We did however, change the name of the SOA to NS1
instead of using the name of the server. Could this be the problem?

Probably not, with one exception: If the DHCP server
is set to use the Secondary, and the SOA record lists the Master
under a name which is NOT resolvable to an IP (i.e., no A record
for the Primary which accepts the dynamic updates.)
(Maybe even if it is set to use the Primary.)

How does the DHCP FIND the Dynamic Master (i.e., the Primary)?

We are
not using the DNS registration credentials in the DHCP Advanced options.

That shouldn't matter since (presumable in an NT domain) you
don't have AD Integrated DNS and thus don't have "secure updates"
enabled.

Those credentials only matter for secure updates. (And although I
don't know this, I would be unsurprised if using them when not
necessary confused the DHCP server.)

The Primary and Secondary DNS servers are pointing repectively to
themselves
in IP Config for thier preferred DNS with no alternate DNS.

That's irrelevant to all except those two specific servers.

Where is the DHCP server pointed and how can it resolve
to FIND the DYNAMIC Primary DNS server?

The errors in in the DHCP log I am getting is as follows:
31,04/28/06,00:20:25,DNS Update Failed,10.100.101.91,IT-10058.,-1,
31,04/28/06,00:20:25,DNS Update Failed,10.100.101.92,it-10131.,-1,
31,04/28/06,00:20:25,DNS Update Failed,10.100.101.93,IT-10127.,-1,

You might not want to truncate those line.

It looks like DHCP is trying to update DNS but fails. Any ideas? Thanks.

It's probably not finding the DYNAMIC Primary for the zone.

 

[Guest]

Thanks for your reply.

1. DNS is set for nonsecure and secure updates
2. I am sure what you asking when you want to know how DHCP finds Dynamic
master. ie. Primary DNS. I listed the scope options below if this helps:
- 003 Router
- 006 DNS Server - Added Primary and Secondary DNS here
- 044 WINS Svr
- 046 Wins Node - 0x8
- 001 MS Disable Netbios - 0x1

DHCP Server Options enabled:
1. Enable DNS dynamic update
a. Dynamically update DNS A and PTR records if requested
2. Discard A and PTR records
3. Update DNS for clients that do not request

The DHCP and Primary DNS reside on the same server. Thanks for all your help.

Thanks for all you r help in this matter.

Current Configuration:
Primary DNS, DHCP, WINS - 2K3 server - member server on NT40 domain
Secondary DNS, WINS - 2K3 server - member server on NT40 domain
Workstation clients - All Windows XP Pro

Is your primary Zone set to allow updates?

I have all the neccessary configurations set in DHCP to dynamically update
the DNS servers but it is not working.

When you say "all the necessary..." we cannot really help
you. Unless you list those we have to presume you know
and have everything correct.

The Primary DNS server is working
without any errors. We did however, change the name of the SOA to NS1
instead of using the name of the server. Could this be the problem?

Probably not, with one exception: If the DHCP server
is set to use the Secondary, and the SOA record lists the Master
under a name which is NOT resolvable to an IP (i.e., no A record
for the Primary which accepts the dynamic updates.)
(Maybe even if it is set to use the Primary.)

How does the DHCP FIND the Dynamic Master (i.e., the Primary)?

We are
not using the DNS registration credentials in the DHCP Advanced options.

That shouldn't matter since (presumable in an NT domain) you
don't have AD Integrated DNS and thus don't have "secure updates"
enabled.

Those credentials only matter for secure updates. (And although I
don't know this, I would be unsurprised if using them when not
necessary confused the DHCP server.)

The Primary and Secondary DNS servers are pointing repectively to
themselves
in IP Config for thier preferred DNS with no alternate DNS.

That's irrelevant to all except those two specific servers.

Where is the DHCP server pointed and how can it resolve
to FIND the DYNAMIC Primary DNS server?

The errors in in the DHCP log I am getting is as follows:
31,04/28/06,00:20:25,DNS Update Failed,10.100.101.91,IT-10058.,-1,
31,04/28/06,00:20:25,DNS Update Failed,10.100.101.92,it-10131.,-1,
31,04/28/06,00:20:25,DNS Update Failed,10.100.101.93,IT-10127.,-1,

You might not want to truncate those line.

It looks like DHCP is trying to update DNS but fails. Any ideas? Thanks.

It's probably not finding the DYNAMIC Primary for the zone.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

 

[Guest]

I also want to verify that we currently have an NT40 domain in place. In
which when I restart the DNS service I get the infamous "your host is a
single name domain" error. I have the fix for this via technet article:

http://support.microsoft.com/kb/888048/en-us

Should I make these changes?

Also, since we do not have AD yet should I go ahead and still authorize the
DHCP server?

 

[Herb Martin]

Thanks for your reply.

1. DNS is set for nonsecure and secure updates
2. I am sure what you asking when you want to know how DHCP finds Dynamic
master. ie. Primary DNS. I listed the scope options below if this helps:
- 003 Router
- 006 DNS Server - Added Primary and Secondary DNS here
- 044 WINS Svr
- 046 Wins Node - 0x8
- 001 MS Disable Netbios - 0x1

How about the DNS Domain name/suffix? (option 015 )

Otherwise it won't know which zone to register in.

Make sure the clients and the DHCP server are also
in this DNS domain in the SYSTEM CONTROL panel.
(not the NIC suffixes.)

DHCP Server Options enabled:
1. Enable DNS dynamic update
a. Dynamically update DNS A and PTR records if requested
2. Discard A and PTR records
3. Update DNS for clients that do not request

This part is for NT/9x

The DHCP and Primary DNS reside on the same server. Thanks for all your
help.

Also from your other message there are issues with
SINGLE LABEL DNS domain names and dynamic
registration.

Your zone should have at least two labels but you
might look into the fixes in the Knowledge base:

Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]



--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Thanks for all you r help in this matter.

Current Configuration:
Primary DNS, DHCP, WINS - 2K3 server - member server on NT40 domain
Secondary DNS, WINS - 2K3 server - member server on NT40 domain
Workstation clients - All Windows XP Pro

Is your primary Zone set to allow updates?

I have all the neccessary configurations set in DHCP to dynamically
update
the DNS servers but it is not working.

When you say "all the necessary..." we cannot really help
you. Unless you list those we have to presume you know
and have everything correct.

The Primary DNS server is working
without any errors. We did however, change the name of the SOA to NS1
instead of using the name of the server. Could this be the problem?

Probably not, with one exception: If the DHCP server
is set to use the Secondary, and the SOA record lists the Master
under a name which is NOT resolvable to an IP (i.e., no A record
for the Primary which accepts the dynamic updates.)
(Maybe even if it is set to use the Primary.)

How does the DHCP FIND the Dynamic Master (i.e., the Primary)?

We are
not using the DNS registration credentials in the DHCP Advanced
options.

That shouldn't matter since (presumable in an NT domain) you
don't have AD Integrated DNS and thus don't have "secure updates"
enabled.

Those credentials only matter for secure updates. (And although I
don't know this, I would be unsurprised if using them when not
necessary confused the DHCP server.)

The Primary and Secondary DNS servers are pointing repectively to
themselves
in IP Config for thier preferred DNS with no alternate DNS.

That's irrelevant to all except those two specific servers.

Where is the DHCP server pointed and how can it resolve
to FIND the DYNAMIC Primary DNS server?

The errors in in the DHCP log I am getting is as follows:
31,04/28/06,00:20:25,DNS Update Failed,10.100.101.91,IT-10058.,-1,
31,04/28/06,00:20:25,DNS Update Failed,10.100.101.92,it-10131.,-1,
31,04/28/06,00:20:25,DNS Update Failed,10.100.101.93,IT-10127.,-1,

You might not want to truncate those line.

It looks like DHCP is trying to update DNS but fails. Any ideas?
Thanks.

It's probably not finding the DYNAMIC Primary for the zone.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

 

[Guest]

Thanks for all your help. I added the 015 DNS Domain Name to our DHCP
server. I also found out that 2000 SP4 and XP clients do not by default
dynamically update to single level domains unless you add the registry hack.
I already see 1 NT40 workstation we had left register on our DNS.

I just have 1 more question, If I wanted to make dynamic updates work before
we upgrade to AD can I just go ahead and rename our Primary DNS server to
name.mydomain.local. - this is the naming convention we are going to use
with AD. It is already joined to our NT40 domain, so could I trick this 2K3
member server by just renameing it?

Thanks for your reply.

1. DNS is set for nonsecure and secure updates
2. I am sure what you asking when you want to know how DHCP finds Dynamic
master. ie. Primary DNS. I listed the scope options below if this helps:
- 003 Router
- 006 DNS Server - Added Primary and Secondary DNS here
- 044 WINS Svr
- 046 Wins Node - 0x8
- 001 MS Disable Netbios - 0x1

How about the DNS Domain name/suffix? (option 015 )

Otherwise it won't know which zone to register in.

Make sure the clients and the DHCP server are also
in this DNS domain in the SYSTEM CONTROL panel.
(not the NIC suffixes.)

DHCP Server Options enabled:
1. Enable DNS dynamic update
a. Dynamically update DNS A and PTR records if requested
2. Discard A and PTR records
3. Update DNS for clients that do not request

This part is for NT/9x

The DHCP and Primary DNS reside on the same server. Thanks for all your
help.

Also from your other message there are issues with
SINGLE LABEL DNS domain names and dynamic
registration.

Your zone should have at least two labels but you
might look into the fixes in the Knowledge base:

Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]



--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Thanks for all you r help in this matter.

Current Configuration:
Primary DNS, DHCP, WINS - 2K3 server - member server on NT40 domain
Secondary DNS, WINS - 2K3 server - member server on NT40 domain
Workstation clients - All Windows XP Pro

Is your primary Zone set to allow updates?

I have all the neccessary configurations set in DHCP to dynamically
update
the DNS servers but it is not working.

When you say "all the necessary..." we cannot really help
you. Unless you list those we have to presume you know
and have everything correct.


The Primary DNS server is working
without any errors. We did however, change the name of the SOA to NS1
instead of using the name of the server. Could this be the problem?

Probably not, with one exception: If the DHCP server
is set to use the Secondary, and the SOA record lists the Master
under a name which is NOT resolvable to an IP (i.e., no A record
for the Primary which accepts the dynamic updates.)
(Maybe even if it is set to use the Primary.)

How does the DHCP FIND the Dynamic Master (i.e., the Primary)?

We are
not using the DNS registration credentials in the DHCP Advanced
options.

That shouldn't matter since (presumable in an NT domain) you
don't have AD Integrated DNS and thus don't have "secure updates"
enabled.

Those credentials only matter for secure updates. (And although I
don't know this, I would be unsurprised if using them when not
necessary confused the DHCP server.)

The Primary and Secondary DNS servers are pointing repectively to
themselves
in IP Config for thier preferred DNS with no alternate DNS.

That's irrelevant to all except those two specific servers.

Where is the DHCP server pointed and how can it resolve
to FIND the DYNAMIC Primary DNS server?

The errors in in the DHCP log I am getting is as follows:
31,04/28/06,00:20:25,DNS Update Failed,10.100.101.91,IT-10058.,-1,
31,04/28/06,00:20:25,DNS Update Failed,10.100.101.92,it-10131.,-1,
31,04/28/06,00:20:25,DNS Update Failed,10.100.101.93,IT-10127.,-1,

You might not want to truncate those line.


It looks like DHCP is trying to update DNS but fails. Any ideas?
Thanks.

It's probably not finding the DYNAMIC Primary for the zone.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

 

[Herb Martin]

Thanks for all your help. I added the 015 DNS Domain Name to our DHCP
server. I also found out that 2000 SP4 and XP clients do not by default
dynamically update to single level domains unless you add the registry
hack.
I already see 1 NT40 workstation we had left register on our DNS.

I just have 1 more question, If I wanted to make dynamic updates work
before
we upgrade to AD can I just go ahead and rename our Primary DNS server to
name.mydomain.local. - this is the naming convention we are going to use
with AD. It is already joined to our NT40 domain, so could I trick this
2K3
member server by just renameing it?

It really has nothing to do with the NAME OF THE DNS
server. It has to do with the name of the ZONE, and the
DNS domain of the clients (and specified by DHCP.)

Now, technically the DNS server is (going to be) a
domain member and DNS client eventually too, but
the registration is not dependent on that, or its name.

(Real analogy: You could have a Unix box with an
arbitrary name doing this if it had a dynamic zone that
matched the client DNS name -- I am not recommending
this, just pointing out that the DNS server, especially
its own nam, it irrelevant if it can do the task.)



--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Thanks for your reply.

1. DNS is set for nonsecure and secure updates
2. I am sure what you asking when you want to know how DHCP finds
Dynamic
master. ie. Primary DNS. I listed the scope options below if this
helps:
- 003 Router
- 006 DNS Server - Added Primary and Secondary DNS here
- 044 WINS Svr
- 046 Wins Node - 0x8
- 001 MS Disable Netbios - 0x1

How about the DNS Domain name/suffix? (option 015 )

Otherwise it won't know which zone to register in.

Make sure the clients and the DHCP server are also
in this DNS domain in the SYSTEM CONTROL panel.
(not the NIC suffixes.)

DHCP Server Options enabled:
1. Enable DNS dynamic update
a. Dynamically update DNS A and PTR records if requested
2. Discard A and PTR records
3. Update DNS for clients that do not request

This part is for NT/9x

The DHCP and Primary DNS reside on the same server. Thanks for all
your
help.

Also from your other message there are issues with
SINGLE LABEL DNS domain names and dynamic
registration.

Your zone should have at least two labels but you
might look into the fixes in the Knowledge base:

Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]



--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

:

Thanks for all you r help in this matter.

Current Configuration:
Primary DNS, DHCP, WINS - 2K3 server - member server on NT40 domain
Secondary DNS, WINS - 2K3 server - member server on NT40 domain
Workstation clients - All Windows XP Pro

Is your primary Zone set to allow updates?

I have all the neccessary configurations set in DHCP to dynamically
update
the DNS servers but it is not working.

When you say "all the necessary..." we cannot really help
you. Unless you list those we have to presume you know
and have everything correct.


The Primary DNS server is working
without any errors. We did however, change the name of the SOA to
NS1
instead of using the name of the server. Could this be the problem?

Probably not, with one exception: If the DHCP server
is set to use the Secondary, and the SOA record lists the Master
under a name which is NOT resolvable to an IP (i.e., no A record
for the Primary which accepts the dynamic updates.)
(Maybe even if it is set to use the Primary.)

How does the DHCP FIND the Dynamic Master (i.e., the Primary)?

We are
not using the DNS registration credentials in the DHCP Advanced
options.

That shouldn't matter since (presumable in an NT domain) you
don't have AD Integrated DNS and thus don't have "secure updates"
enabled.

Those credentials only matter for secure updates. (And although I
don't know this, I would be unsurprised if using them when not
necessary confused the DHCP server.)

The Primary and Secondary DNS servers are pointing repectively to
themselves
in IP Config for thier preferred DNS with no alternate DNS.

That's irrelevant to all except those two specific servers.

Where is the DHCP server pointed and how can it resolve
to FIND the DYNAMIC Primary DNS server?

The errors in in the DHCP log I am getting is as follows:
31,04/28/06,00:20:25,DNS Update Failed,10.100.101.91,IT-10058.,-1,
31,04/28/06,00:20:25,DNS Update Failed,10.100.101.92,it-10131.,-1,
31,04/28/06,00:20:25,DNS Update Failed,10.100.101.93,IT-10127.,-1,

You might not want to truncate those line.


It looks like DHCP is trying to update DNS but fails. Any ideas?
Thanks.

It's probably not finding the DYNAMIC Primary for the zone.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

 

[Guest]

So in short, I keep getting the single domain error when I restart the DNS
services. I assume this is why my XP clients are not updating. Should I fix
this issue on this domain member server via the following technet even though
it is not a domain controller, or will this screw up my domain membership?
Thanks.

http://support.microsoft.com/kb/888048/en-us

Thanks for all your help. I added the 015 DNS Domain Name to our DHCP
server. I also found out that 2000 SP4 and XP clients do not by default
dynamically update to single level domains unless you add the registry
hack.
I already see 1 NT40 workstation we had left register on our DNS.

I just have 1 more question, If I wanted to make dynamic updates work
before
we upgrade to AD can I just go ahead and rename our Primary DNS server to
name.mydomain.local. - this is the naming convention we are going to use
with AD. It is already joined to our NT40 domain, so could I trick this
2K3
member server by just renameing it?

It really has nothing to do with the NAME OF THE DNS
server. It has to do with the name of the ZONE, and the
DNS domain of the clients (and specified by DHCP.)

Now, technically the DNS server is (going to be) a
domain member and DNS client eventually too, but
the registration is not dependent on that, or its name.

(Real analogy: You could have a Unix box with an
arbitrary name doing this if it had a dynamic zone that
matched the client DNS name -- I am not recommending
this, just pointing out that the DNS server, especially
its own nam, it irrelevant if it can do the task.)



--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Thanks for your reply.

1. DNS is set for nonsecure and secure updates
2. I am sure what you asking when you want to know how DHCP finds
Dynamic
master. ie. Primary DNS. I listed the scope options below if this
helps:
- 003 Router
- 006 DNS Server - Added Primary and Secondary DNS here
- 044 WINS Svr
- 046 Wins Node - 0x8
- 001 MS Disable Netbios - 0x1

How about the DNS Domain name/suffix? (option 015 )

Otherwise it won't know which zone to register in.

Make sure the clients and the DHCP server are also
in this DNS domain in the SYSTEM CONTROL panel.
(not the NIC suffixes.)

DHCP Server Options enabled:
1. Enable DNS dynamic update
a. Dynamically update DNS A and PTR records if requested
2. Discard A and PTR records
3. Update DNS for clients that do not request

This part is for NT/9x

The DHCP and Primary DNS reside on the same server. Thanks for all
your
help.

Also from your other message there are issues with
SINGLE LABEL DNS domain names and dynamic
registration.

Your zone should have at least two labels but you
might look into the fixes in the Knowledge base:

Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]



--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]



:

Thanks for all you r help in this matter.

Current Configuration:
Primary DNS, DHCP, WINS - 2K3 server - member server on NT40 domain
Secondary DNS, WINS - 2K3 server - member server on NT40 domain
Workstation clients - All Windows XP Pro

Is your primary Zone set to allow updates?

I have all the neccessary configurations set in DHCP to dynamically
update
the DNS servers but it is not working.

When you say "all the necessary..." we cannot really help
you. Unless you list those we have to presume you know
and have everything correct.


The Primary DNS server is working
without any errors. We did however, change the name of the SOA to
NS1
instead of using the name of the server. Could this be the problem?

Probably not, with one exception: If the DHCP server
is set to use the Secondary, and the SOA record lists the Master
under a name which is NOT resolvable to an IP (i.e., no A record
for the Primary which accepts the dynamic updates.)
(Maybe even if it is set to use the Primary.)

How does the DHCP FIND the Dynamic Master (i.e., the Primary)?

We are
not using the DNS registration credentials in the DHCP Advanced
options.

That shouldn't matter since (presumable in an NT domain) you
don't have AD Integrated DNS and thus don't have "secure updates"
enabled.

Those credentials only matter for secure updates. (And although I
don't know this, I would be unsurprised if using them when not
necessary confused the DHCP server.)

The Primary and Secondary DNS servers are pointing repectively to
themselves
in IP Config for thier preferred DNS with no alternate DNS.

That's irrelevant to all except those two specific servers.

Where is the DHCP server pointed and how can it resolve
to FIND the DYNAMIC Primary DNS server?

The errors in in the DHCP log I am getting is as follows:
31,04/28/06,00:20:25,DNS Update Failed,10.100.101.91,IT-10058.,-1,
31,04/28/06,00:20:25,DNS Update Failed,10.100.101.92,it-10131.,-1,
31,04/28/06,00:20:25,DNS Update Failed,10.100.101.93,IT-10127.,-1,

You might not want to truncate those line.


It looks like DHCP is trying to update DNS but fails. Any ideas?
Thanks.

It's probably not finding the DYNAMIC Primary for the zone.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

 

[Kevin D. Goodknecht Sr. [MVP]]

So in short, I keep getting the single domain error when I restart
the DNS services. I assume this is why my XP clients are not
updating. Should I fix this issue on this domain member server via
the following technet even though it is not a domain controller, or
will this screw up my domain membership? Thanks.

http://support.microsoft.com/kb/888048/en-us

This message is telling you that the DNS server does not have a primary DNS
suffix, so its system name is server, instead of server.domain.com.
To give the DNS server a primary DNS suffix use the System control panel,
select the Computer name tab, click the change button, then click the More
button, and give your DNS server a valid DNS domain name for its primary DNS
suffix, a valid DNS domain is somedomain.SomeTopLevelName.

 

[Guest]

Thanks a bunch for this. I do not kow why I did not catch this. Anyway made
the changes in System PRoperties for the computer names DNS suffix. One more
question, when I entered the dns suffix (domain.local) should I put a period
"." at the end of this also? Thanks for all your help.

 

[Herb Martin]

Thanks a bunch for this. I do not kow why I did not catch this. Anyway
made
the changes in System PRoperties for the computer names DNS suffix. One
more
question, when I entered the dns suffix (domain.local) should I put a
period
"." at the end of this also? Thanks for all your help.

It is generally not required to put the final period
(making an FQDN) in CLIENT-side software or
settings.

Although, technically that terminating period should
ALWAYS be legal there is some (stupid) software
that doesn't allow it or won't work with it.

Leave it off.

One the DNS servers themselves the meaning of the
"Zone files" entries change, depending on whether
you terminate (fully qualify) the name or not.

You can also terminate or not when you ping etc.,
and the behavior is DIFFERENT.

 

[Guest]

Thanks for the info. I have one more question. After I made these changes
my DNS runs well with no errors on restart. However, only the Win NT 4.0
clients we have left updated with DNS. I had to change the primary DNS
suffix on my XP client before it would update with DNS. THe same thing I did
on the DNS server to fix the single domain issue. Why do I have to do this
and do I have to wait till we upgrade to AD before the XP clients will get a
primary DNS suffix?

 

[Herb Martin]

Thanks for the info. I have one more question. After I made these
changes
my DNS runs well with no errors on restart. However, only the Win NT 4.0
clients we have left updated with DNS. I had to change the primary DNS
suffix on my XP client before it would update with DNS. THe same thing I
did
on the DNS server to fix the single domain issue. Why do I have to do
this

I will tell you but it is better if you think it through
first, or with me.

XP needs to "register itself in DNS". What DNS?

What zone? Where should it register itself?

It has to pick a SPECIFIC zone to register itself.
Your DNS cannot register itself in MY DNS, or Google's,
and you don't want it to register in the WRONG DNS
zone if you have more than one domain/zone, right?

So, XP will register itself in it's 'own zone' !!!!

It registers in the one to which it BELONGS, and that
is set in the System Control Panel. (Although DHCP
can set it too.)

and do I have to wait till we upgrade to AD before the XP clients will get
a
primary DNS suffix?

No. Just go to each of them and give them the correct
suffix in the System Control Panel.