>> 3) From inside the LAN, using a computer pointing to your DNS server,
>> are you able to resolve any hosts on threeofus.com?
> here's what I get running dig at the prompt, logged into monica (.4,
the
> dns server) logged in as root:
> [root@monica jfreeman]# dig threeofus.com
> ; <<>> DiG 8.3 <<>> threeofus.com
> ;; res options: init recurs defnam dnsrch
> ;; got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 4
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
> ;; QUERY SECTION:
> ;; threeofus.com, type = A, class = IN
> ;; Total query time: 127 msec
> ;; FROM: monica to SERVER: default -- 199.232.38.4
> ;; WHEN: Mon Aug 6 09:24:29 2001
> ;; MSG SIZE sent: 31 rcvd: 31
> I don't think I can resolve any hostname on my LAN from inside.
That could be the problem :-) If you can't connect from inside your LAN
then that means at least one problem lies with your DNS server. You can
try the following to make sure:
1) Pick a node where you want to test your DNS server inside the LAN
2) Make sure that the first DNS server that computer connects to is your
DNS server (on Linux, /etc/resolv.conf specifies the DNS servers,
whichever comes first is the one it contacts)
3) Type "nslookup", and follow the sample below substituting the correct
values where appropriate:
% nslookup
> <some_valid_local_node>
> <that_same_local_nodes's_IP_address>
So, for an example I'll make up some computer names and IP addresses and
show the output:
% nslookup
Default Server: dns_server.threeofus.com <=== make sure you see your
DNS server here (#1)
Address: 16.103.121.21
> node1
Server: dns_server.threeofus.com
Address: 16.103.121.21
Name: node1.threeofus.com <=== make sure it appends threeofus.com
Address: 16.103.121.37 <=== and you see its IP address (#2)
> 16.103.121.37 <=== type same IP address from just above
Server: dns_server.threeofus.com
Address: 16.103.121.21
Name: node1.threeofus.com <=== make sure it does "reverse lookup" to
find that IPs name (#3)
Address: 16.103.121.37
#1) If the "Server:" value isn't your DNS server, that means you can't
resolve your DNS server even from the inside.
#2) If it doesn't return the IP address of node1 after you type "node1"
at the prompt, then that means you aren't able to resolve any hostnames
in threeofus.com. That means your DNS server isn't configured properly
and needs proper configuring.
#3) If you do get the IP address of node1, but do not get the name back
when you type the IP address by itself, that means your DNS server is
configured to resolve names to IP address, but it's not configured to
resolve IP addresses to names (also known as "reverse lookup"). Then
you need to configure it to also do the reverse lookup.
These steps are meant only to find your problem. Once you find exactly
what it is, then we can given step-by-step instructions on what to do
about it. Once you verify that your DNS server is working properly,
then we will know for sure that the problem comes from somewhere else.
Regards,
Warren
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
