Re: bind9 and dns forward

Le 1 juin 2023 Bonno Bloksma a écrit : >> If you get an answer it's a dnssec problem with the error message in your >> logs. If there is no answer it's another problem. > Well, it seems I get an answer with the +cd option, and none without. Yes. If I do : # dig tio.nl A +dnssec +multiline ;

RE: bind9 and dns forward

Hi, @Tim, If I use the dnssec-validation no; option then indeed it all works. Just tested it again to make sure. And as a final solution to this problem I might accept it, but I would rather not. @Michel, > I reread all our mails and I miss to ask you this one (as answers via > external dns

Re: bind9 and dns forward

Le 1 juin 2023 Bonno Bloksma a écrit : > I can do that, but ... that is only for inbound traffic TO my dns server on > this network. > That part is working without any problem. Changing that will not change > anything for the clients on this network. You are right. I simply used to fix

RE: bind9 and dns forward

On Thu, 1 Jun 2023, Bonno Bloksma wrote: My bind instance can reach the company dns server buy claims the response is false/insecure Does that maybe mean that my bind gets a "normal" response from the company dns whereas the external dns at toplevel .nl. (being the parent zone) tells that

RE: bind9 and dns forward

at this moment as the company network has only partial IPv6 set up and is not using it over the whole network yet. I am only sure to reach all servers via IPv4, including the dns servers. Which is why I forward to the relevant ipv4 addresses. > Usually fe80:: are local only and not routed.

Re: bind9 and dns forward

Le 1 juin 2023 Bonno Bloksma a écrit : > linbobo:~# ss -nap | grep named > tcp LISTEN 0 10 [2a02:a45f:96c2:1:1e69:7aff:fe0c:65e3]:53 [::]:* > users:(("named",pid=554,fd=78)) > tcp LISTEN 0 10 [fe80::1e69:7aff:fe0c:65e3]%eno1:53 [::]:* > users:(("named",pid=554,fd=71)) > tcp LISTEN 0 10

RE: bind9 and dns forward

Hi, > resolv.conf must have only one search entry. And you don't want to resolv > with google directly. So you should have : Ok, I have the google dns commented. Alhough Now I remember why I had the google dns in there. ;-) For my machine to create the VPN it needs to know the ip number of

Re: bind9 and dns forward

Le 19 mai 2023 Bonno Bloksma a écrit : > Been a few busy week, that is why I only respond now, sory. Same for me :/ > beheerdertio@linbobo:~$ cat /etc/resolv.conf > domain bobo.xs4all.nl > search bobo.xs4all.nl > search tio.nl > search staf.tio.nl > search student.tio.nl > nameserver 127.0.0.1

RE: bind9 and dns forward

Hi, Been a few busy week, that is why I only respond now, sory. Also as there is a lot of sensitive info in this mail, like a complete lost to domain controllers to be hacked, ;-) I am sending it direct. I will send a redacted version to the list >> What does +cd do? I was unable to find

Re: bind9 and dns forward

Le 8 mai 2023 Bonno Bloksma a écrit : > I also do not understand this difference when querying the internal dns > server directly. > Why does the +trace +cd not show an answer but when I leave them out I get a > correct answer. Is that because +trace forces it to start at the root which is >

RE: bind9 and dns forward

:) Just did a flush and then a query. It still seems to query the public dns and not (exclusively) forward the request. linbobo:/etc/bind# dig einsccmdp-01.tio.nl +trace +cd ; <<>> DiG 9.16.37-Debian <<>> einsccmdp

Re: bind9 and dns forward

Le 5 mai 2023 Bonno Bloksma a écrit : > linbobo:/etc/bind# cat named.conf.local You have only zone blocks in this file, right ? And you don't use views ? > Why does it first go to the public dns and then run into the dnssec problem? > There is a direct definition for the tio.nl zone in my

RE: bind9 and dns forward

n the same forwarders. > I don't know if it's valid but it seems useless. And your logs suggest a > problem between staf.tio.nl and tio.nl. > Could you comment staf.tio.nl and student.tio.nl, restart bind (or reload + > flush) and try again above dig ? So you say if I just forward tio.nl to t

