In a bind about named and network printing.

2002-12-03 Thread Paul Lewis
I have been playing with my local networks 'named' and finally got it 
working more or less the way I think it should. Evidence for this is 
that I can ping local machine name and it returns the fully qualified 
machine name plus the ping responces. This works on all machines except 
the server 'named' is actually running on. Where the ping goes off 
along the cable modem never to resolve (my network is strictly a local 
affair). So far so good.

What is really causing me to scratch my head is that suddenly ( at the 
same time ) the printer located on my server (the same server which 
runs named) no longer works for print jobs across the network. The 
print jobs are all queued on my debian machine but never get printed on 
my redhat server.

I am pretty sure it is related to my tinkerings but just can't see 
where the problem lies. Any suggestions?


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: In a bind about named and network printing.

2002-12-03 Thread Stephen Gran
This one time, at band camp, Paul Lewis said:
 I have been playing with my local networks 'named' and finally got it 
 working more or less the way I think it should. Evidence for this is 
 that I can ping local machine name and it returns the fully qualified 
 machine name plus the ping responces. This works on all machines except 
 the server 'named' is actually running on. Where the ping goes off 
 along the cable modem never to resolve (my network is strictly a local 
 affair). So far so good.

This seems like the problem here, actually.

 What is really causing me to scratch my head is that suddenly ( at the 
 same time ) the printer located on my server (the same server which 
 runs named) no longer works for print jobs across the network. The 
 print jobs are all queued on my debian machine but never get printed on 
 my redhat server.
 
 I am pretty sure it is related to my tinkerings but just can't see 
 where the problem lies. Any suggestions?

If the debian box can't resolve the print server, how can it send print
jobs to it?  Fix name resolution, either within named, or just add it to
/etc/hosts.
-- 
 --
|  Stephen Gran  | Horner's Five Thumb Postulate:  |
|  [EMAIL PROTECTED] | Experience varies directly with |
|  http://www.lobefin.net/~steve | equipment ruined.   |
 --



msg16768/pgp0.pgp
Description: PGP signature


Re: In a bind about named and network printing.

2002-12-03 Thread Alan Chandler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tuesday 03 December 2002 1:58 pm, Paul Lewis wrote:
 I have been playing with my local networks 'named' and finally got it
 working more or less the way I think it should. Evidence for this is
 that I can ping local machine name and it returns the fully qualified
 machine name plus the ping responces. This works on all machines except
 the server 'named' is actually running on. Where the ping goes off
 along the cable modem never to resolve (my network is strictly a local
 affair). So far so good.

Doesn't sound good to me, I would have expected a ping of yourself to work.

I am not sure of your topology, but for me I have a linux box (my dns server) 
also acting as a gateway between the local area network and the cable modem.  
This box has TWO ip addresses, one for each interface.  Your names must 
resolve to one or other of these two ip addresses, but not both.  

My dns server is in charge of the *.home domain, so I have names like 
roo.home, kanger.home and pooh.home (AA Milne eat your heart out) as internal 
names. roo.home is this gatway.  The dns server (bind) returns the ip address 
for roo.home from the interface on the internal network.  In my case thats 
10.0.10.100


But the server box can also be reached from the outside, and although its a 
dhcp allocated address and supposidely variable, it has not changed for for a 
year, so I have allocated the name home.chandlerfamily.org.uk on an outside 
dns service (this outside dns service is in charge of the 
chandlerfamily.org.uk domain).  When I ping using this name from within my 
network, the local dns server is asked for the name and initially goes to the 
outside dns service for the ip address, although bind then caches this 
locally for a short while.  Following requests do not need to go out to the 
internet.

I can ping either of the names of the box from within my local area network or 
from a shell account on the the box itself and both names, in both 
circumstances the box responds with the appropriate ip address that matches 
the name it was ping'ed with.

  
Solve this, and your other problem is probably solved.  If you want help here, 
more detail of ip addresses and names (change the names to equivalents if you 
want to maintain confidentiality) is needed, along with your various 
configuration files.

- -- 
Alan Chandler
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE97OoBuFHxcV2FFoIRArC1AJ9Fb5VZ/zx1gKIvRM6R0sxKvS0N+gCfRKXP
ythROyoeL7lY7+TQ/lOdIEE=
=9tm9
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: In a bind about named and network printing.

2002-12-03 Thread Gary Hennigan
Paul Lewis [EMAIL PROTECTED] writes:
 I have been playing with my local networks 'named' and finally got it
 working more or less the way I think it should. Evidence for this is
 that I can ping local machine name and it returns the fully
 qualified machine name plus the ping responces. This works on all
 machines except the server 'named' is actually running on. Where the
 ping goes off along the cable modem never to resolve (my network is
 strictly a local affair). So far so good.

How do your internal machines resolve external addresses? Does each of
them have a resolve.conf that points to your ISP nameservers, as well
as your internal nameserver, or do you have your internal name server
query your ISPs nameservers? You really want the latter to have
everything work the Right Way (TM).

