Re: Slow DNS Lookup (4TH POSTING)

2001-02-28 Thread Bram Dumolin
re, Alvin Oga([EMAIL PROTECTED])@Wed, Feb 28, 2001 at 03:55:02PM -0800: > what does the snippetts of your dns files look like ??? > > -- are you supporting more than one domain name on your lan ??? > > soa records > a records > ns records > ptr records > > $TTL > $ORIGIN > > contents of > na

Re: Slow DNS Lookup (4TH POSTING)

2001-02-28 Thread Martin Marconcini
Leonard, I am pasting my named files for you to crosscheck. I only have one zone here and it's an INTERNAL dns.. that means that resolves to 10.0.x.x/255.255.0.0 but It will also serve as a Cache Nameserver for other hosts. Sorry about the lenght of the email. - /etc/named.conf --

Re: Slow DNS Lookup (4TH POSTING)

2001-02-28 Thread Alvin Oga
hi ya leonard... what does the snippetts of your dns files look like ??? -- are you supporting more than one domain name on your lan ??? soa records a records ns records ptr records $TTL $ORIGIN contents of named.boot/named.conf c ya alvin On Wed, 28 Feb 2001, Leonard Leblanc wrote: > I am

Re: Slow DNS Lookup (4TH POSTING)

2001-02-28 Thread Bud Rogers
On Wednesday 28 February 2001 19:22, Leonard Leblanc wrote: > > Do you have reverse dns entries in your named configuration? If > > your internal hosts are doing reverse queries to your server and > > they're timing out, that could cause the delays you see. > > yes, i do have reverse dns entries i

Re: Slow DNS Lookup (4TH POSTING)

2001-02-28 Thread Leonard Leblanc
> Do you have reverse dns entries in your named configuration? If your > internal hosts are doing reverse queries to your server and they're > timing out, that could cause the delays you see. > yes, i do have reverse dns entries in my named configuration should i take them out? leonard

Re: Slow DNS Lookup (4TH POSTING)

2001-02-28 Thread Bud Rogers
On Wednesday 28 February 2001 16:19, Leonard Leblanc wrote: > > Since they are listed as SOA for the reverse domain, you can't fix > > it. You have to convince them to add the relevant entries. > > since getting them to change it is probably out of the question do > you know of any documents that y

Re: Slow DNS Lookup (4TH POSTING)

2001-02-28 Thread Leonard Leblanc
I made all of those changes, when i tried to ping (from the dns box) and of the domains (www, ftp, etc) I just kept getting ping: unknown host ftp.emergeknowledge.com ping: unknown host www.emergeknowledge.com etc etc etc Leonard

Re: Slow DNS Lookup (4TH POSTING)

2001-02-28 Thread Leonard Leblanc
> Since they are listed as SOA for the reverse domain, you can't fix it. > You have to convince them to add the relevant entries. > since getting them to change it is probably out of the question do you know of any documents that you can point me towards that will describe what kind of issues this

RE: Slow DNS Lookup (4TH POSTING)

2001-02-28 Thread Martin Marconcini
I have removed all but what I think you should change... db.emerge file: $ORIGIN emergeknowledge.com. /// THIS @ IN SOA ns.emergeknowledge.com. admin.emergeknowledge.com. ( 1 ; serial 8H ; refresh 2H ; retry 1W ; expire 1D) ; minimum, TTL NS ns.emergeknowledge.com. MX 1

Re: Slow DNS Lookup (4TH POSTING)

2001-02-28 Thread Bud Rogers
On Wednesday 28 February 2001 14:40, Leonard Leblanc wrote: > > [EMAIL PROTECTED]:~$ dig -x 64.59.157.18 > > > > ;; ANSWER SECTION: > > 18.157.59.64.in-addr.arpa. 1H IN PTR 64-59-157-18.ivideon.com. > > > > [EMAIL PROTECTED]:~$ dig soa 18.157.59.64.in-addr.arpa > > > > ;; AUTHORITY SECTION: > > 1

Re: Slow DNS Lookup (4TH POSTING)

2001-02-28 Thread Leonard Leblanc
> [EMAIL PROTECTED]:~$ dig -x 64.59.157.18 > > ;; ANSWER SECTION: > 18.157.59.64.in-addr.arpa. 1H IN PTR 64-59-157-18.ivideon.com. > > [EMAIL PROTECTED]:~$ dig soa 18.157.59.64.in-addr.arpa > > ;; AUTHORITY SECTION: > 157.59.64.in-addr.arpa. 1H IN SOA ns1.ivideon.com. isp.videon.ca. ( > >

Re: Slow DNS Lookup (4TH POSTING)

2001-02-28 Thread Leonard Leblanc
Sorry about the size of thisbut here's my config files: named.conf: options { directory "/var/cache/bind"; // If there is a firewall between you and nameservers you want // to talk to, you might need to uncomment the query-source // directive below. Previous

Re: Slow DNS Lookup (4TH POSTING)

2001-02-28 Thread Leonard Leblanc
D]> Cc: Sent: Wednesday, February 28, 2001 2:13 PM Subject: Re: Slow DNS Lookup (4TH POSTING) > When you type 'nslookup www.emergeknowledge.com' on your DNS server, > what is the full results? How about 'nslookup ' (to see if the > reverse is the same)? > &

Re: Slow DNS Lookup (4TH POSTING)

2001-02-28 Thread Bud Rogers
On Wednesday 28 February 2001 13:33, Leonard Leblanc wrote: > I am currently running a Debian 2.2 box as my DNS/www/ftp/ssh/etc etc > etc... Anyway the DNS lookup is working fine except for when the > internal machines try to look up 'www.emergeknowledge.com' which is > essentially local. When I a

Re: Slow DNS Lookup (4TH POSTING)

2001-02-28 Thread elysium
When you type 'nslookup www.emergeknowledge.com' on your DNS server, what is the full results? How about 'nslookup ' (to see if the reverse is the same)? This is a slow lookup from your DNS server as well as from other boxes using it as their DNS server over the network, right? What does your /et

Re: Slow DNS Lookup (4TH POSTING)

2001-02-28 Thread Peter Jay Salzman
leonard, it's hard to say since i have next to no info, but it sounds like you may want to look at tracerroute, ping and tcpdump. these three utilities, when taken together, can diagnost just about any network problem. (you may need to see output of tcpdump on the DNS server). pete On Wed 28 Fe

RE: Slow DNS Lookup (4TH POSTING)

2001-02-28 Thread Martin Marconcini
bject: Slow DNS Lookup (4TH POSTING) I am currently running a Debian 2.2 box as my DNS/www/ftp/ssh/etc etc etc... Anyway the DNS lookup is working fine except for when the internal machines try to look up 'www.emergeknowledge.com' which is essentially local. When I am working from hom

Slow DNS Lookup (4TH POSTING)

2001-02-28 Thread Leonard Leblanc
I am currently running a Debian 2.2 box as my DNS/www/ftp/ssh/etc etc etc... Anyway the DNS lookup is working fine except for when the internal machines try to look up 'www.emergeknowledge.com' which is essentially local. When I am working from home (yes i get to telecommute 4 days a week :)) I c