Re: bind9 and dns forward

Le 2 mai 2023 Bonno Bloksma a écrit : > linbobo:/etc/bind# cat named.conf.local > --- > [] > zone "tio.nl" IN { > type forward; > forward only; > forwarders {172.16.128.40; 172.16.208.10;}; > }; > > zone &

RE: bind9 and dns forward

do, however by now the machine has been up and running for over 3 days. > Do you have defined somewhere on linbobo a zone staf.tio.nl ? > I guess not but do a grep just to be sure. Yes, like I wrote in my original mail. > And similar lines for each possible subdomain like staf.tio.nl li

Re: bind9 and dns forward

Le 28 avril 2023 Bonno Bloksma a écrit : > We use a different dns server(s) and zonefile for the external dns > environment from what we use internally. Company dns is Windows server 2016 > incase that is relevant. It's better to use dig (package bind9-dnsutils) to first eliminate problems on

bind9 and dns forward

to the internal dns servers. A few months ago we had a change in our external dns provider and they enabled secure dns. After that I had some (security?) problems getting bind to forward my internal dns servers. My guess was that somehow it would see the security for the domain at the .nl level

[Path forward] WAS: Changing from Debian 9.13 to Debian 11.3

On 04/21/2022 07:03 AM, Richard Owlett wrote: I am not upgrading in place. I currently have Debian 9.13 installed on one partition with /home on a different partition. I will install Debian 11.3 on a fresh partition and have /home remain on its current partition. I'm aware of cautions

Re: neomutt on Bullseye not retaining multipart/alternative MIME on forward

* On 2021 05 Feb 19:02 -0600, darb wrote: > For anyone following along this was fixed in the latest neomutt release > 20210205 [1] I was going to follow up that version 20201127+dfsg.1-1 landed in my update for Bullseye today and the forwarding issue is fixed in this latest Debian version. -

Re: neomutt on Bullseye not retaining multipart/alternative MIME on forward

On 06/01/21 08:41PM, Nate Bargmann wrote: Last month I upgraded this desktop from Buster to Bullseye. It was a fresh installation since something went wrong on that particular day with 'apt dist-upgrade'. Oh well. Anyway, with the current neoumtt package whenever I forward an email

Re: neomutt on Bullseye not retaining multipart/alternative MIME on forward

Well, yesterday I finally got around to filing a bug on the neomutt GitHub issue tracker: https://github.com/neomutt/neomutt/issues/2788 The developers quickly bisected to the bug and the fix has been applied: https://github.com/neomutt/neomutt/commit/396a61b106ea16a8ea528a86fff5e0ab141df2fc I

Re: neomutt on Bullseye not retaining multipart/alternative MIME on forward

My apologies as I neglected to say that I set the variable to 'yes' and restarted neomutt and forwarded the latest message and the HTML attachment was dropped as before with this version. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears

Re: neomutt on Bullseye not retaining multipart/alternative MIME on forward

Well, that looked promising, David. Thanks for catching that. It appears that the count_alternatives variable is intended for counting the attachments a message has and showing that number in the index view. Its documentation leads to: https://neomutt.org/guide/mimesupport.html#attachments

Re: neomutt on Bullseye not retaining multipart/alternative MIME on forward

kage whenever I forward an email > that is MIME encoded and has an HTML attachment wrapped in a > multipart/alternative MIME block, the HTML attachment is dropped. The > message I am forwarding is to a local hobbyist mailing list and I was > notified by one of the list members a f

neomutt on Bullseye not retaining multipart/alternative MIME on forward

dist-upgrade'. Oh well. Anyway, with the current neoumtt package whenever I forward an email that is MIME encoded and has an HTML attachment wrapped in a multipart/alternative MIME block, the HTML attachment is dropped

Re: Easiest Way to forward an email Message from Linux to a Mac

Greg Wooledge writes: > Either you didn't run "apt-get update" first, or your mirror is out of > sync. The current version of dovecot-core in buster is > 1:2.3.4.1-5+deb10u1. Thank you. It was the former. I failed to run apt-get update but I didn't just forget. Ever since I upgraded

