Hi all,
I have a Redhat v9 box that is incapable of resolving certain specific
DNS addresses, but it can resolve others. Addresses that work:
www.google.com
www.is.co.za
www.anazi.co.za
Addresses that do not work:
www.yahoo.com
www.apple.com
An attempt to resolve the packet looks like this:
PROTECTED]
Sent: Friday, September 05, 2003 9:11 AM
To: [EMAIL PROTECTED]
Subject: DNS problems from the twilight zone
Hi all,
I have a Redhat v9 box that is incapable of resolving certain specific
DNS addresses, but it can resolve others. Addresses that work:
www.google.com
www.is.co.za
their queries specifically?
Regards,
Graham
--
-Original Message-
From: Graham Leggett [mailto:[EMAIL PROTECTED]
Sent: Friday, September 05, 2003 9:11 AM
To: [EMAIL PROTECTED]
Subject: DNS problems from the twilight zone
Hi all,
I have a Redhat v9 box that is incapable of resolving certain
On Fri, 2003-09-05 at 09:10, Graham Leggett wrote:
Hi all,
I have a Redhat v9 box that is incapable of resolving certain specific
DNS addresses, but it can resolve others. Addresses that work:
www.google.com
www.is.co.za
www.anazi.co.za
I would think that your problem is with your NS
David Hart wrote:
I would think that your problem is with your NS provider (The Internet Solution).
Have you tried a caching name server with the ISP as backup?
I have tried about 5 or 6 different nameservers, some on the ISP's
network, some on external networks. As a control, I have run the
At 01:32 6/09/2003, you wrote:
Jason Staudenmayer wrote:
Sounds like a bad routing table. Like the resolve file is set right but the
return route for the packets is bad. Had something similar with a win2k box
and Pcanywhere. It would receive the first packet but couldn't return them.
A bad
On Fri, 2003-09-05 at 09:42, Graham Leggett wrote:
David Hart wrote:
I would think that your problem is with your NS provider (The Internet Solution).
Have you tried a caching name server with the ISP as backup?
I have tried about 5 or 6 different nameservers, some on the ISP's
Steve Phillips wrote:
Anybody heard of Akadns before? Anyone know why a Redhat v9 box cannot
resolve their queries specifically?
This is Akamai - a world wide distributed web system that runs primarily
via DNS and some fancy layer4 routing.
I figured that it might be Akamai, but whois linked
At 02:10 6/09/2003, you wrote:
Steve Phillips wrote:
Anybody heard of Akadns before? Anyone know why a Redhat v9 box cannot
resolve their queries specifically?
This is Akamai - a world wide distributed web system that runs primarily
via DNS and some fancy layer4 routing.
I figured that it might
I was able to get it working by adding the following commands to iptables.
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
I found this solution while searching Usenet. However, since I'm still
very new to RH and iptables, I'm a little nervous about entering these
lines. Am I opening any
the 'lo' in the command means Loopback, its the 127.0.0.1 address.
/B
- Original Message -
From: Dana Holland [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, March 25, 2003 13:58
Subject: Re: DNS problems NOT fixed
I was able to get it working by adding the following commands
I only thought I had corrected my DNS problems. It seems that the dig
command:
dig @205.165.189.182 189.165.205.in-addr.arpa soa
works fine if I'm on that box, but if you issue it from any other box,
you get the following message:
[EMAIL PROTECTED] /root]# dig @205.165.189.182 189.165.205
Dana Holland said:
I'm at a complete loss here - why would I be getting this error message?
check the DNS logs on the box, tune the log configuration on BIND
if you need to, my log configuration for BIND 8 is below(seems similar
to what BIND 9 uses):
logging {
channel chroot_default {
file
I believe I solved the problems I was having with secondary DNS. The first
problem was that I didn't have an entry in the named.conf file for the
reverse zone. The second problem was that when I did put in the entry, I
listed the IP of the master as ...89... instead of ...189 Amazing how
Dana Holland said:
I
think this one falls into the well, duh! category.
that or the *smack* category :)
nate
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
I'm having trouble getting secondary DNS working on my RH 8.0 box. This
is my first attempt at using a Linux box for DNS - in the past I've
always worked with AIX. The primary DNS server is on AIX currently.
Below is the output for the dig commands - dns... is the primary server,
while
-Original Message-
From: Dana Holland
Sent: Friday, March 21, 2003 3:53 PM
Subject: DNS problems
I'm having trouble getting secondary DNS working on my RH 8.0
box. This is my first attempt at using a Linux box for DNS -
in the past I've always worked with AIX. The primary DNS
box have anything to do
with it?
Cowles, Steve wrote:
-Original Message-
From: Dana Holland
Sent: Friday, March 21, 2003 3:53 PM
Subject: DNS problems
I'm having trouble getting secondary DNS working on my RH 8.0
box. This is my first attempt at using a Linux box for DNS -
in the past
I got the DNS HowTo and am going thru just like it says. I'm just trying to
get the nslookup to find itself(127.0.0.1) which is the computer I'm going
to setup the DNS on. Anyways, first thing I've done is gone into the
named.conf file and have 1 entry
options{
directory
snip
I got the DNS HowTo and am going thru just like it says. I'm just trying to
get the nslookup to find itself(127.0.0.1) which is the computer I'm going
to setup the DNS on. Anyways, first thing I've done is gone into the
named.conf file and have 1 entry
options{
directory
Stephen,
You have to have a separate zone file for each domain name, and a separate
zone "x.x.xxx.in-addr.arpa" file for each IP address you use, including
static IP addresses through your ISP and any LAN addresses you use. These
have to be referenced in your /etc/named.conf file.
Note that
Hi all!
I am running into a problem with accessing a DNS server in my local
network from a client. If I ping directly from the client to the DNS
server, I get a response as normal, but when I try to access an outside
site, it says it can't find the name server. I tried changing the
nameserver
This looks to me like a reverse DNS setup issue
At 08:07 AM 9/7/00 -0100, you wrote:
Hi all!
I am running into a problem with accessing a DNS server in my local
network from a client. If I ping directly from the client to the DNS
server, I get a response as normal, but when I try
I've been trying to figure out reverse DNS on both windows and
linux for a while I've had no luck, and had to put it on the back
burner... Sorry I couldn't provide more info...
Fred
At 08:07 AM 9/7/00 -0100, you wrote:
Hi all!
I am running into a problem with accessing
-Original Message-
From: Rodrigo Moya [EMAIL PROTECTED]
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Thursday, September 07, 2000 4:31 AM
Subject: DNS problems
Hi all!
I am running into a problem with accessing a DNS server in my local
network from a client. If I ping directly from
Hi Tony
I don't think I have missed anything unless you can spot it!!
No. RTFM, there are some misconceptions about the "VirtualHost"
directive. You need to do it like this:
NameVirtualHost 194.70.240.235
I used linuxconf to setup the VH and checked the config with
Hi Forrest
You may need to do something with your httpd.conf. Add something under
the virtual domains named www.company-domains.net and see if that works.
I have the following defined in httpd.conf:
VirtualHost www.company-domains.net
ServerAdmin [EMAIL PROTECTED]
Dear All
I wonder if I could pick your brains on a DNS issue?
I have ns.company-domains.net visible on the internet but not www.company-
domains.net! I have aliased the second nic as 'ns www linux' in
linuxconf and the zone file for company-domains.net is:
@ IN SOA
I believe this should be:
@ IN NS ns
@ IN NS ns.company-domains.net.
@ IN MX 10 mail
@ IN MX 10 mail.company-domains.net.
localhost IN A 127.0.0.1
gateway IN A
Got a problem I hope someone can help with, problem follows:
Log entries ...
Jun 21 23:58:21 router named[8365]: starting. named 4.9.6-REL Tue Mar 31
13:35:17 EST 1998
^[EMAIL PROTECTED]:/usr/src/redhat/BUILD/bind-4.9.6/named
Jun 21 23:58:21 router named[8365]: cache zone "" loaded (serial 0)
On Mon, 22 Jun 1998, Paul Fontenot wrote:
Got a problem I hope someone can help with, problem follows:
Couple of problems with this zone file.
Jun 21 23:58:21 router named[8365]: named.forward:1: expected a number
Indicative of having your parenthesis at the end of the first line
pointing
Hi,
At 12:06 AM 6/22/98 -0700, Paul Fontenot [EMAIL PROTECTED] wrote:
Got a problem I hope someone can help with, problem follows:
See below for answers ...
Log entries ...
Jun 21 23:58:21 router named[8365]: starting. named 4.9.6-REL Tue Mar 31
13:35:17 EST 1998
^[EMAIL
And the offending named.forward file ...
cuda.org. IN SOA router.cuda.org. root.router.cuda.org. )
1998072101 ; Serial Number
10800 ; Refresh after 3 hours
3600; Retry after 1 hour
-+-And the offending named.forward file ...
-+-
-+-cuda.org. IN SOA router.cuda.org. root.router.cuda.org. )
-+-
-+-UMMM,^ bingo
Damn, it's getting late when you overlook that...
-Paul
--
PLEASE read the Red Hat FAQ,
On Mon, 22 Jun 1998, Paul Fontenot wrote:
Got a problem I hope someone can help with, problem follows:
Log entries ...
Jun 21 23:58:21 router named[8365]: starting. named 4.9.6-REL Tue Mar 31
13:35:17 EST 1998
^[EMAIL PROTECTED]:/usr/src/redhat/BUILD/bind-4.9.6/named
Jun 21 23:58:21
35 matches
Mail list logo
