Thanks for bearing with my stupidity
Im not 100% sure what you mean here. You can add
a "host" under the "zone" which is under forward lookups
Im not 100% sure how it will help.
www.qccs.com.au is a
web site, but its remotely hosted, not on the PUBLIC IP
of this network.
Below is the headoffice.qccs.com.au forward lookup "zone"
(i've changed the public IP for obvious reasons
)
Name Type Data
_msdcs
_sites
_tcp
_udp
(same as parent folder) Start of Authority [34],
server.headoffice.qccs.com.au.,
admin.headoffice.qccs.com.au.
(same as parent folder) WINS Lookup [192.168.0.1]
(same as parent folder) Name Server
server.headoffice.qccs.com.au.
(same as parent folder) Host 192.168.0.1
AdminAssist1 Host 192.168.0.11
ADMINASSIST2 Host 192.168.0.4
assessor1 Host 192.168.0.15
collegerecp Host 192.168.0.3
DIRECTOR Host 192.168.0.9
jacky Host 192.168.0.37
Kellie Host 192.168.0.2
Principal Host 192.168.0.6
Reception Host 192.168.0.12
Secretary Host 192.168.0.7
server Host 192.168.0.1
PUBLIC Host 240.202.245.244 (this is the entry with
the public IP us said to add,but i can't see how it will
help)
Notice how ALL singel pc names kie "recpetion" is listed
to a corresponding IP YET they still will not resolve
that IP from the name even though its in this section of
the DNS records.
Reverse lookup (192.168.0.x subnet) is
Name Type Data
(same as parent folder) Start of Authority [31],
server.headoffice.qccs.com.au.,
admin.headoffice.qccs.com.au.
(same as parent folder) WINS Reverse Lookup
headoffice.qccs.com.au.
(same as parent folder) Name Server
server.headoffice.qccs.com.au.
192.168.0.1 Pointer server.headoffice.qccs.com.au.
192.168.0.10 Pointer assessor2.headoffice.qccs.com.au.
192.168.0.11 Pointer
adminassist1.headoffice.qccs.com.au.
192.168.0.12 Pointer reception.headoffice.qccs.com.au.
192.168.0.14 Pointer hyperdome1.(not ment to be on
domain)
192.168.0.15 Pointer assessor1.headoffice.qccs.com.au.
192.168.0.2 Pointer kellie.headoffice.qccs.com.au.
192.168.0.3 Pointer
collegerecp.headoffice.qccs.com.au.
192.168.0.37 Pointer jacky.headoffice.qccs.com.au.
192.168.0.4 Pointer
adminassist2.headoffice.qccs.com.au.
192.168.0.6 Pointer principal.headoffice.qccs.com.au.
192.168.0.7 Pointer secretary.headoffice.qccs.com.au.
192.168.0.8 Pointer hyperdome2. (not ment to be on
domain)
192.168.0.9 Pointer director.headoffice.qccs.com.au.
192.168.0.9 Pointer jack.headoffice.qccs.com.au.
192.168.0.9 Pointer director. (it has this entry
after renaming a PC and THEN joining the domain)
DHCP scope options
Option Name Vendor Value Class
003 Router Standard 192.168.0.200 None
006 DNS Servers Standard 192.168.0.1 None
015 DNS Domain Name Standard
headoffice.qccs.com.au None
It certainly seems everything is OK (i think).
Should i "destroy" (ie totally delete) the DNS config and
rebuild it from scratch?
I think the reason that the headoffice domain cannot be
browsed (ie errors), is due to the fact is is lookin ONLY
at "headoffice" and not "headoffice.qccs.com.au" when
browsing, same goes for when joing a domain, use to put
just headoffice and it would resolve, now need
headoffice.com.au.
Why did adding JUST a forward lookup zone of "headoffice"
(ie in addition to "headoffice.qccs.com.au" that was in
existence) sudently allow PC's to ping directly to NAME
only ie "computer", before this
only "computer.qccs.headoffice.com.au". Yet while
local "name" only pcs would not resolve, internet names
would, given both should be resolved via the server (ie
both internet and local names).
Also, In my attempts to fix, I added to the servers own
NIC config its OWN IP as WINS server, is this OK?
(previously wasnt any entry).
-----Original Message-----
Hi Dan,
I think that you do have a problem, because you've put
the 'headoffice' in
front of it, and you should have added it to the end.
Let's try the
following in DNS-server. Can't remember if it should be
in the Forward or
Reverse Lookup Zone, but you'll soon see that.
Rightclick and add a new
host. Give that host the public IP number. You'll create
a new record that
will look like:
www.qccs.com.au with your public IP.
Restart DNS-server and see if you can get anywhere from
the server and the
clients.
You're right about the DNS: it should point to your
server-IP on your
servernics and thus on the clients too.
--
Regards,
Marina
"Dan" <
[email protected]> schreef in
bericht
AD domain name is
headoffice.qccs.com.au
internet domain (ie web/mail externally hosted)
qccs.com.au
It has been setup like this for 1year +.
I figured having qccs.com.au as the AD domain would
give
trouble, hence made added headoffice.
ALL internet names are resolved fine, so in that
regard i
guess the DNS forwarding is working on the server
(unless
due to the default gateway being the router the router
is
resolving these?, but the clients ARE set to use
192.168.01 as DNS server).
-----Original Message-----
Hi Dan,
Is your AD-domainname the same as your internet
domainname?
--
Regards,
Marina
<
[email protected]> schreef in
bericht
ipconfig /all
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : server
Primary DNS Suffix . . . . . . . :
HEADOFFICE.QCC
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . :
HEADOFFICE.QCC
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SiS 900
PCI Fa
Physical Address. . . . . . . . . : 00- 0A-
E6-
5F-BF
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . :
192.168.0.1
Subnet Mask . . . . . . . . . . . :
255.255.255.0
Default Gateway . . . . . . . . . :
192.168.0.200
DNS Servers . . . . . . . . . . . :
192.168.0.1
Primary WINS Server . . . . . . . :
192.168.0.1
Sever is both DHCP and DNS with following config (as
you "walked" me through last time
thanks)
DHCP:
Automaticly update DHCP is enabled (ie in
properties of
the "server" under DHCP)
Scope Options are. DNS at 192.168.0.1 (the
server)
DNS Domain Name: headoffice.qccs.com.au
Router: 192.168.0.200
Thoses "options" are under the only "scope" of
192.168.0.2 thru 192.168.0.99
DNS:
The Servers OWN lan card has the DNS set to its OWN
IP,
ie 192.168.0.1 (no other entries)
In DNS config ONLY listening on the LAN 192.168.0.1
DNS forwarding enabled and pointing to ISP DNS
PASSES both simple query and recursive query tests.
Forward lookup zones has:
headoffice.qccs.com.au as the zone
under that is the usual listing of hosts (ie IP's
handed
out by DHCP matching PC names, which "computer"
not "computer.headoffice.qccs.com.au".
Also has start of authority as
server.headoffice.qccs.com.au and same for name
server
and 192.168.0.1 for Wins lookup.
Has the usual sub sections as _msdcs _sites _tcp
_udp
Under reverse lookup:
has zone: 192.168.0.x Subnet
Underwhich pointers are listed
-----Original Message-----
Hi Dan,
How many nics in the server? Can you post the
ipconfig/all please? Is the
server doing the DHCP and DNS-serving?
Does the ipconfig/all from the clients show that
everything is pointing to
the server-IP? What OS on the clients?
--
Regards,
Marina
"Dan" <
[email protected]>
schreef in
bericht
ALL of the PC's will not resolve the other PC's
IP
through
JUST the PC name. for example "Server". They
will
resolve the name via the full domain path ie
"server.headoffice.com.au" for example.
Same goes for the domain, the
domain "headoffice" is
not
visable unless the full domain path is entered
ie "headoffice.com.au" for example
This presents problems given network shares/drive
mapppings etc are setup on only the PC name
ie "server",
in which case the wont reconnect due to this
issue.
One can access the shares via
\\server.headoffice.com.au
or \\192.168.0.1 for example but not via \\server
NET VIEW commands return "the list of servers for
this
workgroup is not currently available". Same
occurs if
on
navigates through "entire network",
the "headoffice"
domain can be seen, but the same error is
returned
if
one
attempts to "browse" it.
Also when "joining" the domain initially the full
path
must be entered, ie 'headoffice.com.au' as
just 'headoffice' returns error that domain
cannot
be
found.
Any ideas would be greatly appreciated.
2000k server XP Pro Clients
Marina (if u read this) you've helped me before,
any
ideas
Thanks
Danny
Sorry for the double post (also in DNS) but A
quick
search found Marina frequents this more, was
extremely
helpful with my last problem
.
.
.
