Go to the DNS snap-in and expand the server for the zone.Right-click
"Reverse Lookup Zones" and select "New Zone". When the wizard starts,
just
accept the defaults and when you get to the "Revers Lookup Zone Name"
page,
type in the subnet (192.168.0, I believe was what you were using).
Complete
the wizard and you'll have a RL Zone.
To add a PTR record, just right click the reverse zone you just created
and
put in the IP address and name fo your server.
.....kurt
Hi Kurt,
I see now how bad it was for me to create a domain name with
.com.
Next time,( If there is one) I will use .local. This problem has been
driving
me crazy for months
If you don't mind, can you please explain as best you can on how I go
about
creating a reverse zone ( with what settings) and add the server's PTR
record
manually ?
Thanks so much.
P.S. The reason I need to get this resolved is because most of the
programs
that allow me to to do remote installs, updates, etc require it to
resolve
names to IPs and thus they don't work. :-(
:
Sorry, I'm used to non-public domains being something.local or
whatever.
If
your domain is gdserver.com, that is the zone you will require.
gdserver.com
is a public name, I can look it up and it resolves as such:
Server: cpi-dc-02
Address: 10.0.0.113
Name: gdserver.com
Address: 204.251.15.162
You must have your own local zone to resolve local names. Since
192.168.0.100 is presumably your DNS server, it is replying. But it
went
to
the Internet to look it up, so it doesn't think it's the SOA for the
zone.
It's not the best idea to name your internal DNS space the same as
your
public space (or even worse, someone else's public name). If you do,
you'll
have to manually maintain all records that point to public servers.
The
reason you can't resolve your own server's name is because you don't
have
a
reverse lookup zone and/or a PTR record for 192.168.0.100. You can
create
a
reverse zone and add the server's PTR record manually.
....kurt
Ok.
I ran nslookup from the DC server and I got the following results:
Can't find server name for address 192.168.0.100: Non-existent
domain
Server: Unknown
Address: 192.168.0.100
Name: /?.gdserver.com
Address: 204.251.15.162
:
Thanks Kurt for responding.
1. I didn't have a zone created for GDSERVER.LOCAL. I only had 1
for
gangserver.gdserver.com (gangserver is the name of the dc
computer). I
added
one for GDSERVER.LOCAL. I also checked and both the DNS Client and
DNS
Server
services are both running. Still didn't work.
How do I make sure all of the clients are using only the gangserver
DC
as
their nameservers ?
Thanks a lot for your time and help. It is much appreciated !
How do I do a nslookup ?
:
First of all, make sure you have zones created locally for
GDSERVER.LOCAL,
and that the DNS server service is running on your DC. Then make
sure
all of
your clients are using your DC (and ONLY your DC) as their
nameservers -
that includes the server itself.
Do an nslookup for fax.gdserver.com and see which DNS server is
providing
the reply. It should be yours. And it should not be a
"non-authoritative
answer", since your DNS server IS the authoritative name server
for
your
domain. Post the results here if it still won't work.
....kurt
Hi,
I am having a very hard time ttrying to figure out what is
causing
my
problem and I am hoping some of you may be able to help me.
I have a domain setup up on a Windows 2000 Server machine. The
domain
name
is GDSERVER.COM. When I try and ping 1 of the 25 computers on
the
domain
by
the client machine name, it appears to be going out to the
internet
to try
and resolve the IP. For example, when I type Ping Fax (name of
1
of
the
client machines on the domain) it shows the IP as
204.251.15.162
instead
of
it resolving to 192.168.0.176. Here si the exact response:
Pinging fax.gdserver.com [204.251.15.162] with 32 bytes of
data.
Obvisiously it times out. It appears that its trying to go out
to
the
internet to gdserver.com. Anyone have any suggestions on how I
might
correct
this ? Thanks. Kevin
