Benoit POSTE wrote:
Sorry ... mail server problems ...
I'm having problems here too - just got your message. There seems to be a time delay of quite a few hours for most messages between iname.com receiving a message and it forwarding it on to my real account :(
First (perhaps obvious) question is: is DNS actually running on the router?
err ... maybe you hit the right point ... toughest question actually ;) ... all I know is that I used (or tried to use) Yast to set it up ... how exactly do I check that it is running? (and if, as I suspect, it is not, how do I make it run?) As you may have noticed, I am no good with nameservers.
As root: 'rcnamed status' should tell you whether or not DNS is running. You don't necessarily need to set up DNS on you Linux box - you could always just feed Windows the IP addresses of your ISPs nameservers. Windows would then contact your ISPs DNS servers directly, rather than speaking to the Linux box, which then speaks to the ISPs DNS servers and passes the result back to the Windows box. Follow that? ;-) If 'rcnamed status' doesn't return "OK", then you can try to restart the DNS server with 'rcnamed restart'. The relevant variable in /etc/rc.config is, I think, START_NAMED, and it should be set to "yes". One other thing that you will need to do, is to edit /etc/named.conf. Find the options section towards the start of the file. Within the options section, you want the forwarders subsection. Inside the forwarders subsection, you need to put the IP addresses of your ISPs DNS servers (comment out the ones already there, if they're not already commented out). Once you've edited the configuration file, restart the server as before. Then try pinging google.com or some other high-profile host.
For testing purposes *only*, use the following commands once you've booted up the router: echo 1 > /proc/sys/net/ipv4/ip_forward ipchains -P input ACCEPT ipchains -P forward MASQ ipchains -P output ACCEPT This will allowing anything and everything...
Well, I must say it worked better: I actually could ping 216.239.35.100 ... and that's about it, nothing else would work.
Try again with this configuration of the router. If this still doesn't work, blame Windows. Do a 'route print' on the Windows box. This should produce something like: 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.2
I get nothing that simple ... more in the lines of 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.2 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2 192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1 192.168.0.255 255.255.255.255 192.168.0.2 192.168.0.2 224.0.0.0 224.0.0.0 192.168.0.2 192.168.0.2 255.255.255.255 255.255.255.255 192.168.0.2 0.0.0.0 ... no idea why it is so messed up ... maybe Webwasher did this ... anyhow, first line is OK, so I guess it is still all right.
Don't worry about it - I just extracted the most relevant part. But you're right, Windows routing tables are *ugly*.
You could also try to ping 216.239.35.100 (google.lb.google.com) to see if it's a DNS problem.
As I said, ping 216.239.35.100 worked (windows box), but ping google.lb.google.com just stayed there. So this is probably a DNS problem, only I do not know how to correct it. Any pointer?
Yes, almost definitely a DNS problem.
By the way, I was searching through the SuSE manual, and found a section about masquerading and firewalling that I hadn't noticed at first (a few more things to change in the rc.config), is this what I should use once I get my DNS working?
Having just had a look at the manual - yes, that section looks pretty comprehensive. I, personally, roll my own firewalling scripts rather than rely on SuSE to get it right (although I'm sure they do a good job). I would say to go with what it says in the manual. Hope that helps some more, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
Hello again Chris, hello all ...
I'm having problems here too - just got your message. There seems to be a time delay of quite a few hours for most messages between iname.com receiving a message and it forwarding it on to my real account :(
Same here, happens from time to time when I use my yahoo account. <snip>
As root: 'rcnamed status' should tell you whether or not DNS is running. You don't necessarily need to set up DNS on you Linux box - you could always just feed Windows the IP addresses of your ISPs nameservers. Windows would then contact your ISPs DNS servers directly, rather than speaking to the Linux box, which then speaks to the ISPs DNS servers and passes the result back to the Windows box. Follow that? ;-)
I think I did. I hope I did. Now there's still one thing that had me wonder to no end. When connecting directly to the internet (whether on the linux box or the win98 box), there is absolutely no need to set up the DNS (manually at least) and everything works like a charm. But when I connect with the Win98 through the Linux gateway/router, it looks like I must set the DNS, either in the win98 or in the linux box. Why is that so? Isn't there such a thing as "auto DNS forwarding" or something?
If 'rcnamed status' doesn't return "OK", then you can try to restart the DNS server with 'rcnamed restart'. The relevant variable in /etc/rc.config is, I think, START_NAMED, and it should be set to "yes".
One other thing that you will need to do, is to edit /etc/named.conf. Find the options section towards the start of the file. Within the options section, you want the forwarders subsection. Inside the forwarders subsection, you need to put the IP addresses of your ISPs DNS servers (comment out the ones already there, if they're not already commented out). Once you've edited the configuration file, restart the server as before. Then try pinging google.com or some other high-profile host.
I'll try all that this evening, and I'll tell you how it worked. <snip>
Hope that helps some more, Chris
It does, it almost feels like I'm beginning to understand things ;). Benoit.
Benoit POSTE wrote:
As root: 'rcnamed status' should tell you whether or not DNS is running. You don't necessarily need to set up DNS on you Linux box - you could always just feed Windows the IP addresses of your ISPs nameservers. Windows would then contact your ISPs DNS servers directly, rather than speaking to the Linux box, which then speaks to the ISPs DNS servers and passes the result back to the Windows box. Follow that? ;-)
I think I did. I hope I did. Now there's still one thing that had me wonder to no end. When connecting directly to the internet (whether on the linux box or the win98 box), there is absolutely no need to set up the DNS (manually at least) and everything works like a charm. But when I connect with the Win98 through the Linux gateway/router, it looks like I must set the DNS, either in the win98 or in the linux box. Why is that so? Isn't there such a thing as "auto DNS forwarding" or something?
When you dial up, your ISP will assign you an IP address automatically using a protocol known as DHCP. Using DHCP, it is possible to specify more than just an IP address - many ISPs also provide their default gateway and DNS servers in this way. When either Windows or Linux dials up, the computer that dials up is given all the information it needs (IP address, default gateway, and DNS servers). When you try to connect your Windows box through your Linux box, it is the Linux box that receives all this information from your ISP - the Windows box receives nothing. The solutions to this are those that I've already mentioned - either you manually tell Windows the IP addresses of the DNS servers, or you set up DNS on your Linux box. Setting up DNS on your Linux box means that instead of pointing at your ISPs DNS servers, you can point Windows at your Linux box as a DNS server.
If 'rcnamed status' doesn't return "OK", then you can try to restart the DNS server with 'rcnamed restart'. The relevant variable in /etc/rc.config is, I think, START_NAMED, and it should be set to "yes".
One other thing that you will need to do, is to edit /etc/named.conf. Find the options section towards the start of the file. Within the options section, you want the forwarders subsection. Inside the forwarders subsection, you need to put the IP addresses of your ISPs DNS servers (comment out the ones already there, if they're not already commented out). Once you've edited the configuration file, restart the server as before. Then try pinging google.com or some other high-profile host.
Another step along the path to understanding ;-) Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
participants (2)
-
Benoit POSTE -
Chris Reeves