Hello David,
> After further investigation I discovered the problem is the forwarder is
> not responding. The DNS server has a private IP address and the forwarder is a
> public ip address. There is a firewall between the two servers. What is
> required to get replys back from t
After further investigation I discovered the problem is the forwarder is
not responding. The DNS server has a private IP address and the forwarder
is a public ip address. There is a firewall between the two servers.
What is required to get replys back from the forwarder?
david
On Fri, 15 Dec
Hi Michael
If I stop named. All network connections work properly (including ping
internet addresses)
When I start named I can no longer ping any ip address not in dns. I
cannot do a lookup of any ip address not in the local domain
All local domain entries are pingable and can be looked up
dav
Hi Lenord
If I stop named, then ping works correctly. If I ping an address in the
DNS then it works. It looks to me like I have DNS configured incorectly
for looking up external addresses.
david
On Fri, 15 Dec 2000, Leonard den Ottolander wrote:
> Hi again David,
>
> > Even a
I have the HOWTO and unfortunately, to me it looks like everything is
correct
david
On Fri, 15 Dec 2000, Leonard den Ottolander wrote:
> Hi David,
>
> > I have almost figured out how to get DNS working. The one thing piece I
> > need help with is requests outside my domain.
>
Well, we're going to have to look more at your networking issues. If
you can not ping anything outside your network, you're looking at
other problems...not DNS, as Leonard noted.
Do you have your gateway and netmask set properly?
On Fri, 15 Dec 2000 15:05:48 -0500 (EST), David Brett wrote:
>He
Here is the contents of the /etc/resolv.conf file. The last two
entrys I put in to see if this would help. I also tried nameserver as
127.0.0.1 as well. None of these configurations worked. I did restart
named after each change
domain company.com
search company.com
nameserver 10.1.100.9
True...but if "nameserver 127.0.0.1" isn't included in that
resolv.conf file, lookups won't work. Also, even if it is included,
if the connection to the net isn't there, it won't work, either.
In other words, as long as you have a working DNS setup on 127.0.0.1,
and a connection to the net, it s
Hi again David,
> Even a
> ping to an IP address on the internet from the DNS server fails as well.
A little oversight from me here. If you can't ping an IP address something
else is wrong. You don't need DNS for this, because you are not resolving
names in this case. Maybe so
Hi David,
> I have almost figured out how to get DNS working. The one thing piece I
> need help with is requests outside my domain.
It's been a while since I have done anything with DNS, but I set up a DNS for
a tiny domain over a year ago. I don't remember any of the details,
Hi Michael,
> What do you have as the contents of your /etc/resolv.conf file?
>
> You need to have at least one valid DNS server listed in that file in
> order for outside lookups to work. Two or three is even better.
The machine that is the DNS only needs a reference to itsel
What do you have as the contents of your /etc/resolv.conf file?
You need to have at least one valid DNS server listed in that file in
order for outside lookups to work. Two or three is even better.
On Fri, 15 Dec 2000 12:37:14 -0500 (EST), David Brett wrote:
>I have almost figured out how to g
I have almost figured out how to get DNS working. The one thing piece I
need help with is requests outside my domain. DNS is working for lookups
and reverse lookups within the domain I have set-up. What does not work
is the forwarders. i.e. nslookup www.yahooo.com. this fails. Even a
ping to
13 matches
Mail list logo