Re: Easiest Way to forward an email Message from Linux to a Mac

On Mon, Nov 04, 2019 at 12:06:44PM -0600, Martin McCormick wrote: > Then the wheels flew off: > > Err:1 http://ftp.us.debian.org/debian buster/main i386 dovecot-core i386 > 1:2.3.4 > .1-5 > 404 Not Found [IP: 208.80.154.15 80] Either you didn't run "apt-get update" first, or your mirror is

Re: Easiest Way to forward an email Message from Linux to a Mac

Bob Weber writes: > Why not create a user on the Linux box to receive such emails and have the > MAC client connect to that user on the Linux box. You might have to > install a pop server (popa3d ... easiest to install and configure) or imac > server (dovecot-imapd ... harder to configure and

Re: Easiest Way to forward an email Message from Linux to a Mac

. We are on a private vlan as in 192.168.x.x. All local host names are resolved via hosts files. Messages to go to the big wide world must go through Suddenlink's SMTP smarthost and I definitely don't want to break that. On rare occasions, I want to forward an email to the Mac which normall

Re: Easiest Way to forward an email Message from Linux to a Mac

to the big wide world must go through Suddenlink's SMTP smarthost and I definitely don't want to break that. On rare occasions, I want to forward an email to the Mac which normally doesn't send or receive emails. What would be the simplest way to "forward" an email from the

Re: Easiest Way to forward an email Message from Linux to a Mac

that. On rare occasions, I want to forward an email to the Mac which normally doesn't send or receive emails. What would be the simplest way to "forward" an email from the Linux box to the Mac's mailer? The Mac only needs to be able to receive, not send any email.our Hi Martin, D

Re: Easiest Way to forward an email Message from Linux to a Mac

o through Suddenlink's SMTP smarthost and I definitely don't want to break that. On rare occasions, I want to forward an email to the Mac which normally doesn't send or receive emails. What would be the simplest way to "forward" an email from the Linux box to the Mac's mailer?

Re: Easiest Way to forward an email Message from Linux to a Mac

Bob Weber writes: > > > Why not create a user on the Linux box to receive such emails and have the > MAC client connect to that user on the Linux box. You might have to > install a pop server (popa3d ... easiest to install and configure) or imac > server (dovecot-imapd ... harder to configure

Re: Easiest Way to forward an email Message from Linux to a Mac

that. On rare occasions, I want to forward an email to the Mac which normally doesn't send or receive emails. What would be the simplest way to "forward" an email from the Linux box to the Mac's mailer? The Mac only needs to be able to receive, not send any email. Thank you Martin W

Easiest Way to forward an email Message from Linux to a Mac

Here is the setup. We are on a private vlan as in 192.168.x.x. All local host names are resolved via hosts files. Messages to go to the big wide world must go through Suddenlink's SMTP smarthost and I definitely don't want to break that. On rare occasions, I want to forward an email

Re: which one is executed first ip_forward=1 or iptables FORWARD Drop

On Thu, Jun 13, 2019 at 10:06:30AM +0100, BELAHCENE Abdelkader wrote: > Hi, > I am using one machine, say SERV, as a gateway ( cards eth0, eth1) from > network1 to network2, I want to forward all packets but tcp port 80 so > I used > *sysctl -w net.ipv4.ip_forward=1* Th

which one is executed first ip_forward=1 or iptables FORWARD Drop

Hi, I am using one machine, say SERV, as a gateway ( cards eth0, eth1) from network1 to network2, I want to forward all packets but tcp port 80 so I used *sysctl -w net.ipv4.ip_forward=1* *I want to drop port 80, and accept others port* *I tryed* *iptables -A FORWARD -i eth1 -o eth0 -p

BIND forward de una zona publica al resolver 8.8.8.8 de Google

ot;mykey";}; recursion yes; zone "linux. <http://teamviewer.com>org" { type forward; forward only; forwarders { 8.8.8.8; // Este es el resolver de Google }; }; }; Pero el resultado es que todos los clientes pueden consultar tanto &

BIND forward de una zona publica a un resolver externo

"mykey";}; zone "linux. <http://teamviewer.com>org" { type forward; forward only; forwarders { 172.18.1.1; // Este es mi resolver conectado a Internet }; }; };

Re: Simple iptables table doesn't let me forward X windows

On Sat, Jan 20, 2018 at 07:30:09PM +, Joe wrote: > On Sat, 20 Jan 2018 12:13:12 -0600 > Jason wrote: > > > Hi, > > > > I am trying to setup (what should be) a simple iptables table between > > two machines on a local network, both with static IP addresses. The > >

Re: Simple iptables table doesn't let me forward X windows

On Sat, Jan 20, 2018 at 07:58:27PM +0100, Pascal Hambourg wrote: > Le 20/01/2018 à 19:13, Jason a écrit : > > > >I am trying to setup (what should be) a simple iptables table > > I don't think so. In iptables, "tables" are preexisting data structures > containing chains, and chains contain rules

Re: Simple iptables table doesn't let me forward X windows

Joe wrote: > OK, that leaves little doubt that it's a firewall issue. usually xauth missing or wrong xauth people do upgrade, then just press yes and pile up mess over mess and then come here to ask for help. it's fun regards

Re: Simple iptables table doesn't let me forward X windows

On Sat, 20 Jan 2018 12:13:12 -0600 Jason wrote: > Hi, > > I am trying to setup (what should be) a simple iptables table between > two machines on a local network, both with static IP addresses. The > machine I want to set up the iptables on is a headless server which I >

Re: Simple iptables table doesn't let me forward X windows

Le 20/01/2018 à 19:13, Jason a écrit : I am trying to setup (what should be) a simple iptables table I don't think so. In iptables, "tables" are preexisting data structures containing chains, and chains contain rules that you create. The set of rules in these chains and tables is called,

Simple iptables table doesn't let me forward X windows

Hi, I am trying to setup (what should be) a simple iptables table between two machines on a local network, both with static IP addresses. The machine I want to set up the iptables on is a headless server which I access using ssh. I want to cut off all communications except with the machine I ssh

Re: Consulta sobre port forward con shorewall

El 12 sept. 2016 10:53, "Camaleón" <noela...@gmail.com> escribió: > > El Sun, 11 Sep 2016 19:39:59 -0300, OddieX escribió: > > > Estimados, estoy teniendo un tema con shorewall y ya me he quemado la > > cabeza... > > > > Necesito hacer un forward d

Re: Consulta sobre port forward con shorewall

El Sun, 11 Sep 2016 19:39:59 -0300, OddieX escribió: > Estimados, estoy teniendo un tema con shorewall y ya me he quemado la > cabeza... > > Necesito hacer un forward de un puerto a otro ip... > > Es algo sencillo pero no esta funcionando y ya me he vuelto loco... (...)

Consulta sobre port forward con shorewall

Estimados, estoy teniendo un tema con shorewall y ya me he quemado la cabeza... Necesito hacer un forward de un puerto a otro ip... Es algo sencillo pero no esta funcionando y ya me he vuelto loco... Necesito que, cuando se haga una consulta al puerto de LDAP "389" desde cualquie

Re: Problem forward/postroute http/https thru vlan-ed interface.

Mimiko vbv...@gmail.com wrote: I did some test today to with tcpdump. It's realy strange. First I uninstalled vlan. Configured all again. using tcpdump I saw it was sending packets. But at first it didn't want to work. I added 8021q to /etc/modules, rebooted server and as I wrote: ping

Re: Problem forward/postroute http/https thru vlan-ed interface.

Well. I did some test today to with tcpdump. It's realy strange. First I uninstalled vlan. Configured all again. using tcpdump I saw it was sending packets. But at first it didn't want to work. I added 8021q to /etc/modules, rebooted server and as I wrote: ping works, ftp works, but not

Re: Problem forward/postroute http/https thru vlan-ed interface.

Mimiko wrote: I set up in interfaces: auto eth0 iface eth0 inet static address local_lan_ip netmask mask auto eth1.2 iface eth1.2 inet static address isp1 netmask mask auto eth1.4 iface eth2.4 inet static address isp2 netmask mask VLAN ID 2 is

Problem forward/postroute http/https thru vlan-ed interface.

$eth2.4_gateway dev $eth2.4_eth weight 100 In iptables I do: iptables -t nat -A POSTROUTING -o eth1.2 -j MASQUERADE iptables -t nat -A POSTROUTING -o eth1.4 -j MASQUERADE iptables -A FORWARD -j ACCEPT Now when i ping from the linux router - it works. When I ping from some workstation behind

Re: Problem forward/postroute http/https thru vlan-ed interface.

Bob Proulx b...@proulx.com wrote: Mimiko wrote: I set up in interfaces: auto eth0 iface eth0 inet static address local_lan_ip netmask mask auto eth1.2 iface eth1.2 inet static address isp1 netmask mask auto eth1.4 iface eth2.4 inet static address isp2

Re: Problem forward/postroute http/https thru vlan-ed interface.

Sven Hartge wrote: Bob Proulx b...@proulx.com wrote: I see no vlans in your configuration above. The above simply shows additional IP addresses being assigned. If your switch is requiring vlan tagging then that is likely your problem. Ah, nope. It's magic. Since Wheezy ifupdown

Re: Problem forward/postroute http/https thru vlan-ed interface.

Mimiko wrote: What is wrong with http/htpps ? Why icmp works, ftp works, but http/https is not working? Since Sven pointed out that I was out of date I no longer have a clue. To debug this I would run tcpdump on both sides of the router and examine the packets for http and verify that they are

Q: Apache::mod_proxy how implement request forward for image files

Using Mod Proxy, forward all requests for image files (.jpg, .gif, or .png) to the backend server without modifying the URL of the request All errors should log to /var/www/vhosts/frontend/logs/error.log All access requests should be logged to /var/www/vhosts/frontend/logs

Kile 2.1.0-1: No more Config kile. forward view and inverse search not working anymore

Hi all, This does not seems do be known as a bug. But on my last kile (from sid) I can not find the configure Kile from tools menu. Moreover the inverse search with okular is not working anymore. Neither the forward view from Kile. Without the configure kile buttons I am stuck. Any

Re: how forward email

john@example.net \john Cool! thanks :-) Pol -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51a24d4f.9080...@fuckaround.org

how forward email

Hi folks! putting an email to .forward (into a dir account) its email goes to that address. I need keep a copy of that email. Can I do it with /etc/aliases? or there's another way? thanks! Pol -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe

Re: how forward email

On Sat, 18 May 2013, Pol Hallen wrote: Hi folks! putting an email to .forward (into a dir account) its email goes to that address. I need keep a copy of that email. Can I do it with /etc/aliases? or there's another way? thanks! Pol One way would be to use procmail. Regards

Re: how forward email

Pol Hallen de...@fuckaround.org wrote: putting an email to .forward (into a dir account) its email goes to that address. I need keep a copy of that email. Can I do it with /etc/aliases? or there's another way? Put yourself into the .forward too, prefixed with \. For example, for someone

How to forward serial devices' input to X?

Hi, We have a barcode scanner used here, which for some reason has to be a serial device. So all its scanning output is sent to /dev/ttyACM0. If I `cat /dev/ttyACM0`, I could get the strings. Problem now is, how to let these input be sent to X, acting like a normal keyboard. Any ideas? --

Re: How to forward serial devices' input to X?

On Tue, Apr 30, 2013 at 02:48:29PM +0800, Magicloud Magiclouds wrote: Hi,   We have a barcode scanner used here, which for some reason has to be a serial device. So all its scanning output is sent to /dev/ttyACM0. If I `cat /dev/ttyACM0`, I could get the strings.   Problem now

Re: How to forward local mail to external address?

of the crontab entry for the user that cron is running the jobs for, like this: MAILTO=u...@othermachine.com If you want all mail that's being sent to a local address to be forwarded, you can put a .forward file in the home directory of the user that's receiving the mail

Re: How to forward local mail to external address?

to a local address to be forwarded, you can put a .forward file in the home directory of the user that's receiving the mail, with the address to be forwarded to in it. No other text is needed, just the address. --Dave signature.asc Description: OpenPGP digital signature

Re: How to forward local mail to external address?

...@othermachine.com If you want all mail that's being sent to a local address to be forwarded, you can put a .forward file in the home directory of the user that's receiving the mail, with the address to be forwarded to in it. No other text is needed, just the address. A third way is to add an entry

How to port forward inside a folder ?

iptables -A FORWARD -p tcp --dport 82 -i ${LAN_IFACE} -j ACCEPT iptables -A PREROUTING -t nat -i ${WAN_IFACE} -p tcp --dport 82 -j DNAT --to 192.168.1.2:80 iptables -A FORWARD -p tcp -d 192.168.1.2 --dport 80 -j ACCEPT ``` How can I forward inside a folder like 192.168.1.1

Re: How to port forward inside a folder ?

${LAN_IFACE} -p tcp --dport 82 -j DNAT --to 192.168.1.2:80 iptables -A FORWARD -p tcp --dport 82 -i ${LAN_IFACE} -j ACCEPT iptables -A PREROUTING -t nat -i ${WAN_IFACE} -p tcp --dport 82 -j DNAT --to 192.168.1.2:80 iptables -A FORWARD -p tcp -d 192.168.1.2 --dport 80 -j ACCEPT

Re: How to port forward inside a folder ?

} -p tcp --dport 82 -j DNAT --to 192.168.1.2:80 iptables -A FORWARD -p tcp --dport 82 -i ${LAN_IFACE} -j ACCEPT iptables -A PREROUTING -t nat -i ${WAN_IFACE} -p tcp --dport 82 -j DNAT --to 192.168.1.2:80 iptables -A FORWARD -p tcp -d 192.168.1.2 --dport 80 -j ACCEPT

Re: How to port forward inside a folder ?

-A INPUT -p tcp -m tcp --dport 82 -j ACCEPT iptables -A PREROUTING -t nat -i ${LAN_IFACE} -p tcp --dport 82 -j DNAT --to 192.168.1.2:80 iptables -A FORWARD -p tcp --dport 82 -i ${LAN_IFACE} -j ACCEPT iptables -A PREROUTING -t nat -i ${WAN_IFACE} -p tcp --dport 82 -j DNAT --to 192.168.1.2:80

Re: How to port forward inside a folder ?

On 5/24/12 11:32 AM, J. Bakshi wrote: Ok, thanks. Then I'll do it by rewrite through .htaccess If you have access to the web server's configuration file, put your changes there instead. It is better to have everything in the same place. Also, if you haven't already, take a look at the Rewrite

Re: How to port forward inside a folder ?

On Thu, 24 May 2012 12:46:33 +0300 Lars Noodén lars.noo...@gmail.com wrote: On 5/24/12 11:32 AM, J. Bakshi wrote: Ok, thanks. Then I'll do it by rewrite through .htaccess If you have access to the web server's configuration file, put your changes there instead. It is better to have

network / nat / port forward -- problem

on the internet flawlessly, but I cannot host a server myself, others can't connect to me. how to I forward the ports to the eth1 machine so that I can have a server on it? (or as routers often call it virtual servers) I also want to activate the firewall on the debian machine but that also has

Re: network / nat / port forward -- problem

On Jo, 12 ian 12, 16:34:16, YR wrote: The system has 2 network cards. Debian accesses the internet via eth0 without problems. (typical dhcp getting IP from ISP) the internet connection is shared, and the xp machine connected to eth1 connects to the internet also without problems (none that I

Re: network / nat / port forward -- problem

the machine connected to eth1 I could play quake 3 connecting to a server on the internet flawlessly, but I cannot host a server myself, others can't connect to me. how to I forward the ports to the eth1 machine so that I can have a server on it? (or as routers often call it virtual servers) Here you

Re: network / nat / port forward -- problem

of your Debian box? my problem is that I cannot access the machine on eth1 when it serves. For example, from the machine connected to eth1 I could play quake 3 connecting to a server on the internet flawlessly, but I cannot host a server myself, others can't connect to me. how to I forward

Re: Address forward en bind.....?

el momento no he encontrado mucha información. Se puede configurar con bind lo que se llama Address Forward? Esto es, definir en la zona del dominio que todos los mails a @domain.com se reenvien a @other.com, servicios como easydns y zoneedit tienen esta opción, pero no sé si es posible

Re: Address forward en bind.....?

On Sun, 31 Jul 2011 14:41:05 -0300 Carlos Miranda Molina (Mstaaravin) wrote: El registro MX lo apuntas donde quieras. domain.com. IN MX 5 mx.other.com. fíjate en el punto del final y recuerda que mx.other.com debería ser un registro A y no un CNAME o tendrás problemas con algunos

Re: Address forward en bind.....?

ser mi primera instalación en producción con Bind (siempre fui fan de DJBDNS) Tengo una duda que hasta el momento no he encontrado mucha información. Se puede configurar con bind lo que se llama Address Forward? Esto es, definir en la zona del dominio que todos los mails

Re: Address forward en bind.....?

bien hasta el momento ademas de ser mi primera instalación en producción con Bind (siempre fui fan de DJBDNS) Tengo una duda que hasta el momento no he encontrado mucha información. Se puede configurar con bind lo que se llama Address Forward? Esto es, definir en la zona del dominio que

Re: Address forward en bind.....?

hasta el momento no he encontrado mucha información. Se puede configurar con bind lo que se llama Address Forward? Esto es, definir en la zona del dominio que todos los mails a @domain.com se reenvien a @other.com, servicios como easydns y zoneedit tienen esta opción, pero no sé si es

Re: Address forward en bind.....?

2011/7/31 Juan Antonio push...@limbo.ari.es: El registro MX lo apuntas donde quieras. domain.com. IN MX 5 mx.other.com. fíjate en el punto del final y recuerda que mx.other.com debería ser un registro A y no un CNAME o tendrás problemas con algunos intercambiadores. Me parece que no

Re: Address forward en bind.....?

El Sun, 31 Jul 2011 14:41:05 -0300, Carlos Miranda Molina (Mstaaravin) escribió: 2011/7/31 Juan Antonio push...@limbo.ari.es: El registro MX lo apuntas donde quieras. domain.com. IN MX 5 mx.other.com. fíjate en el punto del final y recuerda que mx.other.com debería ser un registro A y no

Address forward en bind.....?

configurar con bind lo que se llama Address Forward? Esto es, definir en la zona del dominio que todos los mails a @domain.com se reenvien a @other.com, servicios como easydns y zoneedit tienen esta opción, pero no sé si es posible hacerlo con bind para evitar poner un MTA que redireccione los mails

Re: Opportunity for moving Debian forward - Re: Created RAID wiki page. Please add some information. ; gre

On Tuesday 21 June 2011 09:10:41 giovanni_re wrote: I have given an opportunity to the Debian community Tommy-rot. The Debian community already was, and is still, able to post anything to the wiki that it wishes. All you have done is create empty pages that will confuse search engines, and

Opportunity for moving Debian forward - Re: Created RAID wiki page. Please add some information. ; gre

, think for merely 10 to 15 seconds about what you might do in merely 30 seconds to help move the debian community forward when looking at a page such as the one I'd created. Then, move it forward. TIA. :) -- Jon Dowland

Re: Opportunity for moving Debian forward - Re: Created RAID wiki page. Please add some information. ; gre

On 21/06/11 18:10, giovanni_re wrote: Thanks for your interest in this, Jon. :) Please don't top post. Please don't fork threads. Please read, and respect the rules and guidelines for posting - it's not that hard to re-quote posts as they were originally formatted. On Mon, 20 Jun 2011

Re: Opportunity for moving Debian forward - Re: Created RAID wiki page. Please add some information. ; gre

On Tue, Jun 21, 2011 at 4:10 AM, giovanni_re john...@fastmail.us wrote: FYI http://lists.debian.org/debian-www/2011/06/msg00157.html -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

qemu port forward host - guest: unable to get network access

Hi, I want to start a virtual machine and be able to connect to it from the host. Reading the qemu manual, I found I have to use -net nic to choose both NIC MAC and model and -net user in order to define port forwards from host to guest. I want to forward ports (tcp) this way: host:2564

Re: qemu port forward host - guest: unable to get network access

Sorry: the MAC I wrote is too long, please read aa:bb:cc:dd:ee:ff instead. Nicolas -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4de79491.7070...@yahoo.fr

Re: Problema con IP FORWARD ySSH

Hice nat al router para que peuda pasar los paquetes e hice un port forward para redireccionar el trafico ssh(22) a una maquina dentro de la LAN pero nunca llega, segui probando y puse otro server para ssh pero esta vez con una ip de la dmz en este caso la misma maquina que me esta sirviendo

Problema con IP FORWARD ySSH

paquetes e hice un port forward para redireccionar el trafico ssh(22) a una maquina dentro de la LAN pero nunca llega, segui probando y puse otro server para ssh pero esta vez con una ip de la dmz en este caso la misma maquina que me esta sirviendo como router y en esta el si se conecta. Es decir

debian lenny no ipv6 forward

Hello, I cannot get radvd to work out of the box because ipv6 forward is disabled -quote--- linbobo:/var/log# /etc/init.d/radvd start Starting radvd: * IPv6 forwarding seems to be disabled. * See /usr/share/doc/radvd/README.Debian * radvd will *not* be started. linbobo:/var/log

Re: debian lenny no ipv6 forward

On 2010-11-24 21:31 +0100, Bonno Bloksma wrote: I cannot get radvd to work out of the box because ipv6 forward is disabled -quote--- linbobo:/var/log# /etc/init.d/radvd start Starting radvd: * IPv6 forwarding seems to be disabled. * See /usr/share/doc/radvd/README.Debian

Re: debian lenny no ipv6 forward

Bonno Bloksma wrote at 2010-11-24 13:31 -0700: I cannot get radvd to work out of the box because ipv6 forward is disabled However in sysctl.conf in sysctl.conf I have: -quote--- linbobo:~# grep ipv6 /etc/sysctl.conf net.ipv6.conf.all.forwarding=1 #net.ipv6

BIND - Como fazer forward dominio.local para outro DNS ?

Olá Pessoal, Tô com um problema de configuração do Bind. Ainda não encontrei na documentação algo assim, por isso estou perguntando 'a lista. Eu tenho num cliente um servidor que eu mesmo instalei e nele um DNS só para resolver internet, ok ? Porém, o mesmo cliente tem um Active

cherokee et x-forward-for : ça le fait pas

) J'ai des serveurs apache et cherokee derrière. - pour apache j'utilise le x-forward-for avec succès - pour cherokee, je comprends pas comment cela fonctionne avec cela : Je prends mon site virtuel (site1.toto.com) - dans 'journalisation' - je coche Accept Forwarded IPs + restart cherokee

Enigmail no me reconoce la firma cuando hago un forward

Hola: Utilizo Enigmail con Icedove (Mozilla para entendernos :-) en Leny. Funciona bien, me envío correos entre mis cuentas y la firma siempre es reconocida, salvo cuando hago un forward de algún mensaje. He buscado con google y en los bugs de enigmail, pero no he visto nada. Alguien puede

Sobre squid (2 NICs, no forward)

: luego de agregar la 2da iface al squid y configurar todo, debería también habilitar el bit forward (en el servidor squid). Según mis conocimientos la respuesta debería ser que no, ya que no veo la necesidad de que los clientes lleguen a la interfase del squid que estaría conectada al router. Bueno

[iptables] Forward http

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I just installed a new debian lenny server and now i am trying to forward all http request from my old debian etch installation to the new one. The statement i used was the following: iptables -t nat -A PREROUTING -p tcp --dport http -j DNAT

  1   2   3   4   5   6   7   >