I'm assuming you don't have your local bind configured to query your
ISP name server? That's probably what you need to do to fix things up
completely and then put into /etc/resolv.conf on your box running
named:
domain whatever.you.call.your.home.domain
search whatever.you.call.your.home.domain
nameserver 127.0.0.1
nameserver ISP nameserver #1 IP
nameserver ISP nameserver #2 IP

The 127.0.0.1 will cause your server to query itself first, then, if
necessary go to your ISP nameservers.

You'll have to look at the bind docs to see how to set up your bind
server to forward requests for external IPs to your ISPs
nameservers. In Bind 4 (my server ran OpenBSD), after you defined your
local zones in named.boot you put:

forwarders  10.x.x.x 10.x.x.x
options forward-only

replacing the two 10.x.x.x addresses with your ISPs nameserver
IP addresses

 What is really causing me to scratch my head is that suddenly ( at the
 same time ) the printer located on my server (the same server which
 runs named) no longer works for print jobs across the network. The
 print jobs are all queued on my debian machine but never get printed
 on my redhat server.
 
 I am pretty sure it is related to my tinkerings but just can't see
 where the problem lies. Any suggestions?

Fix the first prob, then the second may disappear. If not you can ask
again after the first problem is resolved!

Gary


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: In a bind about named and network printing.

2002-12-03 Thread Paul Lewis
On 2002.12.03 18:06 Gary Hennigan wrote:

Paul Lewis [EMAIL PROTECTED] writes:

So far so good.


How do your internal machines resolve external addresses? Does each of
them have a resolve.conf that points to your ISP nameservers, as well
as your internal nameserver, or do you have your internal name server
query your ISPs nameservers? You really want the latter to have
everything work the Right Way (TM).

I'm assuming you don't have your local bind configured to query your
ISP name server? That's probably what you need to do to fix things up
completely and then put into /etc/resolv.conf on your box running
named:
domain whatever.you.call.your.home.domain
search whatever.you.call.your.home.domain
nameserver 127.0.0.1
nameserver ISP nameserver #1 IP
nameserver ISP nameserver #2 IP


On 2002.12.03 18:06 Gary Hennigan wrote:

Paul Lewis [EMAIL PROTECTED] writes:

So far so good.


How do your internal machines resolve external addresses? Does each of
them have a resolve.conf that points to your ISP nameservers, as well
as your internal nameserver, or do you have your internal name server
query your ISPs nameservers? You really want the latter to have
everything work the Right Way (TM).

I'm assuming you don't have your local bind configured to query your
ISP name server? That's probably what you need to do to fix things up
completely and then put into /etc/resolv.conf on your box running
named:
domain whatever.you.call.your.home.domain
search whatever.you.call.your.home.domain
nameserver 127.0.0.1
nameserver ISP nameserver #1 IP
nameserver ISP nameserver #2 IP

The 127.0.0.1 will cause your server to query itself first, then, if
necessary go to your ISP nameservers.


Thanks to all three of you (Stephen, Alan and Gary), this reply seemed 
the easiest to try and it looks like it worked. After some addional 
spice thrown in by my dsl modem. Leastwise everything seems to be 
functioning normally now. My resolve file looks similar to this now 
except I did not include the domain. The docs, such as I have read them 
suggested they are incompatible together.

You'll have to look at the bind docs to see how to set up your bind
server to forward requests for external IPs to your ISPs
nameservers. In Bind 4 (my server ran OpenBSD), after you defined your
local zones in named.boot you put:

	forwarders  10.x.x.x 10.x.x.x
	options forward-only

replacing the two 10.x.x.x addresses with your ISPs nameserver
IP addresses


According to the HOW-TO is am working from the correct format for my 
named.conf is

forwarders first;
forwarders {
numeric ip ns1;
numeric ip ns2;
};



 I am pretty sure it is related to my tinkerings but just can't see
 where the problem lies. Any suggestions?

Fix the first prob, then the second may disappear. If not you can ask
again after the first problem is resolved!


Absolutely, spot on.



Gary

The 127.0.0.1 will cause your server to query itself first, then, if
necessary go to your ISP nameservers.


Thanks to all three of you (Stephen, Alan and Gary), this reply seemed 
the easiest to try and it looks like it worked. After some addional 
spice thrown in by my dsl modem. Leastwise everything seems to be 
functioning normally now. My resolve file looks similar to this now 
except I did not include the domain. The docs, such as I have read them 
suggested they are incompatible together.

You'll have to look at the bind docs to see how to set up your bind
server to forward requests for external IPs to your ISPs
nameservers. In Bind 4 (my server ran OpenBSD), after you defined your
local zones in named.boot you put:

	forwarders  10.x.x.x 10.x.x.x
	options forward-only

replacing the two 10.x.x.x addresses with your ISPs nameserver
IP addresses


According to the HOW-TO is am working from the correct format for my 
named.conf is

forwarders first;
forwarders {
numeric ip ns1;
numeric ip ns2;
};



 I am pretty sure it is related to my tinkerings but just can't see
 where the problem lies. Any suggestions?

Fix the first prob, then the second may disappear. If not you can ask
again after the first problem is resolved!


Absolutely, spot on.



Gary




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]