It's becoming clearer.  I'm going to write out some troubleshooting
steps below so you can see some basic dns queries.  I'll bet the problem
is in your named.conf file, but this will narrow it down:

First Look at the dns report at:
http://www.dnsreport.com/tools/dnsreport.ch?domain=mystyka.com
This shows more detail for your domain that you may need as you learn
dns.

Start troubleshooting dns.  Check for "glue" at the root.
It looks like your registrar, aitdomains, has dns entries for ns1 and
ns3.mystyka.com but your dns server does not have A records for those
servers:

----- snip ------
$ dig @64.91.118.88 ns1.mystyka.com

; <<>> DiG 9.2.1 <<>> @64.91.118.88 ns1.mystyka.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 15656
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;ns1.mystyka.com.               IN      A

;; Query time: 389 msec
;; SERVER: 64.91.118.88#53(64.91.118.88)
;; WHEN: Sat Mar 29 22:56:42 2003
;; MSG SIZE  rcvd: 33
---- end snip ----

Also notice the "SERVFAIL" status.

So, let's check to see if a dns server is running on your computer:
---- snip ----
$ dig @64.91.118.88 .

; <<>> DiG 9.2.1 <<>> @64.91.118.88 .
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53846
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;.                              IN      A

;; AUTHORITY SECTION:
.                       1118    IN      SOA     A.ROOT-SERVERS.NET.
NSTLD.VERISIGN-GRS.COM. 2003032901 1800 900 604800 86400

;; Query time: 151 msec
;; SERVER: 64.91.118.88#53(64.91.118.88)
;; WHEN: Sat Mar 29 23:02:33 2003
;; MSG SIZE  rcvd: 92
---- end -----
That query verified that your box is responding to queries for "." (the
root servers).

Also, let's run a query to see which version of bind you are running
(you shouldn't allow this for security, but since you are new to dns, we
won't hold that against you:

---- snip ----
$ dig @64.91.118.88 version.bind chaos txt

; <<>> DiG 9.2.1 <<>> @64.91.118.88 version.bind chaos txt
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52881
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;version.bind.                  CH      TXT

;; ANSWER SECTION:
version.bind.           0       CH      TXT     "9.2.1"

;; Query time: 394 msec
;; SERVER: 64.91.118.88#53(64.91.118.88)
;; WHEN: Sat Mar 29 23:05:40 2003
;; MSG SIZE  rcvd: 48
----- end -----

Good that your server answered, but you should enter a line like this in
the options section of /etc/named.conf

options {
        version "[I don't respond to version queries]";
        }

Now that we know your server is responding, let's check to see if it
will transfer any zone data for mystyka.com (this should also be
restricted before you go live):
---- snip -----
$ dig @64.91.118.88 mystyka.com axfr

; <<>> DiG 9.2.1 <<>> @64.91.118.88 mystyka.com axfr
;; global options:  printcmd
;; connection timed out; no servers could be reached
---- end ----

That means that you've either blocked zone transfers or your server
doesn't think it's authoritative for mystyka.com.

One more query to verify:
--- snip -----
$ dig @64.91.118.88 ns1.mystyka.com

; <<>> DiG 9.2.1 <<>> @64.91.118.88 ns1.mystyka.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 16314
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;ns1.mystyka.com.               IN      A

;; Query time: 369 msec
;; SERVER: 64.91.118.88#53(64.91.118.88)
;; WHEN: Sat Mar 29 23:34:27 2003
;; MSG SIZE  rcvd: 33
---- end -----

your server doesn't answer for ns1 -- to go further, we'd have to look
at your /etc/named.conf.

mjb










On Sat, 2003-03-29 at 22:36, Wikked Skye wrote:
> I have done the dig thing, and it looked alright there.  There is really 
> nothing on the system at all right now, so I am fine giving out that 
> information.  When I do ping for the ip it comes back fine, but when I 
> ping the domain name it comes back host unknown.  I am indeed using the 
> Apache Server.
> 
> ip 64.91.118.88   I am able to hit the site with this.
> domain  www.mystyka.com    I get cannot be found/cannot resolve with this
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to