'A' record dynamic DNS registration failing depending on DHCP serv
mtnit
segments. I want to be able to use DNS for name resolution within the network.
I am running Windows DNS server and am unable to have a client register its
A record with the DNS server automatically when using the Windows DHCP server.
The client will register its pointer (PTR) but not its A record or its FQDN.
I want to be able for the DHCP server set the DNS server to append the DNS
suffix to the hostname so I can use it for name resolution between the
network subnets.
I have gone through the documentation of 'Option 81' and set the DHCP server
to have DNS A and PRT records always dynamically updated. I am able to get
the client to register correctly if I check the clients 'Use this
connection's DNS suffix in DNS registration' in its network connection
options. What's even more strange is that if I use the DHCP server in another
hardware device (Adtran router) the DNS suffix is appended and the FQDN is
correct. As soon as I try to use the Windows DHCP server this no longer works.
Obviously this has something to do with the dynamic update relationship
between Windows DHCP and DNS but I can't work out the option to fix it. I
don't want a solution that involves me changing a setting on every single
workstation.
Appreciate any help!
Jorge Silva
Inline
>I am running a Windows Server 2003 workgroup with many clients and multiple
> segments. I want to be able to use DNS for name resolution within the
> network.
install DNS service on that server, point the server to itself, and point
the clients to the server. If you want you can increase security by
configuring the server to forward the requests to your ISP and/or Router and
enableing the option don't use recursion for this domain.
> The client will register its pointer (PTR) but not its A record or its
> FQDN.
Create a PTR zone an allow updates. Do you have a forward zone?
> I want to be able for the DHCP server set the DNS server to append the DNS
> suffix to the hostname so I can use it for name resolution between the
> network subnets.
I though that we were talking about Workgroup.
Are we talking about Workgroup or Domain Environment?
> I have gone through the documentation of 'Option 81' and set the DHCP
> server
> to have DNS A and PRT records always dynamically updated. I am able to get
> the client to register correctly if I check the clients 'Use this
> connection's DNS suffix in DNS registration' in its network connection
> options. What's even more strange is that if I use the DHCP server in
> another
> hardware device (Adtran router) the DNS suffix is appended and the FQDN is
> correct. As soon as I try to use the Windows DHCP server this no longer
> works.
read this:
Using DNS servers with DHCP
http://technet2.microsoft.com/WindowsServer/en/Library/179d4f6c-9482-4dac-8f03-74bd78b7d2631033.mspx
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
"mtnit" <mt...@discussions.microsoft.com> wrote in message
news:216F34C2-17C3-4C7C...@microsoft.com...
mtnit
Thanks for your response. I followed your suggestions and the clients are
now showing up in the Forward Lookup Zone however they are still not having a
FQDN suffix attached. Please see some of my responses below.
Thanks,
-Kyle
"Jorge Silva" wrote:
> Hi
> Inline
> >I am running a Windows Server 2003 workgroup with many clients and multiple
> > segments. I want to be able to use DNS for name resolution within the
> > network.
> This is called, chache only servers, all you have to do to this work is to
> install DNS service on that server, point the server to itself, and point
> the clients to the server. If you want you can increase security by
> configuring the server to forward the requests to your ISP and/or Router and
> enableing the option don't use recursion for this domain.
DNS has been setup with default settings and is resolving names correctly
for clients.
> > The client will register its pointer (PTR) but not its A record or its
> > FQDN.
> Create a PTR zone an allow updates. Do you have a forward zone?
Yes forward and reverse lookup zones have been created. However the clients
are only being registered in the Reverse Lookup Zone. They are not
registering themselves in the Forward Lookup Zone. Also they only register
themselves in the Reverse Lookup Zone as: 'hostname.', whereas clients that
recieved their IP from another DHCP server register their name under the
'Data' column as: 'hostname.domain.local'.
> > I want to be able for the DHCP server set the DNS server to append the DNS
> > suffix to the hostname so I can use it for name resolution between the
> > network subnets.
> I though that we were talking about Workgroup.
>
> Are we talking about Workgroup or Domain Environment?
Its a workgroup and their is no DC or AD. I would still like DNS to append a
DNS suffix to make a FQDN for the purpose of name resolution within the
network.
>
>
Jorge Silva
> DNS has been setup with default settings and is resolving names correctly
> for clients.
> Yes forward and reverse lookup zones have been created. However the
> clients
> are only being registered in the Reverse Lookup Zone. They are not
> registering themselves in the Forward Lookup Zone. Also they only register
> themselves in the Reverse Lookup Zone as: 'hostname.', whereas clients
> that
> recieved their IP from another DHCP server register their name under the
> 'Data' column as: 'hostname.domain.local'.
Did you enabled the option:Always update DNS
Did you configured the dns suffix on dhcp
If you define staticTCP/ IP with the preferred dns server pointing to the
correct dns server, and run from cmd ipconfig /registerdns, the record
shows?
The clients that are having problems do they already had a A record on DNS
register by the other DHCP, if you delete that record and try again what
happens?
Are these windows xp clients or do you have NT4, W98,etc?
Read:
Troubleshooting dynamic updates
http://technet2.microsoft.com/WindowsServer/en/library/1583e419-88a6-4062-8807-d9eea99e3b421033.mspx?mfr=true
DHCP Dynamic DNS Registration for Windows 2000 Clients Does Not Work
http://support.microsoft.com/default.aspx?scid=kb;en-us;314822
A DHCP Client May Send an Incorrect FQDN in a DHCP-Request Packet
http://support.microsoft.com/?kbid=317288
Dynamic Host Configuration Protocol for Windows Server 2003
http://download.microsoft.com/download/1/6/a/16a11c96-daa4-44a6-98ae-9f9ddb203b46/DHCP2003.doc
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
"mtnit" <mt...@discussions.microsoft.com> wrote in message
news:E3F13C00-6A3B-48DB...@microsoft.com...
mtnit
I'm surprised this is not a more common issue. I don't seem to be doing
anything unusual except I'm not running an actual domain. Answers are below.
-Kyle
> Did you enabled the option:Always update DNS
Yes.
> Did you configured the dns suffix on dhcp
Yes. (Option 15). It sets the connection specific DNS suffix. This does not
append to the hostname however. It only appends if the client has primary DNS
suffix manually set, or it recieves its IP from a different DHCP device.
> If you define staticTCP/ IP with the preferred dns server pointing to the
> correct dns server, and run from cmd ipconfig /registerdns, the record
> shows?
Yes, but it does not include the appended DNS suffix.
> The clients that are having problems do they already had a A record on DNS
> register by the other DHCP, if you delete that record and try again what
> happens?
It is recreated the next time the lease is renewed.
> Are these windows xp clients or do you have NT4, W98,etc?
All are Windows XP clients.
Jorge Silva
allow dynamic updates.
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
"mtnit" <mt...@discussions.microsoft.com> wrote in message
news:C85B6670-ED2A-47C6...@microsoft.com...