DNS - Wrong Server Name

  • Thread starter Thread starter craig
  • Start date Start date
C

craig

I have a W2K Server running DNS,WINS, and DHCP. All of
these services appear to be working properly. My server
name is lc3 and the fqdn is lc3.workgroup.local. My
servers ip address is 193.0.0.3. I can ping 193.0.0.3 and
it will resolve to lc3.workgroup.local. Although if I do
an nslookup it tells me the server is zeeburg.ripe.net, I
have know idea what that is. If I go into DHCP the server
shows up as zeeburg.ripe.net [193.0.0.3], the correct ip
address, again the unknown name. In WINS when I go to the
find by owner the IP looks correct the name is zeeburg.

I have tried clearing the dns cache and flush dns . I
can't seem to shake the zeeburg reference. Can you shed
any light?

Thank you in advance for your time.

Craig
 
I noticed my forward lookup zone created by DCPROMO was
workgroup.local, I added a forward lookup zone
lc3.workgroup.local and this seems to have fixed the
issues in my last email. The new lookup zone does not seem
to be populated like the original (no sub-folders and not
as many records). Now do I leave both zones there or do I
remove the original?
 
Craig,

Your actual AD zone name appears to be workgroup.local. Confirm this to the
domain name that shows up in your ADUC. LC3 from what you're saying, is a
host name in that zone, and not a zone, as you configured. AD is registering
it's info, and if configured properly, the workstations are registering in
the workgroup.local zone also.

Registration is dictated by the netlogon service and what the machine's
Primary DNS Suffix is. You can check that by rt-clicking My Computer,
Network ID tab, Properties, More. You can also run an ipconfig /all and it
will show you your PrimaryDNS Suffix. This name MUST match AD's domain name
and the zone created in DNS and the zone needs to have updates set to at
least YES to make it work.

If you created the lc3.workgroup.local zone, and AD and the other machines
are configured with a Primary DNS Suffix of wrkgroup.local, things will
never get registered in that zone, as what would be normal and expected.

I would remove the lc3.workgroup.local zone, since it won't be used.

As I mentioned in my other post, the IP comes back to the actual owner
registered for that IP range. If it is your ISP, I can suggest to ask them
to delegate the reverse zone to your DNS servers and create the reverse zone
and make sure that there is a PTR entry for your machine(s) to prevent this.
If you meant to have a private zone and accidentally used the 193.0.0.0
range, then I would suggest to change it to a 192.168.0.0 range, such as
192.168.1.0, making this machine 192.168.1.3.

Hope that helps. Any questions, please post back.

--
--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================



Craig said:
I noticed my forward lookup zone created by DCPROMO was
workgroup.local, I added a forward lookup zone
lc3.workgroup.local and this seems to have fixed the
issues in my last email. The new lookup zone does not seem
to be populated like the original (no sub-folders and not
as many records). Now do I leave both zones there or do I
remove the original?
-----Original Message-----
I have a W2K Server running DNS,WINS, and DHCP. All of
these services appear to be working properly. My server
name is lc3 and the fqdn is lc3.workgroup.local. My
servers ip address is 193.0.0.3. I can ping 193.0.0.3 and
it will resolve to lc3.workgroup.local. Although if I do
an nslookup it tells me the server is zeeburg.ripe.net, I
have know idea what that is. If I go into DHCP the server
shows up as zeeburg.ripe.net [193.0.0.3], the correct ip
address, again the unknown name. In WINS when I go to the
find by owner the IP looks correct the name is zeeburg.

I have tried clearing the dns cache and flush dns . I
can't seem to shake the zeeburg reference. Can you shed
any light?

Thank you in advance for your time.

Craig
.
Click to expand...
Click to expand...
 
In
coming in after the fact and the dns and ip scheme was
already setup. I would prefer that it was in a private
range, the customer does not need it to be public,
although I thought that it was hard to change after the
fact. What will I break changing the ip's and what are the
steps I should take?

Thanks again for your time.
Click to expand...

Hi again Craig,

I guess it would be beter to have the private range. It's not that it's hard
to change, just have to plan it out. Write down everything that has an IP
and whether static or DHCP. Purchase a NATdevice (budget here - PIX,
Netgear, Linksys?), and decide on a private IP shceme. Doing it off hours,
change over the servers and setup the router first. Then all the remaining
static addresses then setup the scope, making sure that you change
scope/server options to reflect the new IPs. For WINS, make sure you
tombstone/delete the old IPs and let the new ones self register, any static
mappings recreate. DNS make sure the new IPs show up in the nameserver's tab
and that they register into DNS. Delete any old references.

Doumentation and planning is pretty much the key here.

Good luck.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top