[BlueOnyx:09226] Re: named and authentication problems

[Kevin Anderson]

As a general rule, C names break things.  Most commonly email.

It's probably better to always use A records.  It's a bit more work when things change, but it's way less trouble the rest of the time.

Kev.



----- Original Message -----
From: Gregg <greggk1 at cox.net>
Sent: Tue, 12/13/2011 9:48am
To: "'BlueOnyx General Mailing List'" <blueonyx at mail.blueonyx.it>
Subject: [BlueOnyx:09225] Re: named and authentication problems

 
 
From: blueonyx-bounces at mail.blueonyx.it [mailto:blueonyx-bounces at mail.blueonyx.it] On Behalf Of Chuck Tetlow
Sent: Monday, December 12, 2011 11:50 PM
To: BlueOnyx General Mailing List
Subject: [BlueOnyx:09222] Re: named and authentication problems
 
> I solved the DNS issue, it was one of the zones was not added in correctly, 
> even though it looked like it was through the gui. Resolution was to remove 
> it completely from the gui, and re add it. 
> 
> If the resolver is not working, how can I check to see why? And how to fix 
> it? 
> Tnx 


Go into the management GUI.  Click SERVER MANAGEMENT at the top.  On the left side - click SYSTEM SETTINGS and TCP/IP.  The second window down is where you list the DNS servers for your BX server to use.  

This is not the area for the domains on your box, but the DNS servers your server uses (like your ISP's DNS servers, or the ones in the NOC where your server is located). 

If those DNS servers are not set - the most common symptom is a long wait to log in via SSH or FTP.  Its a timeout while the server attempts to do a reverse lookup and get a name for the logs (instead of just the IP).  But once in - switching user doesn't occur any delay. 

One thing to remember - if the system you use to SSH from is listed in one of your own DNS server's domains, you'll suffer that delay whenever your own DNS servers are down. 

Fix that DNS resolution problem, and your delay will go away. 

As soon as I fixed the DNS issue, the delay did go away, the authentication now is instant.  I still don't know though why when I add a CNAME record to a particular domain, it is bringing down the DNS
The CNAME record I'm adding is like this. schedule.domain.com alias to schedule.someotherdomain.com
As soon as I save that record, it kills BIND.
When I look at the  messages log file it says that there is an error in the configuration, and what I can see from the log files, it loads up all the domain names, but when it comes to that one it has something like _default domain.com etc .  I think the _default tag is what causing bind to not load up, but I don't know why a simple alias could do that.
Thanks for all the help :)
_______________________________________________
Blueonyx mailing list
Blueonyx at mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx