On 2013-08-31 20:25, Cristian Rodríguez wrote:

El 31/08/13 14:01, Carlos E. R. escribió:

...

So far, my only solution is to implement a DNS server, but I hesitate to do it as this machine has little ram (500M).

dnsmasq will do just fine.. it is used with routers that have waaaay less RAM (64 MB or so)

Mmm. +++·········· Lightweight, Easy-to-Configure DNS Forwarder and DHCP Server ··········++- It is a forwarder, not enough. It would have to accept a local definition for names. Ie, act as a real but small DNS. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)

On 2013-08-31 20:34, Cristian Rodríguez wrote:

El 31/08/13 14:32, Carlos E. R. escribió:

...

It is a forwarder, not enough. It would have to accept a local definition for names. Ie, act as a real but small DNS.

You say that because you have not read the documentation, please kindly RTFM ;-P

Ok, ok, I'll have a better look :-) -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)

On 2013-08-31 21:59, James Knott wrote:

Carlos E. R. wrote:

...

...

dnsmasq will do just fine.. it is used with routers that have waaaay

...

less RAM (64 MB or so) Mmm.

+++·········· Lightweight, Easy-to-Configure DNS Forwarder and DHCP Server ··········++-

It is a forwarder, not enough. It would have to accept a local definition for names. Ie, act as a real but small DNS.

I use dnsmasq here and it works fine for both IPv4 & IPv6 addresses. You just have to add local hosts into the /etc/hosts file and then restart dnsmasq. If you're using IPv6 and IPv4, you'll want to have the IPv6 address listed first.

Interestingly, it was already installed. You mean this thing reads the hosts file and that's it? Wow, it works... AmonLanc:~ # host telcontar telcontar.valinor has address 192.168.1.14 Host telcontar.valinor not found: 5(REFUSED) Host telcontar.valinor not found: 5(REFUSED) AmonLanc:~ # huh? AmonLanc:~ # host -v telcontar Trying "telcontar.valinor" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26366 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;telcontar.valinor. IN A ;; ANSWER SECTION: telcontar.valinor. 0 IN A 192.168.1.14 Received 51 bytes from 192.168.1.15#53 in 1 ms Trying "telcontar.valinor" Host telcontar.valinor not found: 5(REFUSED) Received 35 bytes from 192.168.1.15#53 in 0 ms Trying "telcontar.valinor" Host telcontar.valinor not found: 5(REFUSED) Received 35 bytes from 192.168.1.15#53 in 0 ms AmonLanc:~ # Ah, port 53 is not open on that machine. Not important. Ok, lets try email... interesting failure: 2013-08-31T22:37:10.248374+02:00 AmonLanc postfix/smtp[23220]: 06E38486E0: to=, relay=none, delay=0.39, delays=0.34/0.05/0/0, dsn=4.4.3, status=deferred (Host or domain name not found. Name service error for name=telcontar.valinor type=MX: Host not found, try again) So I have to find out how to configure dnsmasq to give an answer for 'MX'. There is another problem - internet name solving fails: p2phelper@AmonLanc:~> host google.es Host google.es.valinor not found: 5(REFUSED) p2phelper@AmonLanc:~> p2phelper@AmonLanc:~> host -v google.es Trying "google.es" Received 27 bytes from " in 0 ms Trying "google.es.valinor" Host google.es.valinor not found: 5(REFUSED) Received 35 bytes from 192.168.1.15#53 in 0 ms p2phelper@AmonLanc:~> Why is it asking for "google.es.valinor"? Why is it asking "192.168.1.15#53"? It should ask the router. But I do not see how to tell it to ask the router, I do not see a forwarder section in "/etc/dnsmasq.conf". It works if I disable dnsmasq. (reading) -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Carlos E. R. wrote:

/etc/resolv.conf:

search valinor #nameserver 192.168.1.1 nameserver 127.0.0.1

I use the external DNS servers here. I have 3 of them, 2 IPv6 and 1 IPv4.

/etc/dnsmasq.conf:

server=192.168.1.1

On my system, that line is commented out.

name solving works, and mail works too :-)

-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iF4EAREIAAYFAlIicAoACgkQAtgmQnSY2k3VLQEA4RjlJ7TuQM5+xhMb+ijzmYht na5ugO3mQNsFuWt/nZQBAIS6+Rm1EIOVR7ODhFCaVKtFC8rqIhu7jENgLxscl7+j =H/sy -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

[01.09.2013 03:31] [Carlos E. R.]:

On Saturday, 2013-08-31 at 18:36 -0400, James Knott wrote:

...

Carlos E. R. wrote:

...

/etc/resolv.conf:

search valinor #nameserver 192.168.1.1 nameserver 127.0.0.1

I use the external DNS servers here. I have 3 of them, 2 IPv6 and 1 IPv4.

...

/etc/dnsmasq.conf:

server=192.168.1.1

...

On my system, that line is commented out.

The documentation says that the way you say it works for other machines asking this machine for names.

But if you want the machine running dnsmasq to also query its own dnsmasq, it says that you point nameserver to itself in resolv.conf, and to an external place in dnsmasq.conf.

If you don't do the second part, you get a loop and no external resolution, which is the problem I had two posts ago.

So, if in resolv.conf you have several external DNS, and in dnsmasq.conf the "server=" is commented out, then that machine sends all queries to outside, not asking its own dnsmasq. Your local network machines instead can ask that machine dnsmasq.

That is the way it is run on my 20+ SAP systems at the office. resolv.conf may point to 1-3 nameservers, and so I configured 127.0.0.1 first, followed by two company name servers as failover when the local dnsmasq is not reachable. But only the local DNSmasq knows all about internally used hostnames in the SAP landscape, which often differ from the "official" ones. In dnsmasq.conf, I define all company name servers on one server= line each, and I tell dnsmasq "no-resolv", because that would be a recursion ;-) BTW, I also use "no-negcache", because sometimes the main internal DNS cluster has a hiccup... In case of mail, this may result in a deferred mail, mails warning you that the mail is deferred (being deferred themselves), and so on - from one mail sent you get 5 mails delivered at least ;-) Regards, Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Carlos E. R. wrote:

It works if I disable dnsmasq.

(reading)

I certainly had no problem with it on my system. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iF4EAREIAAYFAlIibtYACgkQAtgmQnSY2k1D6QEAyo/mEayiHLBkZnZp9WWboXQz KtyI3OGbJavUxqc4f6UA/1fQU7WAH6UyWEg7KymKQTWAwDQv2xk/hKqK7vABZ8wY =mT7Y -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Jeffrey L. Taylor said the following on 08/31/2013 02:35 PM:

Probably not. Postfix doesn't like cer@192.168.1.101, an IP address instead of a domain name. Maybe someone else can come up with a hack around the restriction.

Please read the manuals & documentation. Postfix uses a number of auxiliary files as to what transports to use for what addresses and domains. An address isn't a problem so long as you tell Postfix that. Start with 'Canonical' so you understand the formats, then 'Transport', which is probably the simplest way to address the above. Guessing... @192.168.1.101 smtp:[192.168.2.101]:587 Or maybe "25" instead of "587" :-) It all depends on the configuration :-) -- How long did the whining go on when KDE2 went on KDE3? The only universal constant is change. If a species can not adapt it goes extinct. That's the law of the universe, adapt or die. -- Billie Walsh, May 18 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

[01.09.2013 01:29] [Jeffrey L. Taylor]:

Quoting Anton Aylward :

...

Jeffrey L. Taylor said the following on 08/31/2013 02:35 PM:

...

Probably not. Postfix doesn't like cer@192.168.1.101, an IP address instead of a domain name. Maybe someone else can come up with a hack around the restriction.

Please read the manuals & documentation. Postfix uses a number of auxiliary files as to what transports to use for what addresses and domains. An address isn't a problem so long as you tell Postfix that.

Start with 'Canonical' so you understand the formats, then 'Transport', which is probably the simplest way to address the above.

Guessing...

@192.168.1.101 smtp:[192.168.2.101]:587

Or maybe "25" instead of "587" :-) It all depends on the configuration :-)

Really, as a recipient address? Every place I find an example recipient address given in the Postfix.org documentation, it is given as 'user@domain'. Please give a URL for documentation showing a recipient address (not in a configuration file) with an IP address.

I never found postix accepting user@ip.ad.dr.e.ss. Instead, one can use something like user@dont.know and define a transport like @dont.know smtp:[192.168.2.101] Regards, Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Werner Flamme said the following on 09/01/2013 03:58 AM:

I never found postix accepting user@ip.ad.dr.e.ss. Instead, one can use something like user@dont.know and define a transport like @dont.know smtp:[192.168.2.101]

That's ingenious! To be honest, I'm not sure the issue is with postfix, per se. I've just tried a few MUAs and they all reject "user@ip.add.re.ss" with a "bad address syntax" message. I suppose you could go into the message buffers of postfix and hand edit a valid address into an IP one. Perhaps, given a MUA that will accept that syntax and hand it to Postfix, we can set up a debug g trace to see how it handles or fails with it under various configs. But I can't say its a high priority matter given Werner's idea. -- How long did the whining go on when KDE2 went on KDE3? The only universal constant is change. If a species can not adapt it goes extinct. That's the law of the universe, adapt or die. -- Billie Walsh, May 18 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R. said the following on 09/01/2013 09:24 AM:

I wanted to, previously, because setting up bind is such a hassle... and because the machine is very low on ram.

ROTFLMAO! The machine from the Closet of Anxieties under my desk, the single core 800MHz job that supports, as I said, Bind/DNS, DHCP, fetchmail, VNC server and xfce, SSHD, Postfix, Dovecot and NFS, is now running with just 500M[1]. I saw the load average go up to this morning while running fetchmail though spamassassin, 16 NFS mounts active, mail flowing out. It actually reached 0.9. This machine is running Mageia with a 3.4.52 kernel. Perhaps its that Mageia is dramatically more efficient than openSuse :-) :-) :-) So I think you underestimate the capabilities. Either that or you are basing your estimates on one of a) how MS-Windows performs in similar situations b) how a Linux machine that is overloaded running X performs Having encountered (b) I can sympathise. Bus the kind of server I'm talking about is headless and doesn't need X. Heck, this one doesn't need VNC :-) [1] The other 500M is in another CoA machine I'm commissioning -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R. said the following on 09/01/2013 10:32 AM:

The other reason you forget, is that bind is a hasle to setup and configure. I have done it, and I don't want to do it unless I really need it.

Perhaps it a matter of the tools you use. Many years ago I got Cricket Liu's book. It has many scripts and there are many more out there. There are GUI tools to take care of it. Once I had it set up making small adjustments such as adding new hosts was trivial .... copy, paste, change last digit. Of course the DHCP server does updates too but I don't have to worry about those :-) Now it would be more effort to wipe and it and replace it than to continue using it and occasional ... as in once every few years ... adding a hard coded addition. -- How long did the whining go on when KDE2 went on KDE3? The only universal constant is change. If a species can not adapt it goes extinct. That's the law of the universe, adapt or die. -- Billie Walsh, May 18 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R. said the following on 09/01/2013 01:21 PM:

On Sunday, 2013-09-01 at 11:22 -0400, Anton Aylward wrote:

...

Carlos E. R. said the following on 09/01/2013 10:32 AM:

...

The other reason you forget, is that bind is a hasle to setup and configure. I have done it, and I don't want to do it unless I really need it.

Perhaps it a matter of the tools you use. Many years ago I got Cricket Liu's book. It has many scripts and there are many more out there. There are GUI tools to take care of it.

