BIND rndc problem

[Kevin Darcy]

Well, if you're not going to answer my questions or use real domain names, I
can't really help you...


- Kevin

Mike Kinzie wrote:

> Kevin,
> No. In the SOA it is the domain address of the company that is colocating my
> machine.
> I have for my nameservers:
> ns1.mydomain.ca
> lancelot.myserviceprovider.com
>
> what happens when I use "dig any mydomain.ca" ths ANSWER SECTION list first
> of all
>
> ns1.myserviceprovider.com  hostmaster.myserviceprovider.com
>
> then
> mydomain.ca  21600 IN NS ns1.myserviceprovider.com
> mydomain.ca  21600 IN NS mydomain.ca (without the ns1)
> mydomain.ca  21600 IN MX 10 smtp-fe.myserviceprovider.com
> mydomain.ca  21600 IN MX xxx.xx.xxx.xx (my IP)
>
> I do not see how ns1 becomes part of myserviceprovider's domain when it
> isn't
>
> My zone data file for mydomain.ca is mainly:
>
>                             IN     SOA     ns1.mydomain.ca
> hostmaster.mydomain.ca
>
>           2003080900 etc
>
> ;nameservers
>                             IN    NS    ns1.mydomain.ca.
>                             IN    NS    lancelot.myservicprovider.com.
> mydomain.ca.       IN    MX    10 mail.mydomain.ca.
> www                    IN    CNAME ns1.mydomain.ca
>
> mydomain.ca.        IN    A    xxx.xx.xxx.xxx  (my address)
> ns1                        IN    A  xxx.xx.xxx.xxx  (my address)
> localhost                IN    A    127.0.0.1
>
> All the syntax of the files are ok.
>
> I do not seee wher things get mixed up.
> Can the problem be with the company who is colocatting the machine and who
> has assigned an
> address to me.
>
> Thanks
>
> Mike
>
> "Kevin Darcy" <kcd at daimlerchrysler.com> wrote in message
> news:bh1cck$292d$1 at sf1.isc.org...
> > Mike Kinzie wrote:
> >
> > > Hi,
> > >  I "think" my problem is that the SOA when I " dig any mydomain" brings
> up
> > > my IP's or secondary name server's address rather than mine ie: my.ip's.
> > > domain.   hostmaster.my.ip's.domain.
> >
> > I'm not sure what you mean by this. Do you literally mean there's an IP
> address
> > there? If so, then apparently you accidentally used IP addresses in your
> > SOA record instead of names.
> >
> > > I can ping my domain from a web browser site but not when I am logged on
> via
> > > a terminal
> >
> > I asked you earlier whether your machine was configured to resolve names
> via
> > DNS. I don't think you've answered that yet.
> >
> > > I have gone over and over the named.conf and zone files but have not
> found
> > > the problem.
> > > the syntax via named-checkzone comes up fine.
> > >
> > > Could this be the main reason with the "localhost" referring to my ip's
> > > address rather than my machine's?
> >
> > Seems more and more like your machine is not configured to use DNS for
> name
> > resolution.
> >
> > See
> http://www.europe.redhat.com/documentation/man-pages/man5/nsswitch.5.php3
> >
> >
> > - Kevin
> >
> > > "Kevin Darcy" <kcd at daimlerchrysler.com> wrote in message
> > > news:bgufgb$1rjg$1 at sf1.isc.org...
> > > > Mike Kinzie wrote:
> > > >
> > > > > hello,
> > > > > I have Redhat 8 with BIND 9.2.1
> > > > > rndc has stopped working and I cannot ping my domain or 127.0.01
> > > > > I have checked my /va/log/messages and found the following with
> regard
> > > to
> > > > > the named server startup on a reboot:
> > > > >
> > > > > -couldn't find rndc key for use with command channel: 127.0.0.1#953
> > > > > I have the following in named.conf:
> > > > >
> > > > > controls {
> > > > >         inet 127.0.0.1 allow { localhost; } keys { rndc_key; };
> > > > > };
> > > > >
> > > > > all the zone files loaded okay.
> > > > >
> > > > > I do not understand the command channel and how to correct the rndc
> > > failure.
> > > >
> > > > The BIND 9 documentation tells how to set up rndc. Basically you need
> to
> > > > generate a key.
> > > >
> > > > The failure to set up an rndc channel shouldn't have any direct
> > > relationship to
> > > > your inability to resolve names, though. Although it's encouraging
> that
> > > you are
> > > > looking in the log file for error messages (so many people forget that
> > > step) do
> > > > you have any other information about that problem beyond "I cannot
> ping my
> > > > domain or 127.0.01" and "all the zone files loaded okay"? Have you
> tried
> > > > querying the nameserver with a DNS lookup tool like "dig"? Is your
> machine
> > > even
> > > > configured to use DNS for name resolution? If you turn on query
> logging,
> > > do you
> > > > see the query attempts being logged? Does a "netstat" show anything
> > > listening
> > > > on port 53?
> > > >
> > > >
> > > > - Kevin
> > > >
> > > >
> > > >
> > > >
> >
> >