Can you give us some more information regarding your internal network? 
Do you have a dns server internally?  Is palmetto.dnsalias.net a redhat
box?  Are you running NAT to your internal network?

mjb

Here's my setup:  I have a dynamic ip address on DSL.  I'm using
dnsalias as my dynamic DNS provider.  I'm running RH 8.0 with all the
updates.  Not sure but I think NAT is running.  I had some help with
that.

/etc/named.conf:
----------------------------------------------------------------
# named.conf - configuration for bind
#
# Generated automatically by redhat-config-bind, alchemist et al.
# Any changes not supported by redhat-config-bind should be put 
# in /etc/named.custom
#
controls {
        inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};
 
include "/etc/named.custom";

include "/etc/rndc.key";

options { 
        directory "/var/named/";        
};

zone  "0.0.127.in-addr.arpa" { 
        type master; 
        file  "0.0.127.in-addr.arpa.zone"; 
};

zone  "localhost" { 
        type master; 
        file  "localhost.zone"; 
};

zone "dnsalias.net" {
        type master;
        file "/var/named/dnsalias.net.hosts";
        };
----------------------------------------------------------------------

/var/named/0.0.127.in-addr.arpa.zone:
----------------------------------------------------------------------
$TTL 86400
@       IN      SOA     localhost. root.localhost (
                        2
                        28800
                        7200
                        604800
                        86400 )


@       IN      NS      localhost.

1       IN      PTR     localhost.
1.0.0.127.in-addr.arpa. IN      PTR     localhost.
----------------------------------------------------------------------

/var/named/dnsalias.net.hosts:
----------------------------------------------------------------------
$ttl 38400
dnsalias.net.   IN      SOA     ns1.palmetto.dnsalias.net.
edukes.palmetto.dnsalias.net. (
                        2003033003
                        10800
                        3600
                        604800
                        38400 )
dnsalias.net.   IN      NS      ns1.palmetto.dnsalias.net.
dnsalias.net.   IN      A       10.10.0.1
mail.palmetto.dnsalias.net.     IN      CNAME   palmetto.dsalias.net.
dnsalias.net.   IN      MX      1 mail.palmetto.dnsalias.net
-----------------------------------------------------------------------

/var/named/localhost.zone:
-----------------------------------------------------------------------
$TTL 86400
@       IN      SOA     @ root.localhost (
                        3
                        28800
                        7200
                        604800
                        86400 )


@       IN      NS      localhost.


@       IN      A       127.0.0.1
------------------------------------------------------------------------

# host palmetto.dnsalias.net
palmetto.dnsalias.net has address 151.213.88.57

# host -t mx palmetto.dnsalias.net
palmetto.dnsalias.net has address 151.213.88.57

# host mail.palmetto.dnsalias.net
palmetto.dnsalias.net is an alias for palmetto.dnsalias.net.

Here's the kicker:
# host -t ns palmetto.dnsalias.net
#

Nothing!!!!

It has me stumped.  I've been reading ttill my heads hurts.  :-)

Thanks

On Sun, 2003-03-30 at 14:58, Thomas E. Dukes wrote:
> I am having similar problems with DNS.  I can't resolve 
> palmetto.dnslais.net form itself.  I can from my XP box or from the 
> outside, just not iternally.  I tried to ping myself, but that doesn't

> work either
> 
> I can do dig palmetto.dnsalias.net and get the following:
> 
> 
> ; <<>> DiG 9.2.1 <<>> palmetto.dnsalias.net
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47521
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 
> 5
> 
> ;; QUESTION SECTION:
> ;palmetto.dnsalias.net.               IN      A
> 
> ;; ANSWER SECTION:
> palmetto.dnsalias.net.        60      IN      A       151.213.88.57
> 
> ;; AUTHORITY SECTION:
> dnsalias.net.         85905   IN      NS      ns1.dyndns.org.
> dnsalias.net.         85905   IN      NS      ns2.dyndns.org.
> dnsalias.net.         85905   IN      NS      ns3.dyndns.org.
> dnsalias.net.         85905   IN      NS      ns4.dyndns.org.
> dnsalias.net.         85905   IN      NS      ns5.dyndns.org.
> 
> ;; ADDITIONAL SECTION:
> ns1.dyndns.org.               64463   IN      A       66.151.188.43
> ns2.dyndns.org.               84559   IN      A       209.69.32.137
> ns3.dyndns.org.               84559   IN      A       64.152.102.41
> ns4.dyndns.org.               84559   IN      A       212.100.224.171
> ns5.dyndns.org.               84559   IN      A       66.151.188.44
> 
> ;; Query time: 161 msec
> ;; SERVER: 166.102.165.15#53(166.102.165.15)
> ;; WHEN: Sun Mar 30 16:54:12 2003
> ;; MSG SIZE  rcvd: 256
> 
> 
> Any ideas?  I'm at a loss.
> 
> TIA
> Palmetto Shopper
> http://www.palmettoshopper.com
> Serving all of South Carolina and beyond!
> 
> 
> 
> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED]
> On Behalf Of Mark Johnson-Barbier
> Sent: Saturday, March 29, 2003 10:56 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Setting up NameServer with BIND
> 
> 
> A whois query will not identify a problem in your dns configuration.  
> To check if dns is returning an IP address correctly, you should use 
> the "dig" command in the format: $ dig www.yourdomain.com
> 
> If you see an an answer such as:
> ;; ANSWER SECTION:
> www.redhat.com.         300     IN      A       66.187.232.56
> 
> and your IP address is correct, then you know dns is working.
> 
> Another common way to test dns is to "ping" the server as in: $ ping 
> www.yourdomain.com
> 
> If you get a response such as
> $ ping www.wikkedskye.com
> ping: unknown host www.wikkedskye.com
> 
> you know dns or some other part of name resolution is not working.
> 
> Another common problem for situations like this is that your web 
> server (I'm assuming you are using apache) has a misconfiguration in 
> the virtual web site section.
> 
> If you can provide more specific data with your question, you'll get 
> better answers.  For example, if you feel comfortable sharing your 
> domain name, others can determine if dns is working or not.
> 
> mjb
> 
> 
> 
> On Sat, 2003-03-29 at 17:56, Wikked Skye wrote:
> > I have been trying with this and reading articles with this for four

> > days now, and I am stumped.  I have checked everything, ports are
> open,
> > firewall is set okay.  I can get to my website by using the ip, but
> not
> > with the www address.  Everything is pointed correctly.  I have
> checked
> > with WhoIs and everything seems to be set correctly.  I have checked
> > with my DSL provider and all ports are open.  The only thing I can 
> > figure is that it must be something in this BIND configuration and
the
> 
> > way I have it set up.  Is there any documentation that can explain
> this
> > better? Or anyone out there that might know more than me, since I am
> > just a beginner anyway.
> > 
> > Thanks,
> > Kelly
> 
> 
> --
> Mark Johnson-Barbier


--
Mark Johnson-Barbier



-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to