Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I've just set up an IPV6 tunnel for my server (running Ubuntu Karmic Koala), with GO6 and I'm trying to work out use cases for it.

I have a dynamic ip address, and some wierd proxy setup that makes automatic DDNS currently not work with most providers - I periodically end up needing to do it manually

My webserver is already running IPv6, and other than that very few people have support for it (something I need to work at fixing!), its a lot less troublesome.

While I do have other options (Google apps), I'm pondering running an e mail server, and want to know if IPv4 'fails' due to port blocks, it'll switch over to IPv6, and how an IPv6 mailserver handles sending mail to an IPv4 system?

share|improve this question
    
"its a lot less troublesome", yet you appear to be having rather a lot of trouble. :) –  John Gardeniers Jan 29 '10 at 1:25
    
well, the theory, as opposed to the practical side. My isp does quite a load of strange things.. including breaking almost every dynamic dns service i have tried magnificently. Since i just need to access my own systems remotely primarily, and the mail server is just for fun... I was just curious –  Journeyman Geek Jan 29 '10 at 14:09

3 Answers 3

up vote 4 down vote accepted

You are asking whether IPv4 “fails over” to IPv6 when IPv4 is unavailable. Yes, it sort of does if you look at it from the wrong angle, but it is actually the other way around.

When IPv6 is enabled, it is preferred over IPv4. So in actual fact, IPv4 doesn’t “fail over” to IPv6. Rather, if IPv6 is *un*available, it “fails over” to IPv4.

Your question asks specifically about IPv6 mail servers, but this behaviour is universal. HTTP, FTP, IMAP, you name it. If a website is both IPv6– and IPv4–enabled, your browser will prefer the IPv6 version (assuming you have IPv6 connectvity). If you are sending mail to an IPv6–enabled mail server, it will go over IPv6.

(As to whether it will try again over IPv4 if your IPv6 fails I cannot answer at this stage — not tested it myself, unfortunately. If this is an issue, you could use two MX records — one that points to an IPv6–only hostname, and one to an IPv4–only hostname.)

If you IPv6–enable your mail server, but still keep IPv4 enabled (e.g. on Postfix you would set inet_interfaces = all, not inet_interfaces = ipv6), then you will be able to send mail to IPv4 and IPv6 mail servers, as well as receive mail from IPv4 and IPv6 sources.

This wasn’t part of your question, but does pertain to IPv6 mail servers: currently none of the major DNSBLs (e.g. Spamhaus) support IPv6. While I haven’t seen a single piece of spam originating from an IPv6 address, be aware that the only spam preventative measures you can take are keyword–based.

share|improve this answer
    
my primary ip address is dynamic (yes, i know its not recommended. which is why i'm considering it, as opposed to running it already)- which is one reason i'd prefer ipv6 over ipv4. Having ipv6 ready resources on a secondary subdomain is something i am considering, since it might be easier for me to tell when something is failing, and where ;p As for spam.. i'm not actually very worried since its mostly for experimentation - i'll likely have baysian filtering and such, and if push comes to shove, i'll happily start blacklisting errant ip addresses myself ;p –  Journeyman Geek Mar 7 '10 at 9:23
    
i suppose the crux of the question to me is, can i actually run a viable mail server on ipv6 alone? –  Journeyman Geek Mar 7 '10 at 11:35
    
Can you actually run a viable server on IPv6 alone? In this early stage of IPv6 deployment, if you expect to get mail from other people, the answer is pretty much "no". However, if you have another mail server sitting out there on the Internet that will accept mail over IPv4, and forward to you over IPv6, that's feasible — that's about the only vaguely useful case I can think of right now. –  Jeremy Visser Mar 15 '10 at 6:26

An application that is v4 and v6 capable that fails at v4 might try v6, but it also might not. Dual-stack applications are all over the map on this. For example, some of them try to start in v6, which is fine for you and awful for other folks. Some of them will fail over to v6 as you want, but may not do it when you want: they might do it if they don't get a v4 response "fast enough", making them very hard to debug.

Also remember that most applications are running on OSs that will always do DNS lookups in v4 because they don't have v6 DNS resolution enabled. That makes debugging even more difficult.

The theme here: you can possibly do what you want, but you are buying into some seriously difficult customer support and debugging, at least for the next few years. If you like living on the bleeding edge, party on.

(Disclaimer: I ran such a system for a while as part of the IETF's v6-only experiment, but shut it off due to the debugging issues.)

share|improve this answer

In theory, your interface will not have an IPv4 interface, so any users (that is, clients on your machine) will get "destination unreachable." However, the world makes this very hard to do sometimes.

How many of these clients behave is totally client dependent. I've had very back luck with some, and some simply will not use anything but IPv4 and fail when it is not available.

You will be able to reach some places, but not all. It's hard to live in IPv6 only without sometimes.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.