Re: Firefox and Flash ...
Just a thought, are you using a 64-bit processor? I remember back in my Linux user days that Macromedia was not willing to release a 64-bit version for alternative operating systems Kiffin Gish wrote: I know I am not the first nor more than likely the last, but I cannot for the life of me get Flash to work in Firefox 1.0.6 on FreeBSD 5.4. I've tried everything according to the FreeBSD handbook, mailing lists, etc, but still when there is a page with Flash, poor Firefox chokes and dies. One thing interesting I noticed though, which might be a hint, is that if I exit Xfce, logout, login this time as root, fire up Xfce again and then run Firefox, everything works without a hitch, e.g. even flash-based pages don't crash Firefox. Weird. What gives? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
centralized address book
My organization lost its Exchange server, and now users are wanting to have a common address book that they call all use, so anyone can start typing Joe Blo.. and his address pops up in their mail client. They're all using Outlook and I was thinking - is this a job for openldap? I haven't done an ldap installation before, but I thought this would be a good use for it. Am I correct in assuming that? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
speed up bind9?
The single dns I am running resolves...eventually. I have not set up a secondary name server (caching) but I plan to. Our proxy server is querying my one-and-only dns but often queries time out. Is there a way to optimize the performance of the dns? The same box handles httpd, postfix, and spamd, so I realize there may not be much else I could do. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: speed up bind9?
I had read where the bind9 implementation of IPv6 was a bit flaky, so I found that tip and am trying it. Doesn't seem to change things though. Henrik Lidström wrote: Jerod Prothe wrote: The single dns I am running resolves...eventually. I have not set up a secondary name server (caching) but I plan to. Our proxy server is querying my one-and-only dns but often queries time out. Is there a way to optimize the performance of the dns? The same box handles httpd, postfix, and spamd, so I realize there may not be much else I could do. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Hi, try starting bind with the -4 flag. See if that helps. /Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
dns resolutions -- again
Hello all, I contacted this list a few weeks ago (got good responses - thanks) but now it seems that other domains are still not getting refreshed. I set my zone file refresh at 20m. Why is it that our domain (usd217.org) gets recognized by other domains (example: acck.edu) but not by my isp (pld.com). I called them to ask for them to clear their cache but they seem unwilling and not responsive. The old server (otto) should not be getting asked to handle mail, but unfortunately, others' records seem to indicate that. How can I get this changed throughout the internet? Thanks. Jerod ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mail malady - dns/postfix
Greetings all,
On my network, we used to have some NT box acting as the mail exchanger and a
faulty dns for our domain. That box has nearly crumbled. It's still active,
but no longer accepting mail. I set up a computer (called galley) with 5.4 and
it is (supposedly) running authoritative dns for our domain, and is handling
mail via postfix. Since I changed the dns, I alerted our registrar, which was
originally doing lookups for us.
The problem is, now local citizens are trying to send mail to us, but they are
getting bounce messages reporting that it couldn't talk to otto, the old NT box.
Here is my /etc/namedb/named.conf :
// $FreeBSD: src/etc/namedb/named.conf,v 1.15.2.3 2005/03/23 17:35:58 dougb Exp
$
//
options {
directory /etc/namedb;
allow-query { any; };
recursive-clients 15000;
pid-file /var/run/named/pid;
forwarders {
209.42.72.2;
};
};
zone . {
type hint;
file named.root;
};
zone 0.0.127.IN-ADDR.ARPA {
type master;
file localhost.rev;
};
/*
zone domain.com {
type slave;
file s/domain.com/bak;
masters {
192.169.1.1;
};
};
zone 0.168.192.in-addr.arpa {
type slave;
file s/0.168.192.in-addr.arpa.bak;
masters {
192.168.1.1;
};
};
*/
zone usd217.org {
type master;
file db.usd217.org;
};
zone 72.42.209.in-addr.arpa {
type master;
file usd217-reverse;
};
key rndc-key {
algorithm hmac-md5;
secret VR7Bsxrqrrtf38pGNzog1A==;
};
controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { rndc-key; };
};
And here is my /etc/namedb/localzone:
; Definition of zone usd217.org
$TTL 1d
usd217.org. IN SOA galley.usd217.org techcoord.usd217.org. (
2005082601 ; Serial (date, 2 digit version of day)
1d ; refresh
1h ; retry
100d; expire
1h ); negative cache entry
; name servers
IN NS ns
; MX records
IN MX 50 galley.usd217.org.
ns IN A209.42.72.2
; Host
localhost IN A127.0.0.1
galley IN A209.42.72.2
bess-proxy IN A209.42.72.247
ottoIN A209.42.72.250
; nickname
www IN CNAMEgalley
ftp IN CNAMEgalley
There may be more at stake here: If this doesn't work well, then any
credibility that I have with my employer concerning using open-source may be
exhausted. Any other conf's I should show?
Thanks
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mail malady - dns/postfix
Norberto Meijome wrote: Jerod, pls define 'local citizens'. My view of local is surely different to yours. Good question: local as in residents down the street in the same small town yup, # telnet otto.usd217.org 25 Trying 209.42.72.250... telnet: Unable to connect to remote host: Connection refused BTW: whois usd217.org [...] Name Server:GALLEY.USD217.ORG Name Server:OTTO.USD217.ORG From Sydney, AU, the DNS records seem to have propagated: $ nslookup.exe Default Server: x Address: 10.168.100.10 set type=ns usd217.org Non-authoritative answer: Server: x Address: 10.168.100.10 usd217.org nameserver = otto.usd217.org usd217.org nameserver = galley.usd217.org otto.usd217.org internet address = 209.42.72.250 galley.usd217.org internet address = 209.42.72.2 and MX: usd217.org mail exchanger = 50 galley.usd217.org. but from TX,USA: # nslookup set type=ns usd217.org Server: 207.218.192.38 Address:207.218.192.38#53 usd217.org nameserver = rolla.usd217.org. usd217.org nameserver = ns1.pld.com. usd217.org nameserver = ns2.pld.com. usd217.org nameserver = pta6000.pld.com. and MX: usd217.org MX preference = 10, mail exchanger = otto.usd217.org otto.usd217.org internet address = 209.42.72.251 Otto is not supposed to handle mail for our domain AT ALL. It shouldn't be. Our ISP does want to have our MX records since they do not host our dns, at least that was what their representative said when I told her of my network changes. so it seems that, to begin with, you have some inconsistency in what we can see of your network, the answers i'm seeing from this USA-based NS being the old ones. Notice that from USA, I'm getting MX pointing to otto., which it seems not to be taking connections on tcp/25. galley OTOH smtp listening on tcp/25. There may be more at stake here: If this doesn't work well, then any credibility that I have with my employer concerning using open-source may be exhausted. this doesnt seem at all a problem of 'MS is better than OS' or otherwise (wont enter in that argument anyway) - just DNS not propagated yet, and not much you can do about that but to wait it out, other than giving otto's IP to galley for the time being so all smtp traffic goes to the box that is working. I'm not making it out to be an os holy war, but the powers that be say but we've always used Windows, why use something else? Next time, you may want to reduce your refresh settings in your zone before you perform a drastic change. Any other conf's I should show? I'm not too sure the exact configuration you have / intend to have. do you want galley to forward emails to otto? galley should be the sole handler of mail, coming and going. Otto should have nothing to do with our services anymore. Notice that I'm able to send and receive to this list without any trouble. My computer (this is my first month at this job) was statically set to use otto for lookups. So is every other computer at my employment. I know I'll need to change everyone's settings (probably a Labor Day weekend project.) regards, beto I really do appreciate your response. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mail malady - dns/postfix
Greg Barniskis wrote: Jerod Prothe wrote: Greetings all, On my network, we used to have some NT box acting as the mail exchanger and a faulty dns for our domain. That box has nearly crumbled. It's still active, but no longer accepting mail. I set up a computer (called galley) with 5.4 and it is (supposedly) running authoritative dns for our domain, and is handling mail via postfix. Since I changed the dns, I alerted our registrar, which was originally doing lookups for us. The problem is, now local citizens are trying to send mail to us, but they are getting bounce messages reporting that it couldn't talk to otto, the old NT box. [config snipped] There may be more at stake here: If this doesn't work well, then any credibility that I have with my employer concerning using open-source may be exhausted. Any other conf's I should show? At a glance (not thorough inspection) your config looked OK. Expire time of 100 days seems a bit long. When I nslookup MX for your domain, I get the addr of your new server galley, so no apparent problem there (although I see from a follow-up post that some folks are getting MX = otto, and *that* is your problem in a nutshell). If otto is no longer providing any services to the outside world, how about just indicating via DNS that otto is CNAME to galley? CNAME to galley? That's a good idea. I changed it and reduced the expire time to 10d (I got it out of the Lehey Complete FreeBSD book). I wonder why it is that Australia has updated but a US State has not? Thanks for your help. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