Once I had it set up making small adjustments such as adding new hosts was trivial .... copy, paste, change last digit.

I also used scripts to create mine. I could simply copy my files over, and trim. But it happens that dnsmasq doesn't need any configuration at all! It just reads the existing /etc/hosts file and produces its own things, in ram probably.

...

Of course the DHCP server does updates too but I don't have to worry about those :-)

Now it would be more effort to wipe and it and replace it than to continue using it and occasional ... as in once every few years ... adding a hard coded addition.

My main desktop computer uses bind. But I did not want to do the same on this laptop. Believe me, dnsmasq is easier.

Its that laptop which does it. Oh and a loaded /etc/hosts file. But given a loaded /etc/hosts file the scripts produce a Bind file... So really its down to dnsmasq being lighter, since the laptop isn't going to be doing other things like handing out DHCP. I don't need to duplicate. Default boot on my laptop is DHCP and the DHCP server here hands out DNS server addresses among other things. -- How long did the whining go on when KDE2 went on KDE3? The only universal constant is change. If a species can not adapt it goes extinct. That's the law of the universe, adapt or die. -- Billie Walsh, May 18 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Quoting Anton Aylward :

Carlos E. R. said the following on 09/01/2013 09:24 AM:

...

I wanted to, previously, because setting up bind is such a hassle... and because the machine is very low on ram.

ROTFLMAO!

The machine from the Closet of Anxieties under my desk, the single core 800MHz job that supports, as I said, Bind/DNS, DHCP, fetchmail, VNC server and xfce, SSHD, Postfix, Dovecot and NFS, is now running with just 500M[1]. I saw the load average go up to this morning while running fetchmail though spamassassin, 16 NFS mounts active, mail flowing out. It actually reached 0.9.

This machine is running Mageia with a 3.4.52 kernel. Perhaps its that Mageia is dramatically more efficient than openSuse :-) :-) :-)

So I think you underestimate the capabilities. Either that or you are basing your estimates on one of a) how MS-Windows performs in similar situations b) how a Linux machine that is overloaded running X performs

Having encountered (b) I can sympathise. Bus the kind of server I'm talking about is headless and doesn't need X. Heck, this one doesn't need VNC :-)

Postfix (w/o Spamassassin) runs comfortably on a 150MHz Pentium equivalent w/ 64MB of RAM. X usable, but the video card labored - flicker at any kind of refresh rate. Jeffrey -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Quoting Werner Flamme :

[01.09.2013 01:29] [Jeffrey L. Taylor]:

...

Quoting Anton Aylward :

...

Jeffrey L. Taylor said the following on 08/31/2013 02:35 PM:

...

Probably not. Postfix doesn't like cer@192.168.1.101, an IP address instead of a domain name. Maybe someone else can come up with a hack around the restriction.

Please read the manuals & documentation. Postfix uses a number of auxiliary files as to what transports to use for what addresses and domains. An address isn't a problem so long as you tell Postfix that.

Start with 'Canonical' so you understand the formats, then 'Transport', which is probably the simplest way to address the above.

Guessing...

@192.168.1.101 smtp:[192.168.2.101]:587

Or maybe "25" instead of "587" :-) It all depends on the configuration :-)

Really, as a recipient address? Every place I find an example recipient address given in the Postfix.org documentation, it is given as 'user@domain'. Please give a URL for documentation showing a recipient address (not in a configuration file) with an IP address.

I never found postix accepting user@ip.ad.dr.e.ss. Instead, one can use something like user@dont.know and define a transport like @dont.know smtp:[192.168.2.101]

Thank you, I understand this. It's specific enough and I've done something similar to this in the past. Endless calls to RTFM (I have) with vague handwaving to which part of TFM to read are not helpful. This helps with e-mail, though the other threads about setting up a local DNS server are a more general solution. Thank you, Jeffrey -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org